White-Label Site Build Intake (Onboarding)

White-Label Site Build Intake (Onboarding)

1. 01

   Score the prospect against a minimum viable retainer before any generation work starts

   A build that cannot carry platform cost plus 6 to 10 hours of human correction is a loss leader, not a product. Write the number down and get it signed off internally before the kickoff call.

2. 02

   Collect brand assets, legal pages, and the client's own service descriptions in one intake folder

   Generated copy is only as specific as the inputs. If the client cannot supply service descriptions, book a 30 minute interview and transcribe it rather than letting the model invent positioning.

3. 03

   Confirm the white-label boundary in writing: whose domain, whose invoice, whose support inbox

   Platforms such as Duda and Lindo ship reseller billing and branded dashboards, but the client relationship still belongs to the agency. Decide before launch whether the client ever sees the underlying vendor name.

4. 04

   Map every page the client expects against the template library before promising a page count

   A 12 page scope on a builder with 200 plus templates is a different job than a 12 page scope on a constrained one. Reconcile the sitemap against what the platform actually renders cleanly.

5. 05

   Set the revision allowance at two rounds and state what counts as a round

   Unlimited revisions is the fastest way to erase delivery margin on a small build. Define a round as one consolidated set of comments returned within five business days.

6. 06

   Log the platform's export and portability terms in the client file

   Some builders let a site leave; others hold hosting and CMS together. Record which one applies so the exit conversation in year two is not a surprise.

7. 07

   Assign a named delivery owner and a named reviewer, not a team

   Shared ownership on a low-budget build means nobody catches the accessibility and performance pass before launch.