White-label embed
Drop the widget into the client's site with their colors, their logo, their domain. Customers fill against the locked artwork without ever seeing StackFill chrome (or yours, if you want).
For agencies
Set the template up once per client. Hand them a hosted link or drop the white-label embed into their site. Stop eating the variant revisions on retainer.
Client signs a retainer for "brand + collateral." First quarter is fun: the brand book, the master designs, the launch. Quarter two onward, every other email is "can we get a new business card for this rep" or "can you do a flyer for the November event with the regional details."
The revisions don't pay. They're not strategic. They're not creative. They're a junior designer typing names into Illustrator at retainer rates. The agency loses margin, the designer loses motivation, the client loses faith that the agency is doing anything but versioning files.
The standard fixes don't fit:
Stand the client up once. Upload their approved files. Mark editable fields, lock the rest. Hand them a hosted fill link or drop the StackFill embed into their existing site as a white-labeled widget — the customer-facing surface carries their brand, not ours.
For the client, every personalized piece becomes self-serve. For the agency, the recurring variant tax disappears — you billed for the setup, the client pays StackFill directly, and your senior designers get back to actual strategy and design.
Multi-tenant from day one: one StackFill workspace per client, isolated templates, isolated billing, optional client logins for direct access. Or run everything from your agency workspace and proxy fills out to the client. Whatever fits your contract.
Drop the widget into the client's site with their colors, their logo, their domain. Customers fill against the locked artwork without ever seeing StackFill chrome (or yours, if you want).
One workspace per client. Templates, fonts, fills, billing all isolated. Add a new client in 5 minutes; remove one and their data leaves cleanly.
Wire StackFill into the client's CRM, their order desk, their marketing automation. Webhooks fire when a fill is finalized. Idempotency keys, rate limits, request IDs — the boring API hygiene is already there.
Run client billing through your StackFill subscription, or hand each client their own subscription and you just configure the templates. Both patterns work.
Each client gets their own fill log: who, when, what values. Hand it over at QBR. Cuts the "what did the retainer actually cover" conversation in half.
The client cannot break the brand. Locked elements stay locked through every fill. The agency's creative work stays intact.
Agency tier is built for many clients — Agency ($299/mo) covers 250 templates, 10,000 renders/mo, 25 seats. For very-large agency operations or custom workspace structures, talk to us.
Yes. The widget carries your client's branding by default. No StackFill chrome required if you don't want it. Custom subdomains, custom CSS, optional locked top-bar — all configurable on Agency.
One workspace per client. D1 row-level isolation, separate R2 prefixes, separate font libraries, separate API keys. A client can never see another client's templates, fills, or fonts.
Your call. Run everything through your agency subscription and pass through, or have each client own their own subscription with you as a collaborator. Both are common.
If the client wants to charge the end customer for each fill (e.g. "$5 to print a personalized card"), StackFill can capture the fill payment through the client's own Stripe account. Pro+.
We export everything: templates, fills, fonts, render history. No lock-in tax.