Understand the current reply workflow
Leads That Bloom keeps prospect context and recorded replies with the prospect. The current daily reply workflow uses a Claude/Cowork skill to read an authorized mailbox, record relevant replies in the workspace, and prepare drafts. The skill prepares drafts for human review; the recipient’s actual conversation guides what the person decides to send.
Access and setup are currently invite-only, and available assistance depends on the workspace configuration. The public sample only illustrates the decisions. Its controls do not read a mailbox, run Claude, create a draft in an account, or send email. A person reviews the actual conversation and decides what to send.
Read the full conversation first
Find the most recent real reply and read the earlier exchange it answers. A prospect may be accepting a small example, asking about scope, correcting a website observation, or explaining that they already have a solution. Those are different conversations and should produce different next steps.
A short snippet can omit the important part of a message. Check the full thread before approving wording, especially when the recipient refers to a previous promise or says “as discussed.” If the conversation is missing or unclear, pause the draft and recover the context rather than filling the gap with a confident guess.
Keep confirmed facts separate from suggestions
Compare each statement in the draft with something the person wrote, a saved note, or source evidence you can check. A website observation can support a question about an inquiry form. It cannot establish lost revenue, prove that an internal process failed, or show that a recipient agreed to a service.
Read offers and commitments especially carefully. Do not invent a price, deadline, scope, or agreement. If the person asks about something your team has not decided, explain what you need to learn or discuss. Claude-assisted wording is a starting point for a response, not confirmation of a business decision.
Choose a useful next action
Answer the recipient’s question before introducing another offer. Keep the reply short enough that they can see what happens next. If they asked for an example, decide what example you can provide. If they requested a later conversation, record that request and its reason beside the next step.
A reply changes whether the original cold outreach should continue. Respect declines, unsubscribes, and do-not-contact restrictions. Keep prepared, reviewed, and sent states distinct: a suggested response or a saved Gmail draft is not delivery confirmation. After the human decision, keep the next action with the prospect so another team member can pick up the thread.
Fictional example
A fictional reply that changes the offer
Willow Studio is fictional. This example demonstrates review judgment and does not represent an email sent to a real prospect.
- Sample reply
- “We already use a project brief. Could you show what you mean by a qualification handoff?”
- Context to keep
- They have a brief already; the question is about the next step after someone submits it.
- Suggested response to review
- “Thanks, that helps. I mean the short note that tells the person reviewing the inquiry what to check next. I can share a simple example if useful.”
- Claim to remove
- “Your current brief is not qualifying leads.” The recipient’s reply does not establish that.
- Next decision
- Check that the example exists, review the wording, and decide whether to send it.
Review checklist
- Full thread read, including the latest real reply
- Recipient’s actual question answered first
- Website claims traceable to a source or removed
- Scope, price, and timing are confirmed rather than invented
- Any promised example can actually be provided
- Reply, decline, unsubscribe, and do-not-contact context respected
- Draft status and the next human decision remain clear
Common questions
Does the public sample generate or send a reply?
No. The example is fictional and only changes what is displayed on the page. The current authorized Claude/Cowork reply workflow prepares drafts for human review.
What if the suggested response does not fit the thread?
Revise or hold it. Return to the original messages and the saved business context. A fluent answer is not useful if it responds to a question the prospect did not ask.
Talk to us about your workflow
Tell us what you sell and how you research prospects today. Access is currently invite-only.
Request access