Run your practice on the platform we run ours on.
Builders Lab is one system for the work a delivery business actually does: the pipeline, the proposals and contracts, the storefront, the licensing ledger, the email list, and the content that goes out on your channels. Partners white-label the whole thing and run their own practice on it.
Every module is load-bearing in our own business before a partner ever sees it.
- 01CRM and pipeline
- 02Publishing and channels
- 03Proposals and contracts
- 04Storefronts and checkout
- 05Licensing and settlement
- 06Email and audience
One plan, scoped to your practice.
White-label the platform and run your own practice.
A 20-minute call, a written scope, then a start date. We onboard Builders Lab partners deliberately rather than self-serve.
- All six modules on one data model
- Your own domain and brand, end to end
- Publishing to the channels you and your clients own
- Per-product commission settlement on a ledger
- A named partner lead at the lab
Scope, timeline and price are agreed with you before anything starts. No card, no trial clock, and no surprise line at renewal.
Built for the people who carry the work.
Running a delivery practice means running a stack: a CRM for the pipeline, a document tool for proposals, something for licensing and commissions, a storefront to sell through, billing that reconciles, email to reach the list, and a scheduler for the content that keeps the phone ringing. Most teams assemble that from six vendors that do not talk to each other, then spend their margin keeping the seams from splitting. The client record lives in one place, the contract in another, and the post that won the lead in a third. Builders Lab is that stack as one system, with the records joined up.
Agencies and studios delivering AI products to clients
Partners who want to resell under their own brand
Teams that publish for clients and need approval before anything goes out
Practices that need CRM, licensing, and billing without stitching five SaaS tools
What you actually get.
Six modules on one data model, so a lead, the proposal it turned into, the licence it activated and the post that sourced it are the same record rather than four exports. Each one is in daily use in our own practice.
CRM and pipeline
Companies, contacts, leads and a funnel that reflects where work actually is, with AI doing the typing and a person keeping the judgement.
- Companies, contacts, leads and stages in one place
- AI intake reads an enquiry and drafts the first reply
- An edit-gating review queue, so nothing leaves without a human
- Scheduled email with tracked links back to the record
Publishing and channels
Plan, approve and publish content to the accounts your business or your client owns, on a calendar everyone can see, with the results coming back into the same console.
- Connect the Facebook Page and Instagram account you own through Meta's own permission screen
- Plan a calendar across LinkedIn, Facebook, Instagram, Threads and X
- Nothing publishes until a person approves it: draft, approved, scheduled, published
- Every published post comes back with its link, its comments and any mentions
- Reply from the console, or unpublish and republish when something changes
Proposals and contracts
The document that wins the work and the agreement that governs it, joined to the client record instead of living in a folder.
- Proposals with per-section editing and a share link per client
- An immutable contract snapshot the moment it is accepted
- A deposit activates the engagement and dates the milestones
- Change orders confirmed with a passkey, and a public status page
Storefronts and checkout
A public place to sell what you deliver, under your brand, with the money arriving where it should.
- A storefront with an editable profile, cover and socials
- Stripe checkout, including a deposit mode for service work
- A product catalog with variants and per-product commission
- Attribution that survives the click and settles to the right partner
Licensing and settlement
The part most practices do in a spreadsheet, done as a ledger that reconciles.
- A credit-limit account with a netting ledger
- Self-verifying signed licences that validate offline
- Per-product commission rules with versions and holds
- Payout destinations and a statement you can hand to finance
Email and audience
Campaigns and funnels on your own infrastructure, with the compliance parts built in rather than bolted on.
- Segments and facets over the contacts you already hold
- Campaigns and multi-step funnels with queue fan-out
- Suppression, consent and one-click unsubscribe
- Tracked links, open reporting, and the provider of your choice
And the surface around them
Channels
- Facebook Pages
- Threads
- X
White-label
- Custom domains
- Per-tenant branding
- White-labeled AI
- Partner portal
AI inside it
- Layered context
- Task framework
- Draft with AI
- MCP tools
Runs on
- Cloudflare Workers
- D1
- R2
- Queues
- Stripe
- Resend
The parts you feel in week two.
One record, not six exports
A lead, the proposal it became, the contract that froze, the licence it issued and the post that sourced it are the same record. Nothing has to be reconciled between tools because there is only one tool.
A human gate on anything outward
Messages, posts and sends pass a review queue before they leave. AI drafts, a person approves, and the approval is recorded against the record so you can show who signed off and when.
Your brand, all the way down
Custom domains, per-tenant branding and white-labeled AI, so a client moving through the storefront, the proposal and the portal never meets our name.
Money that reconciles
Commission rules are versioned, holds are explicit, and the ledger nets what is owed both ways, which means the settlement statement is something finance can read without a call.
Compliance built in, not bolted on
Suppression lists, consent state and one-click unsubscribe are part of the send path rather than a checklist you maintain beside it.
Edge-native by default
It runs on Workers, D1, R2 and queues, so a partner in another region gets the same response times without you provisioning anything.
What it changes, by the person who owns the number.
Five tools hold five halves of the same client. The pipeline is in one, the contract in another, the invoice somewhere else, and nobody can say what a client is worth without an afternoon of exports.
One record carries the lead, the proposal, the contract and the settlement, so the number is on screen rather than in a spreadsheet.
Client content lives in a shared document, gets approved over messages, and is posted by hand from whoever happens to have the login that day.
A calendar the client can see, an approval that is recorded, scheduled publishing to the accounts they own, and the published links coming back on their own.
You want to resell delivery under your own brand without building a platform first, and without your clients ever meeting somebody else's logo.
Your domain, your branding and your storefront, with commission settling per product on a ledger you can audit.
Work starts before the paperwork lands, and nobody is quite sure which version of the scope the client actually accepted.
The accepted proposal freezes into the contract, the deposit starts the clock, and every change order is confirmed and dated.
From an idea to a published post, and from a proposal to a settled licence.
On Monday an idea moves out of the content bank into a draft, and the calendar shows where it lands. On Tuesday the client opens their console, reads it and approves it, which is the only route by which it can be scheduled. Thursday morning it publishes to their Facebook Page and Instagram account, and the console fills in the post links, the comments and any mentions, so the replies happen in the same place the post was planned. In that same week a proposal is accepted, freezes into a contract, takes its deposit and issues the licence that the ledger settles at month end. Both of those are one system, which is the whole argument for it.
- Cloudflare Workers
- D1
- R2
- Queues
- Stripe
- Signed licenses
- TypeScript
The ones buyers actually ask.
- Is this a product or a partnership?
- Both. You get the platform, and you get a partnership with the lab that builds on it every day. We onboard partners deliberately rather than self-serve.
- Can I brand it as my own?
- Yes. Custom domains, white-labeled AI, and per-tenant branding are the point. Your clients see your brand, not ours.
- What happens when a client connects their Facebook Page or Instagram account?
- The client authorises the connection on Meta's own permission screen and picks the Page or account they want to use. We use what Meta returns for three things: showing that list so they can choose where a post goes, publishing the post they approved at the time they scheduled it, and bringing the published post back with its link, comments and mentions so they can reply and plan what comes next. It runs the console for that client and nothing else. Nothing is sold, nothing is shared between clients, and nothing is used to build advertising audiences. Disconnecting the account in Meta stops all of it immediately.
- Who decides what gets published?
- A person does, every time. A piece moves from draft to approved to scheduled, and only an approved piece can be queued, so there is no path that publishes something a human has not signed off. That is deliberate: an approval you can point to is what makes publishing on somebody else's behalf defensible.
- Do I have to use every module?
- No. Partners usually start with the two that hurt most, which tends to be the CRM plus either the storefront or the publishing console, then switch the rest on as they retire the tool each one replaces. The modules share one data model, so adding one later joins it to the records you already hold instead of starting another island.