Systems that show their work
How we work

Four stages, real durations, and a first step that can end in no.

The stage names are ordinary on purpose. What is not ordinary is that the diagnostic is paid, fixed and allowed to recommend against building.

01The four stages
  • Diagnose10 working days (Revenue) · 2 weeks (Operations, Investment)We map the workflow and the information inside it, against your real data — not a questionnaire. You get a written teardown: what breaks, where it breaks, what it costs when it does, and a build/no-build verdict.

    Fixed fee, credited in full against a build booked within 30 days — priced per surface, below. The fee is not contingent on the verdict, which is the only reason the verdict means anything.
  • Build4–8 weeks (Revenue) · 6–10 weeks (Investment)Fixed scope, agreed in writing before we start, built in your environment on your accounts. Scope changes are a conversation and a new line, not a silent extension.

    You get the system, the code, the accounts, the evidence files and the documented playbook.
  • Operate — then transfer, or keep us running itHandover: up to 90 days · Build & Run: monthly, for as long as you want itWe run it alongside your team. On the handover shape we train the person who will own it and leave, and it ends when a named person on your side runs it without us. On Build & Run we keep operating it month to month.

    You own it either way — the repository, the accounts, the evidence files. What varies is who operates it.

    Running it is about 25 hours a month: the deliverability watch, the send ramp, reply triage, and a mailbox pool that degrades and has to be replaced 15 to 30 days before you need it. Handover is the right call when you have someone who will do that every week. Most teams do not.
  • MaintainMonthly, optionalFormat and rule changes, new sources, a quarterly review. Optional means optional — most clients do not need one, and we will tell you if you are one of them.

Every build ships with an operating view — a view of the system running, in your accounts, from the day it goes live. What it did, what it flagged, and the evidence behind each. A window onto the machine, not a substitute for one.

02Three commitments

These are the parts a competitor cannot copy by rewording a page.

  • The diagnostic can end in “no”Including “this does not need AI”. We have designed the commercial terms so that saying no costs us nothing, because a recommendation you cannot trust is worth less than no recommendation.
  • We tell you how often the system gets it wrongMeasured on your data, and which kind of case it gets wrong. Nobody in this category publishes that. We think it is the only number that matters.
  • When we hand over, nothing depends on usYou get the repository, the accounts in your name, the evidence file for every decision the system made, a written playbook, and a named person on your side who has run it with us. Nothing depends on us being reachable.

What it costs to find out

One paid, fixed-scope step, credited against the build. No free discovery call disguised as a pitch, and no proposal that takes three weeks to arrive.

Talk to us
  • ICP Coverage AuditRevenue systems · 10 working days · $1,500
  • Monitoring & Data DiagnosticFinancial & investment firms and operations · 2 weeks · $2,500
  • GTM Systems ReviewRevenue systems · two weeks · $3,500
  • GTM Build AdvisoryThe Review, then six to eight weeks alongside your engineer. A weekly working session on what they built that week, async review of list rules, sequence copy and deliverability configuration before anything sends, and the training and runbook. Your people build it. We are accountable for the design and the review, not for meetings booked. · Quoted on the call; the Review fee is credited in full
  • BuildQuoted after the diagnostic
  • Build & RunThe same build, then monthly while we operate it · Quoted on the call