The campaigns already work. The tooling around them is a spreadsheet. We build the layer an outbound or lead-gen agency runs on: prospects in from Apollo or Clearbit, sequences out over email, SMS and WhatsApp, replies qualified by AI, margin visible per client.
Free call · Fixed-scope quote within 48h
Four shipped products. Two of them are now sold to other agencies.
Apollo.io syncs prospects in, admins reconcile bookings against disputes with a five-state pill and an audit trail, and each role sees exactly its own numbers. Nine screens, four roles.
See it in XDRhubEach workspace runs its own Twilio number, templated campaigns go out at scale and an AI assistant qualifies replies the moment they land. Credit-based plans from $97 to $997.
See it in Tedy.aiBuy a number, import a list, run bulk SMS and email from one composer with one inbox and one ledger. Three clicks from signup to a working number.
See it in MessageWizImport a lead from Clearbit or Apollo, drop them into a four-step nurture sequence, watch four fixed pipeline stages and three KPIs.
See it in StaticEvery one documented end to end: the problem, the build, the result. Filter the case studies.
A four-role analytics platform that replaced a Friday-afternoon Google Sheet. Apollo.io syncs prospects in. Admins reconcile bookings against client disputes. Account managers see…
Read the case study
A multi-organization WhatsApp campaign platform, every workspace gets its own Twilio number, an AI Lead Assistant qualifies replies the moment they land, and a credit-based plan keeps the…
Read the case study
A B2B messaging SaaS that lets a small team buy a phone number, import a contact list, and run bulk SMS + email campaigns from one inbox, without stitching Twilio, SendGrid, and a…
Read the case study
A CRM for solo founders and small sales teams that don't need Salesforce. Import a lead from Clearbit, Apollo.io, or paste it in. Drop them into a four-step nurture sequence. Watch the…
Read the case studyAn outbound agency lives and dies on whether a booked meeting counts. When a client disputes one, the answer used to be a Friday afternoon in a Google Sheet. XDRhub made it a lookup: every booking carries a five-state status (attended, no show, declined, not a decision maker, unresolved) with a timestamped audit trail, and the numbers the client sees are the numbers the agency computes commission from.
That single ledger is the point. BDR commissions, agency expenses and client margin are three views of the same rows, so nobody reconciles anything by hand and every dispute has a record.
Whether the leads come from Meta lead forms, a cold WhatsApp campaign or an inbound page, the economics are decided in the first few minutes after a reply. We build the machine that catches them: instant follow-up over WhatsApp, SMS and email from one composer, an assistant that qualifies replies while the team sleeps, routing with escalation when nobody answers, and attribution from click to booked call.
Tedy.ai runs this at scale for agencies, with a separate Twilio number per workspace and WhatsApp’s template and opt-in rules built to rather than around. MessageWiz does it for SMS and email in one inbox. We do not run the ads themselves; we build and operate everything downstream of the click.
Most agency tooling is the missing layer on top of a CRM that is fine: reconciliation, commission, margin per client, client-facing reporting you can hand over without editing first. We only replace a CRM when the thing you need is a different shape. Static is that case, a nurture-first CRM for founders and small teams, with Clearbit and Apollo enrichment on the way in and scheduled sequences on the way out.
Connecting the tools you already pay for is most of the work: Apollo.io and Clearbit for prospect data, Twilio for WhatsApp and SMS, Stripe for billing, your calendar and your CRM. If it has an API we can almost certainly wire it in, and we tell you early when it does not.
Because roles are separated from the first build, an owner, an admin, a rep and a client each get their own screen and permissions. That is what makes white-label client portals a common add-on once the internal tool is stable, and it is why two of the four products in this lane are now sold to other agencies as SaaS.
Multi-tenancy is designed in from the start: one operator account, many organisations, many numbers, one Stripe billing relationship per tenant.
Fixed scope, a demo every Friday, and a first clickable version around day 7. The full process is on the home page.
For outbound and lead-gen agencies running delivery on spreadsheets, disconnected tools and manual reporting.
3 to 5 wksAdd-onsAI reply qualification · speed-to-lead routing · white-label client portals · Meta lead form capture
Fixed scope · Fixed price
Demo every Friday
Everything else gets answered on the scoping call.
Usually we build around it. If HubSpot or Pipedrive is working for your reps, we leave it and put the missing layer on top: reconciliation, commission, margin per client. We only replace a CRM when the thing you actually need is a different shape, which is what happened with Static, a nurture-first CRM for teams that were never going to run Salesforce.
That is most of the work. Apollo.io and Clearbit for prospect data, Twilio for WhatsApp and SMS, Stripe for billing, your calendar and your CRM. We have shipped all of these into production. If a tool has an API we can almost certainly wire it in, and we will tell you early if it does not.
The follow-up. We build and operate everything downstream of the click: capture from Meta lead forms or landing pages, follow-up over WhatsApp, SMS and email, AI qualification, routing and reporting. Most clients keep their media buyer and hand us the system the leads land in.
Yes. Tedy.ai sends templated WhatsApp campaigns through Twilio with an AI assistant qualifying the replies, metered on credit-based billing. WhatsApp has real template and opt-in rules and we build to them rather than around them.
Yes, and several agencies do. We separate roles from the first build so an agency owner, an admin, a rep and a client each see a different screen with their own permissions. White-label client portals are a common add-on once the internal tool is stable.
Three to five weeks to a tool your team operates without you, with a clickable version around day 7 and a demo every Friday. Fixed scope, fixed price, quoted within 48 hours of the scoping call.
Bring the workflow, rough is fine. In 30 minutes we map what to build, what to integrate and what to leave alone, and you have a fixed-scope quote within 48 hours.
RaftWorks