Two people seen from behind at a desk in the evening, one pointing at a large screen with a pen, an orange band around a closed notebook
AI-native engineering for tech companies

Put customer data to work.

We connect customer, product and billing data in systems you own. Campaigns and customer follow-up run from the same record.

Built for production use, in accounts you control.How it starts

Clients include

  • Granola
  • BLOCKS
  • Reducto
  • Corti

AttioFounding Expert Partner

The customer record

Each customer has one record.

Product use, plan, ownership and the decisions already made sit on one record, ready before a call.

AccountUpdated today

Northwind Labs

Team plan · 42 of 50 seats · renews 14 December

Product use by week

Owner
Maya, account executive
This month
Three new signups

Last agreed decision

New trials from this company go straight to the account owner. Agreed with the revenue lead on 12 August.

Demo data.

Approvals

Routine updates run on their own.

Prices, contracts and anything a customer sees wait for a person to approve them.

OperationsTue 10:12

Done automatically

Three signups joined to Northwind Labs.

Received
Three trials from the same company
Done
Matched to the account, owner told
Why automatic
Low stakes and easy to undo
OperationsTue 10:40

Waiting for you

Renewal quote for Halden Systems.

Prepared
Quote with usage and billing context
Needs
Approval from the revenue lead
Why it waits
It changes a price the customer sees
ApproveEdit

Demo data.

Decisions

Decisions are saved with the reason.

When your team agrees how something should work, the system applies it the next time the case comes up, with a note of who agreed it and why.

A printed contact sheet on a desk at night, each frame one account’s product use by week, the rising accounts circled in orange wax pencil and a falling one crossed out

Campaigns run with account research, lead capture and follow-up connected, and responses sit next to product activity and billing.

The work we take on
Campaigns and go-to-market
Marketing operations
Revenue operations and CRM
Product and customer operations
Attio Founding Expert Partner
Attio

Cloud cost savings

BLOCKS went from zero to $10M ARR in its first year.

We partnered with their go-to-market team to build and run the revenue system, from outbound to inbound lead routing in Attio.

Annual recurring revenue
$10M
From zero
How long it took
1 year
Its first year

We build the CRM, data and workflows your teams share.

Marketing, revenue and customer teams work from the same information.

Built for

CRM implementation on Attio

Rebuild the CRM around accounts, leads and opportunities, migrate the records and get the team using it while selling continues.

Built for

Product data and account routing

Connect users, workspaces and companies. Route qualified signups to the right sales or success owner.

Built for

Answers from your own data

Bring data together so the team can ask business questions and inspect the records behind the answer.

Built for

Account research and outreach

Prepare account research and first-contact drafts, with source context and approval before sending.

Work for tech companies.

What clients say

“Super fast replies, highly competent people, and a smooth collaboration throughout.”

Niklas Rabanus, Founder, ColdIQ

“We now have the exact CRM we have been dreaming of for years.”

Greg Berry, Owner, The Sport Shirt
Seen from above, a business model sketched in pencil as boxes and lines on a large sheet, with a hand holding the pencil

Where it starts

Tell us what you want to change.

Book a free 20-minute call with Alex or Josh. Bring a project or a problem you want to work through.

We discuss how the business works today, then propose the implementation, delivery stages and first useful milestone.

How the first milestone works Book a call, opens the 20-minute booking page in a new tab

Before we start

What does it cost?

We agree the implementation scope, fee and milestones before starting. Optional ongoing service is priced separately, according to the work, volume and support it covers.

Do we have to take the ongoing service?

No. You can commission the implementation with documentation and a handover, then run it with your own team or another provider. If you choose our ongoing service, we agree its scope, fee and start date separately.

Will we have to replace our tools or team?

We keep useful tools and replace the brittle connections between them, including Zapier or Make workflows that have become hard to trust. We migrate in stages while your team keeps running the business.

Who owns the system?

You own your data, client-specific code, configuration and documentation. The repository, database and services run in accounts you control. You can develop the system with us or another team. Shared components and third-party licences are documented separately.

How do you keep up as our plans change?

With the ongoing service, bring changed launch dates, audiences or account rules to the shared Slack channel. We update the affected workflows and retain the decisions for future work. Monitoring, maintenance and improvements follow the agreed scope.

How soon will we see working software?

Programmes may run over 30, 60 or 90 days, with useful systems introduced along the way. We agree the first live milestone after reviewing the scope, access and data.