Set up your client project: ICP definition, messaging guide, objection playbook, and content library
Teams build one Juma project per brand they run revenue for and add context over time. Every handoff, nurture sequence, and content brief pulls from the same project, so the more the project knows, the sharper each brief gets. If a project already exists for this account, adding a few revenue documents means every handoff scores the call against your real ICP and messaging instead of a generic read.
What to add
ICP Definition & Scorecard
Your ideal customer profile and the criteria that define a fit. With this in the project, the ICP-fit signals score the account against your real profile, not a generic guess, and the brief flags exactly where the account matches and where it does not.
Messaging & Positioning Guide
Your named messaging pillars, value props, and proof points. Add this and "what resonated" maps to the specific pillar that landed, so marketing knows which story to keep telling this account.
Objection Handling Playbook
Your approved responses to common objections. With this in the project, each objection in the brief comes with your team's tested counter, not an improvised one.
Content & Nurture Library
What you have already published and the assets sales can send. Add this and the content ideas point to pieces that exist, with new ones proposed only where there is a real gap.
Guide Juma with project info
Add a short description to each knowledge item in the project's info field so Juma knows what each file holds and when to use it. For example:
- ICP Definition & Scorecard: "Our ideal customer profile and fit criteria. Score every account in the handoff against this."
- Messaging & Positioning Guide: "Our messaging pillars and proof points. Map what resonated on the call to these."
- Objection Handling Playbook: "Our approved objection responses. Use these as the counter for every objection in the brief."
- Content & Nurture Library: "What we have already published. Point content ideas here first, and propose new pieces only for real gaps."
Give marketing what they need to support the deal
Frequently Asked Questions
How much time does the sales-to-marketing handoff save compared to writing it by hand?
Writing a handoff brief by hand takes a rep 30 to 45 minutes of re-listening and typing per call, so most never get written. Juma produces the brief in minutes from the recording, which means marketing gets the context on every deal, not just the memorable ones.
The rep still owns the deal. Strategy, taste, and judgment stay human: the brief is a starting draft the team reviews and trims before it moves, and Juma augments the handoff, it doesn't replace the rep's read of the room. For a team running a full pipeline, that is the difference between marketing supporting a handful of deals and supporting all of them.
What does the sales-to-marketing handoff brief include?
Every brief has five parts: an account snapshot, an ICP-fit signals table with evidence from the call behind each signal, the positioning and messaging angles that resonated in the room, the objections to counter with a counter for each, and three to four content or nurture ideas mapped to the account.
The ICP-fit signals table is the part most teams find hardest to build by hand. It lists each signal the account showed on the call, whether budget, timing, use case, or team size, and pairs it with the line where the buyer said it. That evidence is what lets marketing trust the read without re-listening to the recording.
What does Juma need to run the handoff: a Fathom recording or a transcript?
Either works. With Fathom connected, ask for your most recent sales call and Juma pulls the recording and transcript on its own. No Fathom, no problem: paste a transcript from Zoom, Gong, Google Meet, or any recorder, and the same brief runs from the pasted text.
Connecting Fathom is the lighter path when you run this after every call, because you never leave the chat to fetch a file. The connection is read-only and scoped to what your Fathom account can already see, so nothing new is exposed.
How do you keep the handoff accurate and grounded in the call?
Ask Juma to attach a direct quote or timestamp to every ICP-fit signal, objection, and note on what resonated. The grounding pass marks anything it inferred rather than heard, so the team can see where the brief is solid and where it is reading between the lines before anyone acts on it.
Human review is the norm on every brief. The rep who ran the call reads it, corrects anything the transcript missed, and cuts what does not matter before it reaches marketing. Juma does the assembling; the team keeps the judgment about what is true and what counts.
Does this work for agencies running revenue for more than one client?
Yes. Agencies keep one Juma project per client, each with that client's ICP, messaging, and objection playbook. A handoff run inside a client project scores the call against that client's profile, so the same flow produces a brief tuned to each account without re-setting anything between clients.
Unlimited seats on every plan means the whole revenue team, sales, marketing, and CS, can open the same brief without per-seat fees. Juma's pricing is credit-based, so a busy agency running handoffs across a full client roster pays for the work done, not for the number of people who read it.