--- title: What a White Label Web Development Retainer Looks Like url: https://varstatt.com/jurij/p/what-whitelabel-dev-retainer-looks-like author: Jurij Tokarski date: 2026-05-05 description: White label web development on a weekly retainer — senior dev capacity behind an agency or design studio's brand, invisible to their clients. section: Blog (https://varstatt.com/jurij/archive) tags: retainer-shapes (https://varstatt.com/jurij/c/retainer-shapes) --- Most agencies and design studios reach a point where they can sell white label web development to their clients but can't deliver it cleanly. They close clients who want websites, apps, custom integrations — and then either subcontract chaotically, hire too early, or pass on the work and lose the deal. This retainer is the third option. The agency keeps the client relationship, keeps the brand, keeps the margin they want to set. I deliver the work behind their name. Their pipeline becomes the queue. ## Same Retainer, Partner-Facing The white label version of the [Varstatt weekly retainer](/) is the same retainer as every other shape: $997/week, cancel anytime through Stripe, senior engineer working week after week, no minimum commitment. The "white label" framing describes the buyer — a white label agency, design studio, or productized-service operator — and the fact that the work ships under their brand instead of mine. The partner subscribes once. Their clients' projects queue against the retainer. When the pipeline runs full, the retainer runs hot. When it runs dry for a week, they pause through Stripe and resume when the next project lands. No per-project quotes between us, no scope renegotiation per site, no overhead on every deal they close. What they tell their client about pricing, scope, and timelines is **their business**. My rate is fixed and stable. Their margin is whatever they decide to set on top. ## What the Work Actually Looks Like The work itself is the same work the retainer always does — just routed through a partner. A few common shapes that show up in the queue: **Marketing and brochure sites.** White label web design services on top of WordPress, Squarespace, Webflow, or simple Next.js. Themes built from scratch or rebuilt, custom design implementations, design handoffs from a partner's in-house team. Roughly one site per week is realistic if scopes are tight. Two sites per week stretches it. Four sites per month is a reasonable steady state for an agency feeding the queue. **Client web apps.** Booking flows, internal portals, member areas, dashboards — the white label app development side of the queue. The same capacity that would build a [PoC in 2 weeks](/jurij/p/what-a-2-week-poc-looks-like) or an [MVP in 6 weeks](/jurij/p/what-a-6-week-mvp-build-looks-like) — except the partner is the one scoping with the client. **Integrations and small projects.** Stripe wiring, custom forms with backend logic, third-party API hookups, email automation that exceeds what the no-code tool can do. The work agencies usually subcontract poorly because individual jobs are too small to interview a contractor for. **Maintenance on sites the agency built.** A partner's existing client portfolio that needs care — same work as [the maintenance shape](/jurij/p/what-a-software-maintenance-retainer-looks-like), routed through the partner instead of direct. The queue isn't fixed. The retainer doesn't care whether week three is one big project or five small ones — the cadence is what's billable, not the count of deliverables. ## How Invisibility Works I don't talk to the client. The partner runs the brief, the meetings, the revisions, the invoices. I deliver the work into a repo or platform they own, under their account, with their credentials. No Varstatt branding on commits, no portfolio cross-posts without their permission, no public mentions of the projects. This isn't a legal or NDA position — it's the operating default. The partner's relationship with their client is the asset. My job is to make that relationship work, not to compete with it. If a partner wants the opposite — co-branded work, joint case studies, public credit — that's a different shape and a different conversation. Most don't want it, which is why this retainer exists. ## How White Label Web Development Differs from Subcontracting Most agencies who try development work end up subcontracting per project. They quote, they win, they scramble to find someone available, they negotiate per-job rates, they manage scope creep across freelancers who don't share context between projects. It's chaotic for them and unstable for the contractor. The white label web development retainer fixes both ends. **For the partner, it's predictable capacity** — a known person on a known cadence at a known rate, who already knows their client's previous projects. **For me, it's stable work** — one buyer relationship, one rate, no per-project sales cycle, the same continuity benefit [the solo model](/principles/philosophy/solo-model) gives every retainer. Per-project freelance economics work for one-offs. They don't work for an ongoing partnership where four to eight projects flow through a year. The retainer model handles that volume the way it's meant to. ## Who This Fits Marketing and ads agencies whose clients keep asking for sites or apps and who don't want to staff a dev team. Design studios delivering Figma files who need a white label website developer downstream to ship the build. Productized-service operators in adjacent niches — SEO, branding, conversion optimisation — whose clients keep needing white label web development services the operator can't do themselves. Communities of designers or no-code builders who hit the limits of their toolkit and need a senior dev on call for the projects that don't fit. The pattern across all of these: **the partner has the audience and the close, but doesn't have the build capacity**. One competent person, weekly, is the missing piece. ## What This Isn't Not a referral program. Not an affiliate split. Not a one-off subcontract per project. Not a price-per-site contract. The partner subscribes to the retainer like any other client. The white-label framing is the operating reality of the relationship, not a different commercial structure. If a partner wants per-project pricing or one-off work, that's a different shape — closer to [the PoC](/jurij/p/what-a-2-week-poc-looks-like) or [MVP build](/jurij/p/what-a-6-week-mvp-build-looks-like) shapes for fixed-scope projects, with the white-label terms layered on top. The retainer is for ongoing flow. ## Other Shapes the Retainer Takes Same retainer, different shapes — pick the one that matches the work in front of you: - **[What a 2-Week PoC Looks Like](/jurij/p/what-a-2-week-poc-looks-like)** — when a partner has a single fixed-scope project, not ongoing flow - **[What a 6-Week MVP Build Looks Like](/jurij/p/what-a-6-week-mvp-build-looks-like)** — when a partner's client needs a real first version, not a marketing site - **[What a Software Maintenance Retainer Looks Like](/jurij/p/what-a-software-maintenance-retainer-looks-like)** — for the partner's existing client portfolio that needs care - **[All retainer shapes →](/jurij/c/retainer-shapes)** ## How to Start The path is the same for every shape: 1. **[Submit a project brief](/brief)** — 2–3 minutes. Within 24 hours, you get an honest read on whether this engagement fits. 2. **15-minute discovery call** — confirm scope, working pattern, and how invisibility maps to your client relationships. 3. **Subscribe to the weekly retainer** — work begins the next business day. Cancel anytime through Stripe, no paperwork. If you have questions before any of that, the [project brief form](/brief) has a free-text field — write whatever you need to.