Rep knows how sales dashboards are usually laid out, so a short ask like "Build me a pipeline dashboard" gets you a reasonable first version. This playbook covers how to steer it toward the version you want: naming the format, asking for what you care about, adding filters, settling your definitions once, and changing a version instead of starting over.
New to artifacts? Start with Artifacts for what they are, where they live, and who can see them.
Name the format
Say dashboard, deck, or document in your ask. Rep decides between building an artifact and answering in chat, and a request like "a won deals breakdown" or "a battle card" can come back as a chat reply. A chat reply stays in that conversation. An artifact is saved in Library, where you can open it again, share it, and change it.
Start a new chat from Library. Rep uses the page you are on as context, so if you ask while another artifact is open, it may fold that artifact into the new one.
Ask for what you care about
A short ask is a fine place to start. Rep chooses what to show, and you can change it afterward. When one of these matters to you, name it in the ask so Rep does not have to choose:
Which deals. Open only, or everything including won and lost. This is the most common reason a total looks different from what you expected.
What to measure. Total value, deal count, average deal size, win rate.
How to break it down. By stage, source, or month.
What to show. Headline numbers across the top, bar charts to compare, a table when you want to read the deals themselves.
Filters and date ranges
Ask for filters by name, and they appear across the top of the dashboard: "Add a filter for deal owner", "Add a filter for team member". Use a filter instead of asking Rep to split every chart by person, so you can switch between people without a new version.
Ask for a date range filter whenever the time window matters, rather than relying on Rep to add one. What you get depends on what the dashboard counts:
Activity, such as meetings and emails. You get a date picker that starts at the last 30 days. Choose a range, then click Apply. The numbers change only after you click Apply.
A date on the deal, such as close date. Say which date: "Add a date range filter on close date, defaulting to the last 6 months." You get a list of set windows, such as the last 3, 6, or 12 months.
Settle your definitions once
Words like "win rate", "pipeline", or "this quarter" mean different things in different teams. When a term is unclear, Rep asks before it builds. When it has to make a choice on its own, it tells you which one it made.
Rep may also offer to save a definition, for example which stages count as closed won. Say yes when the definition is right. The first time, Clarify asks you to allow Rep to create the skill. Rep saves it to your workspace's Metric definitions skill, so later reports reuse it instead of asking or guessing again. The skill is shared with your workspace, so your teammates' reports use the same definition.
Decks and documents
For a deck or a document about one deal or account, name the record in your ask: "Write a proposal for the Acme expansion deal." Rep reads that record's meetings, emails, and connected records before it writes. See Artifacts about one deal or account.
Say who it is for and how long it should be: "a one-page summary for our CFO", "a 6-slide QBR for the customer".
Prompts to start from
Copy one and change what does not fit.
Pipeline health
Build a pipeline health dashboard for open deals only. Top row: open pipeline value, open deal count, average deal size, and win rate. Then deals by stage and value by stage as bar charts side by side. Label it clearly that closed deals are excluded.
Win rate compares won deals to lost ones, so that one tile always counts closed deals.
Forecast for a quarter
Build a forecast dashboard for deals with a close date in Q4. Show total forecast value, deal count, and average deal size, and the value by stage. Add a filter for deal owner.
Pick an owner in the filter to see one person's forecast. If your fiscal year does not start in January, tell Rep when it starts.
Team activity
Build a team activity dashboard showing meetings and emails per person, with a total at the top. Add a date range filter and a filter for team member.
Each person's numbers only include the meetings and emails you can see.
Won deals
Build a won deals dashboard. Count a deal as won by its close date. Show total won value and count, broken down by source and by owner. Add a date range filter on close date, defaulting to the last 6 months.
To see the deals behind a number, click See underlying data on that tile. Without "by its close date", Rep may count a deal on the day it moved to won instead. If your deals have no field called Source, Rep asks which field to use, or picks the closest one and tells you.
A battle card for one company
Write a one-page battle card document for [company] using what is in Clarify: who we have met, what they asked about, deal stage and value, and any objections raised in meetings.
Name the sections you want. A shorter ask can leave some out. Rep reads the company's meetings, emails, and deals before it writes, so the card is only as full as what Clarify holds.
A deck for a weekly meeting
Build a pipeline review deck for our weekly team meeting.
A short ask works well for a deck. Click Present to show it in the meeting.
If the first version is not right
Do not start a new one. Tell Rep what to change and it saves a new version of the same artifact:
"Group this by owner instead."
"Exclude lost deals."
"Add a filter for deal owner."
"Add a total row."
If a number looks wrong, ask Rep how it calculated it, or click Something off? and then Fix it with Rep. Every save is kept, so you can go back with Version history.
Asking again from scratch leaves you with several half-right dashboards instead of one good one.
Related