Prepared by
For
White-label web development
We handle the development while your agency manages the client.
What’s delivered
- An estimate for your proposal. Before your client signs, we review the brief or designs and send an estimate that lists what it assumes and what it leaves out. Your proposal is then based on the real build.
- The build. The frontend, backend or integration work you’ve handed us, in a repository you or your client own, or one we transfer to you at the end.
- Something to show your client. A staging site your project manager can review and share with the client on your schedule.
- Notes for whoever maintains it. How to set it up, the environment variables, how to deploy it, which third-party accounts it uses, and anything it doesn’t do yet.
What’s needed to start
- Approved designs or a written specification
- Anything your client has fixed
- Access to the repository and hosting
- One person who can make decisions
- Keys for any connected services
What affects the cost
- How complete and settled the designs are
- The number of page types, components and user roles
- Connections to third-party or client systems
- Content or data that has to be moved across
- Hosting, security or compliance requirements from your client
- How tight the timeline is
Usually included
- Frontend, backend and integration work for the agreed scope
- Technical input on your proposal and estimate
- Joining technical meetings with your client, if you want us there
- Setup and maintenance notes for your team
Not included unless agreed
- Selling to or invoicing your client
- Visual design and copywriting, unless agreed separately
- Contacting your client without your agreement
- Hosting or subscriptions in our name, unless agreed
Dependencies
Client IT teams, third-party platforms and late content often decide when a site can launch. We point these out when we estimate, so you can allow for them in your timeline.
Indicative summary. Scope, timeline and cost are confirmed in a written quote for each project.