MuninMunin
Sign inStart free
Use case · Sales

The follow-up nobody sent.

Not the deals you lost — the ones that just went quiet while everyone was busy. And the four-minute email that would have saved one, written on the Tuesday it was still warm.

  • Drafted from what was actually said
  • Never sends itself
  • Your pipeline, not a second one
  • EU-hosted
Anatomy

Nine days of silence, taken apart.

One deal, exactly as it sat on the Tuesday morning it was noticed. Everything on it came from something that had already happened — a call somebody logged, a page somebody read, a deadline somebody said out loud.

  1. 02Day 0Demo call · 42 minutes

    Logged by you: “needs it running before the new warehouse opens in March”.

  2. Day 1Proposal sent

    Three seats, March start, annual terms.

  3. 03Day 4They read it twice

    Then the pricing page, then the DPA. Nobody replied.

  4. 01Day 9Nothing

    No reply, no call, no note. The deal is still sitting in Proposal sent.

  5. Day 9 · 06:40Drafted for you

    Not a nudge. The March deadline, and the DPA they went looking for.

Harbourgate Lettings LtdProposal sent
Contact
Douglas Weir · operations
Value
£24,000 / yr
Owner
You
Source
Inbound · pricing page
Waiting for you
Re: Proposal — three seats from March
04

Douglas — you mentioned the warehouse opens in March, which really means a February start if the team is going to be comfortable with it by then.

I also noticed the DPA got a look. Happy to put our security summary in front of your legal people this week rather than after signature, if that is where this is sitting.

Shall I hold the March slot while you decide?

Your call notes, day 0 · proposal, day 1 · pages read, day 4
05Draft · nothing sent · 06:40
  1. 01
    Nobody remembered this.

    Nine days is roughly where a deal stops being warm. No one on your side did anything wrong — it simply never reached the top of anyone’s morning.

  2. 02
    It reads your own call notes.

    March is not a guess. You typed it on the day. What goes back to Douglas is what Douglas told you, in the words he used.

  3. 03
    The silence is a signal too.

    They opened the proposal twice and then went and read the DPA. That is not disinterest — that is legal, and legal is an objection you can actually answer.

  4. 04
    Every line traces to an event.

    A date, a note, a page. A sentence with nothing behind it does not get written, which is the reason this does not read like a template.

  5. 05
    At 06:40 it is still a draft.

    It goes nowhere until you have read it. There is no autonomous mode for the last step, and there is not going to be one.

What it cost you

Four minutes of judgement.

You spent

4minutes

One decision. Reversible.
You got

11deals read

Three sources each. Nothing sent.

The ratio is the product. Not fewer people — fewer of the steps that never needed one.

Where it came from

The deals that went quiet.

Nobody keeps this list. It is simply the deals whose last event is older than the stage allows — and on an ordinary Tuesday morning there are eleven of them.

The rule is yours: how long a stage may stay silent before it counts as quiet. It reads the pipeline you already keep, and does not invent a second one beside it.

outreach_list_due_followups( )this morning
  • Harbourgate Lettings Ltd · proposal sent9 days
  • Tollbridge Roofing · demo done12 days
  • Ashgrove Joinery · quote requested6 days
  • Calderwell Logistics · proposal sent21 days
  • Redhaven Groundworks · demo booked2 days
11 of 34 deals — none of them lost, all of them cooling
The honest part

What it won’t do.

  • 01

    Send on your behalf. Every follow-up waits in a queue with your name on it, however long you take.

  • 02

    Manufacture urgency. If nobody mentioned a deadline, it does not invent one to create pressure.

  • 03

    Work a list you bought. It follows up conversations you have actually had.

What it touches

Three modules, one pipeline.

  • 01CRM32 toolscrm_
  • 02Outreach17 toolsoutreach_
  • 03Conversations37 toolsconv_

Every step above is an ordinary tool call — the same ones your own agent can make, on the same endpoint. Reading the pipeline, drafting the follow-up and sending it once you say so are three calls on that endpoint, not three products.

Open source. Open protocol.
One stack, your terms.