§ Agency partnership / White-label production
Add production capacity,
without lowering the build standard.
This goes to my inbox, not a partner-sales queue. I'll review your expected build volume, typical scope, stack, approval process, and preferred branding personally.
Tell me what the production pipeline actually looks like: expected builds per month, typical client scope, current stack, who owns copy and approvals, and whether the finished work should stay under your name or carry a Powered by CDS credit.
Delivered directly via the site's own lead pipeline — the same Resend wiring I ship to clients. No CRM, no auto-responder drip.
I check whether the expected volume, turnaround, stack, client profile, and approval process fit the CDS production system. If something would break the relationship later, I name it before terms are proposed.
Client ownership, branding, volume, intake requirements, review windows, scope, ongoing responsibilities, and commercial terms are agreed before production starts.
Price the production obligation,
not a public package.
Agency partnerships are quoted privately around expected build volume, typical scope, platform mix, migration load, approval speed, branding, and who operates the site after launch. A retained-capacity agreement and a one-off fulfillment build are different obligations — the written terms should reflect that.
Next.js is the preferred stack for new work. Existing WordPress sites can stay on WordPress when that is the right client decision, and they can move to Next.js when the old platform is creating a real constraint. The inquiry above is where that mix gets defined.