Jacob
Founder · Operator
Built outbound systems for 150+ teams. Writes the agent training prompts, runs the install kickoff, lives in client Slack for six months.
ABOUT · BUILT BY HUMANS
We install instead of rent.
ReplyArc exists because outbound shouldn't be rented. The domains, the inboxes, the prospect data, the playbook — all of it lives inside your business after the install. Below: the thesis, the timeline, the people behind it.
THE THESIS · WHY NOW
Cold outbound was built for agencies.
For ten years, “outbound” meant paying an agency to do it in someone else's account. The agency owned the domains, the inboxes, the prospect data, the playbook — everything that survived a churn.
That model worked when the unit economics were ad-buyer-good and the contracts were multi-year. It stopped working the moment LLMs collapsed the cost of personalization and made “your voice, your ICP, your brand” a one-week prompt-and-train problem instead of a six-month consulting engagement.
Today the right pattern is installation, not subscription. The agents live inside your org. Your team learns the system in 60 minutes. You keep the leverage when we leave. What we sell is the install + six months of supervised operation. After that we're optional — and that's the whole point.
TIMELINE · HOW WE GOT HERE
Five years of installs, then a brand.
Built in public on three live customer accounts before the website existed. The brand caught up after the system did.
- 2018 — 2022
Five years inside other people's outbound
Ran outbound for 150+ teams as an operator and consultant. Watched the same pattern: clients paid agencies $8-15k/mo, agencies kept the domains, the inboxes, the prospect data, the playbook. Clients churned and started from zero.
- Q1 2024
First install, no website
Built the v0 install for a single client — a 60-person fintech tired of their agency. They paid a one-time fee and got a system inside their org. They still run it today, six months after our support window ended.
- Q3 2024
Agent stack solidified
ICP + Copywriter + Reply + Lead-list + Sequencer agents converged into a single deployment. Phone-home bridge moved oversight to ops without giving ops write access to client DBs.
- Q4 2024
Three installs running
B2B SaaS, an agency, and a Series-A product company — each on their own deploy, their own keys, their own brand. The thesis worked end-to-end.
- Q2 2025
Public launch
Marketing site live. Cohort-based install cadence opens — six spots per quarter so the team can install deeply, not at volume.
TEAM · SMALL ON PURPOSE
Four people. By design.
An install is a high-touch object. We staff to fit the work, not to fill a roster.
Operator — TBD
Install lead
Senior operator — owns the day-by-day install execution, deliverability, and post-install support cadence. Operator pre-launch hire.
Engineer — TBD
Systems engineer
Owns the agent stack, the bridge, and the ops control plane. Migrations, encryption-key rotation, retries — the unsexy reliability work.
Brand — TBD
Brand · Design
Owns the marketing surface, the editorial voice, and per-install whitelabel review. Sharp corners, real photography, no decoration.
Operator note · Team placeholders pending photo + bio sign-off. Founder bio is live.
JOIN US
Want to work on this? Tell us.
We hire for taste and intent. If you're an operator, engineer, or designer who has felt the same frustration with the rented-outbound model, drop us a line. No JD, no portal — just an email and a recent thing you're proud of.
20 MIN · NO PITCH
Book the call.
Twenty minutes. We'll tell you, honestly, whether an install is the right call right now — or whether you should keep renting an agency for another quarter.