Second service line

AI that removes work, not AI that adds a chatbot

Revenue teams lose a startling number of hours to work that is genuinely mechanical: researching accounts, tidying CRM records, assembling the same report every Monday, rewriting the same proposal. That's where this belongs.

What we build

Systems with an obvious hourly saving

We only take builds where you can point at the hours being spent today. If the saving is speculative, the project usually isn't worth either of our time.

Prospect research

Give it an account list; get back a research brief per company — recent hiring, site changes, funding, tech signals, plus a written reason to reach out. This is the system that powers our own outbound, which is why we know what it saves.

CRM hygiene

Deduplication, enrichment, stage-consistency checks and flagging deals that have gone quiet. Forecasting is impossible on a dirty pipeline, and nobody enjoys cleaning it by hand.

Reporting that writes itself

The Monday revenue summary assembled from your own data, with the commentary drafted — what moved, what stalled, what needs a decision. A human still approves it before it goes out.

Proposal and follow-up drafting

Draft proposals, recap emails and follow-ups from the call notes and the deal record, in your voice. Drafts, always — nothing sends to a customer without a person reading it.

Inbound triage

Incoming enquiries scored, routed and enriched before anyone opens them, so the good ones get answered fast. Speed of first response is the most under-rated conversion lever in B2B.

Internal knowledge answers

An assistant that answers from your own documentation, pricing rules and past deals, so a new AE doesn't have to interrupt someone senior to find out what's standard.

How it's priced

Fixed price per build. You own it.

Scoped as a specific workflow with a defined before-and-after, not an open-ended "AI transformation" engagement.

  • A paid scoping session first. We map the workflow, agree what the system will and won't do, and you get that document whether or not you continue.
  • Fixed build price, agreed up front, with a working version in your hands before final payment.
  • You own the system and the code. No platform lock-in, no per-seat rent on something we wrote once.
  • Running costs are yours and visible — model usage billed to your own account, so you can see exactly what it costs to run.

What we'll talk you out of. Automating a process that's broken rather than fixing it. Anything that would send to a customer without human review. And any build where the honest answer is that a spreadsheet and a rule would do the job for nothing.

Why this exists alongside pipeline

The same research engine, pointed inward

Our outbound work runs on an internal system that researches accounts, drafts messages and tracks what happened — because that's what makes pipeline work possible at this price. Automations is that same capability, built for your team's own workflows instead of ours.

That's also why we only take builds with a clear hourly saving already visible. We're not pitching a category ("AI transformation"); we're pointing at a specific Monday-morning task and replacing it with a system that does it in minutes, with a person still approving the output before anything ships.

What we won't build

A system that emails a customer without a human reading it first. A "smart" layer over a process that's actually broken and needs fixing, not automating. Anything sold as a subscription for something that's really a one-time build — you own the code, so ongoing rent isn't the model.