ReplyMark CRM

The problem

ReplyMark is one backend selling under three storefronts — PR pitches, off-market deal flow, and done-for-you cold email. Outbound only works when every message is personalised and watched: tailored emails earn roughly twice the replies of generic ones, and B2B contact data decays around 22% a year, so attention is the whole game. But attention doesn’t scale. Run three engines out of inboxes, spreadsheets and a sea of browser tabs and the operator becomes the bottleneck — drafts wait, replies get missed, and the numbers live in five places at once.

The approach

We built the Command Centre as the single surface the whole business runs on. n8n workflows prospect, draft, and watch for replies; Claude writes each message in the client’s voice; Supabase holds clients, pipeline and approvals. Everything that would otherwise auto-send instead lands in one human-in-the-loop queue — the operator reads, edits, and approves, and only then does it go out from a warmed domain. The dashboard folds revenue, client health, pending approvals and lead horizon into one view, so running the agency is a glance and a few clicks, not a morning of admin.

Outcomes

• One operator runs all three engines from a single queue — no second tool, no spreadsheet
• Every outbound message is human-approved before it sends; nothing automated goes out unseen
• MRR, pipeline, approvals and client health in one screen — the morning review is a glance
• Reply detection routes responses back to the inbox, so warm leads never sit cold

Retrospective

The console is the moat. Anyone can wire an AI to send email; the hard, valuable part is the approval layer that keeps a human in the loop without slowing them down. Making “read, tweak, approve, send” feel like two seconds per item is what lets one person credibly run three outbound businesses at once — and it’s why the product behind every storefront is the same.