Tangensys • Plan, deliver, measure
White-label web design for agencies
Give your agency a website delivery partner that works from an agreed brief through to a usable handover. Tangensys supports client-site design and builds while your team controls the relationship, visual approvals and launch decision.
An agency handover you can review
Your brand, brief and approval route.
- Agreed scopeBrief
- Useful outputDeliver
- Agency approvalReview
How this agency service works
White-label website design lets your agency commission design and agreed website production under its own brand. The scope covers the pages, content responsibilities, design direction, editing requirements and sign-off checks. Tangensys delivers the agreed work; your agency consolidates client feedback and approves the finished website.
- Agency briefScope and client context
- DeliveryTangensys completes the agreed work
- Agency reviewYour team checks it first
- HandoverShared with your client under your brand
Delivery your account manager can explain
A website project needs more than an attractive homepage. The client must supply accurate service information, someone must approve images and content, and the finished contact journey must work. A clear brief resolves those responsibilities early. It also prevents a design approval turning into an open-ended request for additional pages, integrations or custom features.
Where this support fits your agency
Brand and creative agencies
Extend an approved identity into a usable website while retaining creative direction. Share the brand rules, page requirements and reference preferences. The delivery brief identifies what must remain consistent and where a designer can explore.
Marketing teams rebuilding client sites
Connect the new site to the services, campaigns and enquiry actions already in use. Existing URLs and tracking requirements need review alongside the visual design so a redesign supports the wider marketing work.
Freelancers needing production support
Commission a defined site or page set with a staging build you can review. A consolidated feedback route helps you manage the client while the delivery team handles agreed production and testing.
What the agreed website design work can include
Use these areas to shape the brief. Your proposal identifies the actual outputs and who implements, approves and maintains them.
Page structure and content plan
Agree the sitemap, purpose of each page and information needed from the client. Identify the important contact actions and supporting pages before layouts are built. The output gives the agency a practical content-supply list and prevents key service information being postponed until the final review.
Visual direction and page layouts
Develop an approved design direction using the supplied identity and genuine assets. Layouts should make the main message, navigation and contact actions easy to find. The scope identifies the representative layouts and review rounds; approval of one direction gives the remaining pages a consistent basis.
Responsive production and editing
Build the agreed pages for the chosen website platform and test representative phone and desktop journeys. Confirm which content the client should be able to edit and how those fields are organised. Unusual integrations, custom account areas or product logic are development requirements that need their own specification.
Contact journeys and launch checks
Test navigation, quote or contact actions, important forms and the relevant launch settings. On a replacement website, identify old URLs that need an appropriate destination. Analytics, consent tools and booking integrations need supplied credentials and a defined configuration; an attractive button alone does not confirm a completed enquiry.
Assets and handover
Provide the agreed editing guidance, site access and asset record. The agency should know where licensed images came from, which details remain client-owned and how future changes are handled. Hosting, ongoing maintenance and new page production are separate responsibilities unless the proposal includes them.
Practical detail
A delivery record your agency can review
A useful handover makes the finding, action and approval easy to follow. This example is illustrative; it does not describe a client project or claim a result.
| Work stage | Illustrative record | Agency review |
|---|---|---|
| Brief | A professional-services client needs a clearer service hierarchy and a quote popup. | Approve the page list, genuine content and intended editing fields. |
| Design review | A representative service layout shows the offer, supporting evidence and next action. | The agency consolidates feedback against the approved direction. |
| Staging check | Phone navigation and valid, invalid and failed form states are tested. | Keep the test record and confirm the actual enquiry destination. |
| Launch handover | Document approved pages, access, redirects and future maintenance ownership. | The agency approves launch after unresolved items are reviewed. |
Review visual consistency, genuine content, phone behavior and the complete contact journey.
Choose the engagement that fits the workload
A defined first project
Start with a representative service layout and its enquiry journey. Agree the inputs, deliverable format and review decision before production. A small, clearly defined project gives your agency an opportunity to assess the quality of the output and the practicality of communication. It also reveals access or approval problems that should be resolved before more client accounts are added.
Recurring delivery support
Use an agreed account backlog for regular work, with capacity, priorities and reporting responsibilities made visible. Your agency decides which client requests move forward. The arrangement identifies what happens when urgent tasks compete with planned work, and how additional capacity is requested. A recurring scope should be reviewed when client requirements change.
Specialist project or overflow
Commission a specific task alongside your existing delivery team. Share previous decisions and identify where our responsibility starts and ends. The handover should fit your agency’s workflow so an outside contribution does not leave the account manager coordinating several conflicting versions. New requirements are reviewed as scope changes rather than assumed additions.
From the first brief to an accepted handover
The process gives your account manager a clear decision at each stage. Milestones and review rounds are agreed for the actual workload.
Set the account brief
Share the sitemap, brand assets, approved copy and images, platform requirements and the person consolidating feedback. We identify the starting task, missing information and delivery dependencies. Your agency confirms the client objective and scope. Discovery is useful when the current setup is uncertain; a rushed quotation should not hide unresolved access or implementation questions.
Prepare the agreed work
Production follows the approved brief and produces approved layouts, the agreed staging pages, contact tests and editing guidance. The working record distinguishes drafts, recommendations, implemented changes and tests. Questions that affect facts, permissions or scope go to your nominated contact, keeping the client decision with the person authorised to make it.
Review and resolve feedback
Your agency checks the output against the agreed sign-off checks and consolidates comments. We resolve in-scope feedback through that review route. A new requirement, blocked dependency or changed business instruction is recorded separately so everyone can see its effect on cost, schedule and the original delivery decision.
Approve the handover and next scope
Keep the accepted version, completed-task record and outstanding items together. Review visual consistency, genuine content, phone behavior and the complete contact journey. Your agency decides what is shared with the client and whether further work is appropriate. A successful initial task can support a capacity discussion; it does not automatically establish an unlimited delivery commitment.
Keep your agency in control of the client relationship
Your agency remains the client-facing decision owner. Day-to-day delivery runs through the nominated contact unless you explicitly approve another arrangement. If a client call is useful, agree the participants, roles and branding beforehand. The team should know who can make a commercial commitment and who is providing delivery information.
Before sharing client assets or access, agree confidentiality, permitted use, file ownership and any relevant contractual requirements. Use access suited to the task, with a record of who grants and removes it. The actual proposal identifies the delivery team and any partner involvement where relevant; specialist requirements should be discussed before sensitive client information is supplied.
A consistent review route protects everyone’s time. Consolidate client comments into one approved instruction, keep versions identifiable and record unresolved dependencies. These practices make it easier to retain your agency’s voice while giving the delivery team a brief it can act on.
What shapes your delivery quote
Pricing follows the work to be delivered, its complexity and the responsibilities included. For website design, share the proposed account or project, current setup and the sitemap, brand assets, approved copy and images, platform requirements and the person consolidating feedback. The quote should identify quantities or milestones, review rounds, client inputs and any work that remains with another provider.
Separate delivery charges from external costs such as media, hosting, licences, usage or specialist assets where relevant. Writing a recommendation, implementing it and maintaining it are different commitments. Your agency decides its client-facing price; our proposal makes the delivery scope clear so you can assess it against your own commercial arrangement.
Fixed response windows, ongoing capacity and urgent support are confirmed for the engagement. If the client changes the brief or a new dependency appears, we review its effect before proceeding. This keeps the account manager able to explain what is included and what needs a separate decision.
Handle revisions without losing the accepted version
For this service, consider a changed content requirement. This is a hypothetical delivery situation, not a client result.
A service-specific decision
A layout correction within the brief differs from another page type or new user journey. Review the effect on responsive states, editing and implementation before accepting a visual revision as the whole change.
A clear change record
Record the comment, source version and decision owner. A correction within the approved brief differs from a new deliverable. The agency should know the effect on scope and dependencies before promising the client a revised release.
A maintainable handover
Keep accepted assets or findings, test evidence and unresolved items together. Agree permitted client communication and future responsibility. A branded output is ready only when the underlying facts and task have passed the nominated review.
Free agency delivery review
Start with a clear scope and a practical next step.
Share your agency’s services, the client workload and the part of delivery you want support with. We’ll recommend a workable first engagement and provide a quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Is website copy included with the design?
The proposal identifies who supplies each page’s copy. We can discuss writing support, but the client still needs to approve service facts, claims and imagery. A content-supply checklist shows what is ready and what is blocking production. Copywriting should not be assumed from a page-count quotation.
What happens when the client requests more pages?
Record the new requirement and check its effect on layout, content, functionality and delivery. Your agency approves any additional scope before it is produced. This protects the original brief and gives the client a clear choice instead of hiding extra work inside an unresolved feedback round.
Can the output use our agency branding?
We can agree branded or unbranded output formats for the work in scope. Share your template, required sections and preferred terminology before production. Your agency reviews the accepted version before it reaches the client. Branding changes should be part of the brief rather than improvised at the final handover.
Will you communicate directly with our client?
The default route is through your nominated agency contact. Direct involvement requires explicit agreement about the purpose, participants and responsibilities. Your agency retains control of the client relationship, approvals and commercial commitments. A useful technical call does not change that ownership.
How long does delivery take, and how are revisions handled?
The proposal records milestones, review rounds and the information needed to meet them. Your agency supplies consolidated feedback. Late access, missing factual approval or a changed requirement can affect the plan; the delivery record identifies that dependency and the decision needed. We confirm a realistic timeline after reviewing the actual brief.
Can we test the arrangement with one client?
Yes. A defined first task or account gives your team a concrete output to review and a practical way to test communication. Agree its scope and sign-off checks first. Ongoing capacity and a larger client workload are discussed after that experience, rather than assumed from the first quotation.
How is the work priced?
The proposal prices the defined delivery scope, complexity, review rounds and responsibilities. External charges are identified separately where relevant. Your agency sets its own client-facing fees. Share the account setup and required outputs so the quote can distinguish advice, production, implementation and any ongoing support.
What should we share to receive a quote?
Start with the sitemap, brand assets, approved copy and images, platform requirements and the person consolidating feedback. Explain the result your agency needs to hand to the client and which tasks stay with your own team. That information helps us propose approved layouts, the agreed staging pages, contact tests and editing guidance without leaving important approvals or implementation responsibilities unassigned.
Are business results guaranteed?
A website can be reviewed against its agreed pages, editing needs and contact tests. Enquiry volume also depends on the offer, traffic and customer response; no sales total is promised. The proposal identifies the work and appropriate evidence your agency will review.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days