Keep the relationship. Lose the blank-page workload.
A HeyReach integration that turns conversation history, tone, relationship stage and enrichment context into carefully prepared DM drafts—leaving judgment and the final send with a person.
01 / CONTEXTRelationship contextHeyReach thread synced · private text not shown02 / INTERPRETRelationship stageWarm reply · low-pressure next step03 / GROUNDEvidenceApproved public facts + account instruction04 / PREPAREDraftPrepared draft enters the review queue05 / PERSONHuman review and approvalA person edits, rejects or approves the draft. 06 / MANUAL SEND · PERSON-ONLY ACTION
Manual sendSending occurs only after a person confirms whether and when.
InputConversation summary and retrieved facts
System workRelationship stage, tone and timing interpretation
OutputFitted draft in a review queue
Human boundaryHuman edit, approval and manual send
Proof classinternal-live
PLANNING ASSUMPTION / INTERACTIVE
Model the funnel before the walkthrough.
Change the account count and conversion assumptions to see the funnel narrow. This is capacity planning—not a forecast, send control or performance claim.
Planning assumption: $100/account/month, 200 messages/day/account and 30 planning days/month. A person stays in control of account settings, review and send decisions.
Current modeled result36
modeled sales from 120 calls · planning assumptions, not a forecast
MODELED FUNNEL / 20% PlanningValues update from the controls
Account health, LinkedIn/HeyReach limits, audience fit, offer quality, conversation quality and human sales execution can reduce actual performance. The figures are planning assumptions, not guaranteed outcomes.
Synthetic demonstration using public-safe example data
Relationship-to-draft review queue
Synthetic demonstration. Internal-live mechanism; no private conversation is shown.
Inspect one public-safe record as it moves from context and evidence to a fitted draft, human edit, approval and manual-send boundary.
Conversation summary and relationship stage are visible before any draft is trusted.
Retrieved fact: public launch windowSystem interpretation: warm replyHuman instruction: no hard CTA
Conversation summary
Recent reply asks whether timing fits an upcoming launch window.
Relationship stage
Warm reply, not ready to book. Keep the next message low-pressure.
Tone/timing instruction
Brief, useful and no hard CTA.
ContextConversation summary and relationship stage are visible before any draft is trusted.
DraftWhy this draft? Evidence chips explain the sources and interpretation behind the proposed reply.
Human editThe operator edits before approval. The diff is the proof that judgment remains human-owned.
Manual sendThe final send remains manual. The system can record state only after a person confirms the action.
RECIPIENTAura Forge
STATUSUsed and optimised internally · being prepared for ForgeOS launch
TIMEFRAMEOngoing internal optimisation · launch integration in development
COSTInternal R&D · no client price
THE RECIPIENT
Built around a real operating constraint.
Built for an internal outreach workflow where relevance mattered more than unsupervised volume.
Meaningful conversations were spread across long histories and changing relationships. Writing every response from scratch protected quality but consumed the time the system was meant to create.
THE CONSTRAINTS
Useful only if it respects the messy parts.
01
A new draft had to respect previous messages instead of restarting the relationship.
02
Tone and offer had to reflect the current relationship stage and available evidence.
03
Private conversations could not become public proof or be sent without human judgment.
THE SYSTEM
A complete path—not another loose collection of tools.
01HistoryPrevious messages and relationship context
02EnrichRole, company and relevant evidence
03InterpretTone, stage, timing and instruction
04DraftOne context-built reply
05ReviewA person edits and approves
06SendManual action; state returns to CRM
+
HeyReach conversation synchronisation and durable conversation history.
+
Relationship-stage analysis, enrichment context and account-specific instructions.
+
A review queue that prepares missing drafts and preserves edited text.
+
A manual send boundary with CRM state updated after the operator confirms sending.
WORKING EVIDENCE
The claim sits beside the thing that supports it.
The internal CRM exposes synced conversations, relationship stages and draft states.
Drafts can be queued, reviewed, edited and marked sent without automating the final DM action.
The operating system preserves manual-send status and avoids exposing private message content publicly.
