Share a Fathom call link, paste call notes, or name the prospect. Juma researches the company, matches your strongest case studies, recommends a pricing tier, and ships a branded proposal PDF the same session.
Share a Fathom call link, paste discovery notes, or just name the prospect and the scope. Juma researches the company, pulls relevant case studies and pricing structure from the project, and drafts a tailored client proposal ready to send. The output is a branded multi-page HTML proposal exported as PDF, covering the prospect's pain, your recommended approach, a fit pricing tier with reasoning, ROI metrics, and matched social proof.
Paste the Fathom share link and Juma scrapes the transcript directly. The model extracts the prospect's team size, industry, stated pain points, security concerns, and any pricing or scope cues mentioned on the call, then drafts the proposal around what was actually said. No need to summarize the call first. No risk of leaving out something the prospect emphasized that you forgot to write down. The branded PDF comes back with a cover slide naming the prospect, a Challenge section grounded in their exact words, and a Pricing section anchored to the seat count or scope they shared.
Pull the most recent Fathom call with Notion (https://www.notion.so) and draft the proposal.
Paste the notes inline, even if they're rough. Juma asks a few clarifying questions to fill the gaps, like team size, primary pain, who you're competing with, and the scope they want, then drafts the proposal tailored to what you shared. This is the right mode when the call wasn't recorded, when notes live in a doc you don't want to upload, or when you simply prefer to feed context as a paragraph. The output is the same branded HTML and PDF, structured around the prospect's actual situation rather than a generic template.
Just wrapped a discovery call with LEGO (https://www.lego.com). They want to grow direct-to-consumer revenue in Q3, mentioned content production as the bottleneck, and asked about pricing for a 10-person creative team. Draft the proposal.
Once a draft proposal is on the table, ask Juma to revisit the pricing. The model cross-references the prospect's team size, the scope mentioned on the call, and the pricing structure in the project knowledge to recommend a tier with explicit reasoning. It also produces a short justification a senior reviewer can scan in fifteen seconds, and flags the next tier up with the condition that would justify it. This is the moment to stress-test a proposal before sending. Juma will defend the recommendation or change it if the prospect's situation has shifted.
Look at the proposal we just drafted. Recommend the right pricing tier with reasoning, and tell me what would justify moving them up a tier.
Before sending the proposal, ask Juma to predict the objection the prospect is most likely to raise. The model pulls from the call transcript or notes, the prospect's research summary, and any patterns in your past won-and-lost deals stored in the project. It returns the top objection, two backup objections, and a response script for each that the account lead can use live on the next call. This catches the conversation that would have happened anyway, before it happens in a way that costs you the deal.
What's the most likely objection this prospect will raise after reading the proposal? Give me a one-sentence response and a longer rebuttal I can use live on the next call.
A Juma Project is a shared space where the agency stores everything Juma needs to know about itself and the client. Create one project per client, add context as the relationship grows, and Juma uses what's relevant every time the team runs a flow. The more the team adds over time, the sharper every proposal, report, and follow-up gets.
Agency Brand Voice & Visual Identity
How the agency sounds in writing: tone, vocabulary, sentence rhythm, what to avoid. Plus the visual side: logo files (light and dark variants), brand colors as hex codes, accent fonts. With this loaded, every proposal comes out in the right voice and the branded PDF carries the right cover, header, and accent treatment from the first draft.
Case Studies Library
Past engagements that won, with the actual results and the context that made them work. Industry, client size, scope, and the headline outcome stat. Juma matches the right case studies to the prospect automatically. A B2B SaaS prospect gets the SaaS wins, a retail prospect gets the retail wins, and the social proof section never looks generic.
Pricing Structure
Tiers, services, scope examples, and the reasoning behind each price point. With this in the project, Juma recommends the right tier with a defensible explanation, and shows why a lower tier would underserve or a higher tier would overcharge. Without it, the model has to guess.
Past Proposals
Two or three of the agency's strongest past proposals as PDFs or HTML files. Juma picks up the structure, section order, headline conventions, and depth of detail the team uses, so new proposals look consistent with what the agency already sends. Without past proposals, Juma defaults to a sensible structure that may not match the agency's house style.
Add a short description to each knowledge item in the project info field so Juma knows what each file contains and when to use it. For example:
Writing a client proposal manually involves drafting from scratch, searching past work for the right case studies, formatting the document, and exporting to PDF. This Flow compresses the drafting work into a single session: Juma researches the prospect, pulls in matched case studies from the project, recommends a pricing tier with reasoning, and exports a branded PDF in one pass. Agencies that load the project knowledge once and reuse it across pitches report the largest gains.
The savings come from three places: skipping the blank-page phase, removing the manual case-study search, and producing a branded PDF without designer involvement. Strategy, taste, and final review stay with the senior account lead. Juma handles the drafting, formatting, and pricing math.
The output is a single-file HTML proposal exported as PDF, structured as seven sections: cover with the prospect's name and a tailored headline, the Challenge framed around the prospect's actual pain, the Solution with the recommended approach, Pricing with a fit tier and reasoning, ROI with headline metrics, Social Proof with matched case studies and logos, and Next Steps with a clear CTA.
Each section pulls from a different source. The Cover and Challenge come from the call transcript or notes. The Solution and Pricing come from the project's services and pricing knowledge. The ROI and Social Proof come from the case studies library. The Next Steps come from the agency's standard close. The PDF is mobile-responsive with thumbnail navigation and zoom controls, ready to send.
Yes. Upload two or three past proposals to the project as PDFs or HTML files, and Juma matches the structure, section order, headline conventions, and level of detail the agency uses. The uploaded references do not need to be perfect or recent. A representative sample of the house style is enough.
This matters most for agencies where a consistent document format is a brand signal in itself. If the agency uses specific section names, a particular cover format, or a fixed pricing-table layout, those carry over automatically once the past proposals are in the project. Without past proposals loaded, Juma uses a sensible default structure that works but may not match the agency's existing house style.
Yes. Fathom is the fastest entry point, but the Flow runs equally well from pasted call notes, a typed paragraph about the prospect, or even just a name and URL. Juma asks targeted clarifying questions to fill the gaps (team size, scope, competitive context) before drafting. The branded PDF output is identical regardless of input format.
Other meeting platforms are on the integration roadmap, and any platform that exposes a public share link or transcript export will work in the meantime by pasting the link or the transcript text into the chat.
Template tools fill blanks in a pre-built proposal structure. Juma drafts the proposal around the prospect. The Challenge section reflects what they said on the call. The Solution reflects what the agency actually does for clients like this one. The Pricing reflects the agency's structure applied to the prospect's situation. The output is a finished, branded asset, not a template waiting to be edited.
Template tools are useful when the goal is uniformity across many proposals. This Flow is useful when the goal is a proposal that reads like it was written for one specific buyer. Both stay in the toolbox. Juma does not replace document automation. It covers the case where a generic template costs the deal.
Connect the client's Google Ads, Meta Ads, and GA4 accounts, name the period, and get a branded multi-channel report with scorecards, benchmark context, and a prioritised action plan.
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
