The one thing to act on today
Your strongest opportunities are ready for the next conversation. Send Cedar Labs their tailored proposal. Then align on the launch plan with Juniper Works.
Today’s conversations
A little context goes a long way09:30 · Cedar Labs
Discovery is complete. Confirm success criteria, the delivery owner, and a realistic timeline before sharing the proposal.
14:00 · Juniper Works
A warm introduction turned into an active evaluation. Bring one relevant case study and two questions about their current process.
Follow through
Three small moves for a stronger weekSend the proposal
Turn Cedar’s agreed scope into a one-page proposal with milestones and next steps.
Reconnect with Harbor
Share the research note they requested and offer two times for a follow-up.
Update the forecast
Review each close date with its owner before the Friday pipeline review.
Sample call brief
Cedar Labs
A focused conversation about a better operating rhythm.
What we know
- The team wants a shared view of work and fewer manual handoffs.
- A clear pilot outcome matters more than a long feature list.
- The decision owner joins the next review.
Questions to explore
- Where does work slow down today?
- What would a successful first month look like?
- Who needs to sign off on the next step?
Leave with a next step
Mutual action plan
Agree on one measurable outcome, one owner, and a date to review progress.
Sample call brief
Juniper Works
A focused conversation about a better operating rhythm.
What we know
- The team wants a shared view of work and fewer manual handoffs.
- A clear pilot outcome matters more than a long feature list.
- The decision owner joins the next review.
Questions to explore
- Where does work slow down today?
- What would a successful first month look like?
- Who needs to sign off on the next step?
Leave with a next step
Mutual action plan
Agree on one measurable outcome, one owner, and a date to review progress.
Pipeline at a glance
Demo quarter · all amounts fictionalMomentum
Sample weekly performanceConversations per week
Revenue and commission
Closing funnel
Conversation quality
Active opportunities
Next steps, by account
| Account | Stage | Value | Owner | Next step |
|---|---|---|---|---|
| Cedar Labs | Proposal | $12,000 | Alex Morgan | Scope review |
| Juniper Works | Discovery | $8,000 | Jamie Park | Pilot briefing |
| Harbor Studio | Qualified | $16,000 | Taylor Quinn | Technical workshop |
| Lumen Collective | Negotiation | $24,000 | Sam Rivera | Mutual action plan |
Your judgment matters
Choices stay in this demo sessionGive the operating system direction. Review the evidence, choose a path, and make the trade-off explicit.
Which pilot should go first?
Cedar has an agreed scope. Harbor has more upside but needs another workshop.
How should we package discovery?
A short, fixed-scope workshop helps both teams agree on the outcome before delivery.
Execution log
An example of an auditable operating rhythmSample run · Morning brief
Operator note
What should the next run consider?
This scratchpad is session-only. No agent is scheduled or connected.
Context is the foundation
One home for the facts your team and agents use. These example briefs are ready to replace with your own.
Context
The shared operating manual.
Offer
The promise, deliverables, and boundaries.
Example brief
- A four-week operating system pilot.
- Map one workflow, agree on success criteria, build the smallest useful system, and review adoption.
- A clear scope and named owner are required before delivery.
Positioning
What makes your approach worth choosing.
Example brief
- Make useful work easier to repeat.
- Connect shared knowledge to everyday decisions and remove manual handoffs.
- Show a concrete before-and-after instead of promising universal automation.
Ideal customer
Who you serve and who you do not.
Example brief
- Teams of 10–50 with a repeatable service workflow.
- A decision owner, one measurable bottleneck, and time for a small pilot.
- Avoid projects without a clear owner or a realistic success measure.
Sales process
A repeatable path from first contact to delivery.
Example brief
- Discover → qualify → propose → agree → deliver.
- Every stage has an owner, evidence, and a next step.
- Review the forecast weekly and archive stalled opportunities deliberately.
Voice & tone
How your team sounds in every conversation.
Example brief
- Clear, warm, and specific.
- Lead with the customer’s situation, explain the next step, and keep promises bounded.
- Use examples. Avoid hype, pressure, and unsupported outcomes.
Operating rules
Ownership, thresholds, and review cadence.
Example brief
- Review pipeline every Friday.
- Require human review before messages, proposals, contracts, or external actions.
- Use permission-checked vault reads when connecting this template to real data.
Capabilities
Playbooks to customize with your agentCall preparation
Review the account, last conversation, open questions, and next decision.
Follow-up draft
Write a concise recap with an owner and date for every next step.
Pipeline review
Summarize changes, close-date risks, and opportunities needing attention.
Proposal outline
Translate agreed scope into outcomes, milestones, and acceptance criteria.
Account research
Build a sourced account brief from documents you can access.
Win / loss review
Capture what changed the outcome and improve the next conversation.
Your tool stack
Illustrative slots · no services connectedCRM
Accounts, contacts, and opportunity stages.
Meetings
Notes, decisions, and follow-up commitments.
Proposals
Scopes, versions, and acceptance criteria.
Drafts for a human to review and send.
Knowledge
Your vault as the source of truth.
Agent
An assistant you configure and authorize.