Skip to main content
Pipe & Signal

GTM engineering for agencies and B2B SaaS

Booked meetings from a lead machine you own

We build the system that finds your buyers and spots when they are ready. It gives the right rep a reason to reach out. It runs as code in your repo, so it stays yours.

Prices on the page. Fixed quotes by email. No sales call needed.

Built for 2 kinds of team

Agencies that need more build capacity

You sell outbound and GTM systems. We build them under your brand, so you take on more clients without a new hire.

B2B SaaS founders at hire 3

You have founder sales, an SDR and an AE. Now you need the machine behind them. We build it as code your team owns.

Signals in, booked meetings out, in 7 steps

Each step is a job you can see, test and change. Use the whole machine or start with the step that hurts most.

  1. 01

    List

    Find the accounts that fit

    We build a list of accounts that match your ICP: size, market, tech stack and stage.

    Out An account table you can filter and re-run.

  2. 02

    Enrich

    Get the right people and verified emails

    A waterfall asks one data source after another until it finds the person and a verified email. Each source is called only when the one before it finds nothing. The cost log shows what each call cost.

    Out Contacts with a role, a verified email and a source for each field.

  3. 03

    Signals

    See who is ready to buy now

    Jobs watch for funding rounds, new hires, a new exec and visits to your pricing page.

    Out A dated signal on each account, with the source link.

  4. 04

    AI research

    Give each rep a reason to reach out

    An LLM reads the account and the signal. It writes one line on why to reach out now, and a score.

    Out A score and a one-line reason on each account.

  5. 05

    Route

    Send each lead to the right next step

    Rules send each account to its CRM owner, a Slack alert or a sequence. Nothing sends until a named person approves it.

    Out An owner and a next action on every lead.

  6. 06

    Send

    Land in the inbox, not in spam

    We set up domains, warmed inboxes, SPF, DKIM and DMARC, and connect your email and LinkedIn tools.

    Out Sending infrastructure that meets the mailbox provider rules.

  7. 07

    Report

    See replies, meetings and pipeline in your CRM

    Replies, meetings and pipeline flow back to the CRM. A weekly summary goes to Slack.

    Out Pipeline you can trace back to the signal that started it.

See 8 example workflows

Own the machine, not a rented table

Many GTM builds live in a vendor table that your plan limits. Ours call vendor APIs direct from a repo you own. Fewer tools, more ownership.

Your team already works in Clay or n8n? We build there too. You pick the tool. We tell you the cost trade-off in the quote.

Clay vs Claude Code: when each wins

What you own at handover

  • A repo

    The code lives in your GitHub. You can read it, change it and run it without us.

  • Scheduled jobs

    Each step runs on a schedule you can see and change.

  • A database

    Accounts, contacts, signals and scores sit in a database you control.

  • Tests

    Tests cover the routing rules, the scoring and each vendor call.

  • A cost log

    Each run logs what it spent per vendor, so a bad run is easy to spot.

  • A runbook

    Plain steps to run, pause, change and debug the machine.

Vendor accounts, API keys, domains and inboxes are in your name from day one.

Pick the build that fits your team

Lead-gen, outbound and marketing agencies

S to L

White-label build

Sell lead machines under your brand. We build them; your client sees only you.

from $3,000£2,400 per build

  • One workflow, priced by size: S from $3,000, M from $5,000, L from $8,000.
  • Work under NDA. Your brand on every handover document.
  • Code in your repo or your client's repo, in Clay, or in n8n. You choose.
  • A runbook and a recorded walkthrough your team can resell.

Outcome You take on more client work without a new hire.

Seed to Series B B2B SaaS

L

Owned lead machine

All 7 steps, from list to report, built as code in your own repo.

from $12,000£9,600 per build

  • List, enrichment, signals, AI research, routing, sending and reporting.
  • A repo in your GitHub with scheduled jobs and a database.
  • Direct calls to vendor APIs, with no per-row platform fee from us.
  • Tests, a cost log for every run, and a runbook.

Outcome You own a working lead machine and the code that runs it.

B2B SaaS teams with inbound demand

M

Inbound routing sprint

Every form fill gets enriched, scored and sent to the right rep in Slack.

from $5,000£4,000 per build

  • Form to enrichment to score to owner, with a Slack alert to the rep.
  • A build target of 60 seconds from form submit to the Slack alert.
  • Owner rules in code or in your CRM, with tests for each rule.
  • A CRM clean-up pass: duplicates merged, stale contacts flagged.

Outcome Hot inbound leads reach a rep while the buyer still has your tab open.

Indicative prices. You get a fixed quote after we read your scoping brief. Tool and data costs are extra and you pay them at cost.

See the prices

Get from brief to a working machine in 5 steps

  1. 01

    Send a scoping brief

    Tell us what you sell, who you sell to and what you use now. No call needed.

  2. 02

    Get a fixed quote

    We reply by email within 2 working days with questions or a fixed quote. Larger builds start with the paid diagnostic.

  3. 03

    Approve a pilot run

    We run each step on a small sample first and show you the output and the cost. You approve before the full run.

  4. 04

    Take the handover

    You get the repo, the runbook and a recorded walkthrough. Accounts and keys are already in your name.

  5. 05

    Run it yourself, or have us run it

    Run the machine in-house, or keep us on the monthly run and improve plan.

Stay in control of spend and sends

Pilot runs first

Each step runs on a small sample before the full batch. You see the output and the cost first.

Approval gates

Nothing sends until a named person approves it.

A cost log

Every run logs its spend per vendor. A run that costs too much stops.

Your accounts

Domains, inboxes, API keys and data sit in your name from day one.

Questions buyers ask

What is a lead machine?

A lead machine is the system behind outbound and inbound sales. It builds a list and finds people with verified emails. It watches for buying signals and scores each account. Then it routes, sends and reports pipeline back to the CRM.

Do we own the code?

Yes. The code goes in your repo from the first commit. Vendor accounts and keys are in your name. You can run the machine without us.

Do you only build in code?

No. Code is our default, because you own it and it has no per-action platform fee. We also build in Clay or n8n when your team works there.

Who pays for tools and data?

You do, direct to each vendor, at cost. We add no margin. The pricing page lists public prices for common tools.

Do you promise a meeting count?

No. Meetings depend on your offer, your market and your list. We commit to the scope in the fixed quote, and we show you the reply and meeting data in your CRM.

Will my agency's client see your name?

No. White-label work happens under your brand and under NDA. We talk to your client only when you ask us to.

Do we need a call?

No. Send the scoping brief. We reply by email with questions or a fixed quote.

Get a fixed quote for your lead machine

Tell us what you sell, who you sell to and what you use now. We reply by email within 2 working days.

Send a scoping brief