Set up your client project: boilerplate, past releases, spokesperson bios, and brand voice
A Juma Project is a shared space where the team stores everything Juma needs to know about a client. Create one project per client, add context as the team learns more, and Juma uses what's relevant every time a flow runs. For press, this is what changes a generic release into one that sounds like the brand's prior coverage.
What to add
Boilerplate
The standard "About [Company]" paragraph that closes every release. With this in the project, Juma drops it in automatically and keeps it consistent across announcements, instead of paraphrasing it differently each time.
Past Press Releases
Three to five recent releases the team is proud of. Juma uses them to match the brand's tone, sentence rhythm, and structural conventions: how headlines are phrased, whether quotes lead the body or follow it, what's left to the boilerplate and what gets spelled out up top.
Spokesperson Bios
Titles, attribution lines, and one or two paragraphs of background for each leader the team quotes. This shapes how quotes are attributed and what register feels natural for each voice. A CEO quote reads differently than a head of sustainability quote.
Brand Voice Guide
How the brand sounds: formal or conversational, AP style or Chicago, what adjectives are on-brand and what's off. With this in the project, every release comes out in the right voice from the first draft.
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 contains and when to use it. For example:
- Boilerplate: "Standard About paragraph. Drop in at the end of every press release verbatim."
- Past Press Releases: "Reference set for tone and structure. Match the rhythm, not the literal copy."
- Spokesperson Bios: "Use to attribute quotes correctly and match each spokesperson's register."
- Brand Voice Guide: "Apply on every release. Use the words in the USE list and avoid the words in the AVOID list."
Ship a complete press kit in one session
Frequently Asked Questions
How much time does this Flow save compared to drafting a press release manually?
This Flow turns a half-day or full-day press kit into a single working session. Juma writes the release, the journalist pitch, the quote bank, and the social pack from one prompt, then renders the release as a polished PDF. The team reviews, adjusts the quotes with the spokesperson, and ships.
Manual press work typically involves drafting the release, writing tailored pitches per outlet, drafting alternate quote versions for the spokesperson to choose from, adapting the announcement into LinkedIn, X, and Instagram copy, and writing the internal note for the team. Each piece is its own deliverable. Strategy, taste, and judgment stay human: the comms lead still decides the angle, picks the quote, and signs off on the final pitch. Juma handles the drafting layer so the lead spends time on calls and revisions, not on a blank document.
What does a complete press kit include?
A complete kit covers six deliverables: the press release in inverted-pyramid format, an 80 to 120 word journalist pitch email, a quote bank with three to four variants per spokesperson, a social pack for LinkedIn, X, and Instagram, an internal launch note for the team, and a branded PDF of the release for distribution.
The release itself follows AP-style conventions: an SEO-friendly headline, a dateline, a lead sentence answering who, what, where, when, and why, two to three body paragraphs with embedded quotes, the boilerplate, and a media contact block. Quote attribution matches the spokesperson's public title. Each social piece is rewritten for its platform, not copy-pasted from the release. The PDF carries the brand's color palette and uses the boilerplate from the project.
Can Juma match the tone of our prior press releases?
Yes. Add three to five recent releases to the Juma Project for the client, and Juma uses them to match the brand's tone, sentence rhythm, and structural conventions. The output reads like the next release in the same series, not like a template.
The tone-matching layer covers how headlines are phrased, whether the lede is a single long sentence or two short ones, how quotes are introduced ("said" versus more elaborate verbs), and what level of jargon is acceptable for the industry. Without past releases in the project, Juma defaults to AP style and a neutral business register. With them in the project, the AI extracts a register the brand has already publicly committed to.
Does this Flow work for crisis statements, or is that a different Flow?
This Flow covers rebuttal and correction press releases through Step 6. For a full crisis sequence (sentiment monitoring across news and social, holding statements, stakeholder messaging, and post-incident analysis), the crisis communications flow is the right tool. The two are designed to hand off cleanly.
The boundary is straightforward. A correction or rebuttal release is one document responding to one piece of coverage. A crisis response is a sequenced communications plan across multiple channels and audiences over hours or days. If the team needs to draft a single statement, this Flow handles it. If the team needs to monitor what's being said, draft holding statements for different stakeholder groups, and coordinate a response across PR, social, and customer support, the crisis comms flow is the entry point.
How does the Google Workspace integration help, and what happens if Calendar and Gmail are connected?
Connecting Google Calendar lets Juma pull launch dates directly from the team's marketing calendar instead of asking. Connecting Gmail lets Juma drop the journalist pitch straight into the team's drafts folder, addressed to the right reporter, ready for review before send. Together, the two surfaces compress the press release loop from "find the date, write the release, copy the pitch into Gmail" into a single chat.
Each integration is its own connection: the team can connect Calendar without Gmail, or Gmail without Calendar. Drafts always land in Gmail for human review before send. No email goes out without a person clicking Send. Human review on every output. For teams that prefer to keep press work outside of email tooling, the prompts in Steps 1 through 6 work fully without any Workspace connection.