Skip to content

For agencies

Become the platform, not the reseller.

Reselling SaaS means marking up someone else's per-seat invoice and competing with their signup page. Deploy Tinbox to each client's own Cloudflare account instead, brand it as yours, and run the whole stack as your product — support, sending, lists — tuned to each client's business with your own Skills and agent briefs. The relationship stays yours, the data stays theirs, and the margin stops leaking to a vendor.

The old way

Reselling SaaS caps your margin and your moat.

Every client runs on subscriptions you mark up, can't brand, and don't control. The data that should tie them to you sits in a vendor's account, not yours.

Margin leaks to vendors

Per-seat, per-subscriber SaaS recurs forever and grows with every client you add. Worse, your markup competes head-on with the vendor's own signup page.

Someone else's name on everything

Logins, sender domains, and dashboards all carry the vendor's brand. That leaves you the middleman passing along bills, never the platform clients depend on.

Nothing to actually own

When the data lives in a vendor's account, a client can walk with a CSV export. You've built no platform that's yours to operate and price.

How an agency runs it

Deploy, brand, operate.

One Tinbox per client, on the client's own Cloudflare account: provisioned, branded, and operated by you.

01 · Deploy

One stack per client

npx tinbox init provisions everything on the client's own Cloudflare account and ships one bundled worker. You run the deploy; they own the infrastructure.

02 · Brand

White-label it as yours

Set the branding, sender domain, and AI-writing voice at runtime, no redeploy. The inbox your client logs into reads as your product, never a vendor's.

03 · Operate

Your playbook, shipped as code

Build your house Skills, plugins, and agent briefs once — a “qualify inbound leads” agent, a “render the client's CRM record in the thread” Skill, a weekly digest — then roll them across every account and tune each to the client. Your agency's know-how becomes the product, not a config you forward.

Why it's better business

Own the platform, not the invoice you forward.

Flat cost per client

Each deployment is a one-time $249 license, not a recurring per-seat bill. You price the service and pocket the spread; the software stops eating it.

Ownership is the moat

Data lives in the client's own Cloudflare account from day one. That's a simple compliance story, a clean handoff if you ever part ways, and a reason to stay while you don't.

Your expertise, productized

Skills, plugins, journeys, and autopilot configs are code you reuse across every account. It's your agency's know-how, shipped as software you resell at zero marginal cost.

Questions

How the model works.

Can I manage every client from one place?
Today you operate each deployment directly, fully isolated per client. A unified multi-client console is on the roadmap; the per-tenant model it builds on ships right now.
Whose Cloudflare account does it run on?
The client's, ideally: that's what makes the data theirs and the handoff clean. Prefer to hold it for them? Run it on your own account. Either way it's a deploy you operate — Tinbox never runs a server in the middle, so there's no platform fee and nothing to depend on but you and Cloudflare.
How is it licensed across clients?
One license per deployment, with no per-seat metering inside it. Adding a client's entire team costs you nothing extra, so headcount growth never erodes your margin.

Why builders switch

What agencies say.

“We stopped reselling seats and became the platform. One branded stack per client, on their own account — the margin math finally works in our favor.”

Tomás Marín

Founder, Northwind Agency

Sample testimonials: illustrative, pending real customer quotes.

Own the platform your clients run on.

One branded stack per client, on their own account, at a flat cost — your house Skills and agent briefs running across all of them. The margin stops leaking, and the relationship is yours to keep.

Not technical? We'll build it for you →