We rented cold email tools for three years. Then we built the one we needed.
FoxReach began as the sending backend for our own outbound work at a GTM automation agency. Seven people build it, run their own campaigns on it, and now offer it to you.
What outbound ran on, year one to year three
- A warmup service
- A sequencer
- An inbox manager
- A verification tool
- An enrichment spreadsheet
- Automation glue between them
One backend. One API. FoxReach.
Why we built it
Year one
Outbound for clients, on rented tools
We ran cold email for SaaS teams and agencies. Warmup in one product, sequences in another, replies in a third, verification and enrichment in a spreadsheet in between.
Year two
Every quarter, a new tool
Each one fixed one thing and broke another. The stack kept changing and the workflow underneath it never got simpler.
Year three
The models moved faster than the tools
What an outbound workflow could do changed with every model release. The tools still expected a person clicking through a dashboard. None of them were built for an agent to drive.
Today
Our own backend, now open to you
We built the sending layer we wanted for our own campaigns, then for the teams we worked with. That backend is FoxReach.
What we hold to
Three rules that decide what gets built and in which order.
- Agents first, dashboard second
- Every feature ships through the API before it gets a screen. The MCP server, SDKs, and webhooks are the product; the dashboard is one client of it.
- Deliverability is the product
- Warmup is built in on every connected sender. Inbox rotation, bounce handling, and reply monitoring are not add-ons you pay for later.
- We are the first customer
- Our own outbound runs on FoxReach. When something breaks, it breaks for us first, and it gets fixed before it reaches you.
The seven people behind it
Everyone here has run cold email for a living, which is why the product argues with itself less than most.
Runs FoxReach and Buildberg, the automation agency it grew out of. Spent six years building outbound systems for SaaS teams and agencies before deciding the sending layer had to be his own. Wrote cold.md, the open spec for agent-driven outreach.
Owns how people find FoxReach and what happens after they sign up: onboarding, campaigns, and the lifetime deal. The numbers he reports decide what gets built next.
Turns the roadmap into shipped releases: scoping, specs, and the public feature board. Usually the first person to try a build on a live campaign before anyone else sees it.
Co-founded Buildberg and led its analytics services sales. Brings the buyer side to FoxReach: which promises land on a sales call, and which ones a customer will hold you to a year later.
Ran client campaigns on the tools FoxReach replaced. Now owns sequences, deliverability practice, and the handoff between the inbox and the CRM.
Co-founder of Buildberg with a data infrastructure background. Measures what actually lands: inbox placement, reply rates, and the reporting that tells us whether a change helped.
Talks to every team evaluating FoxReach. Objections from those calls become roadmap notes, and closed deals become the onboarding checklist.
Run your outbound on the backend we built for ours
Free plan, no card. If you would rather talk first, the contact page reaches the same seven people.