Tangensys • Plan, deliver, measure
White-label web development for agencies
Turn your agency’s client requirements into software work with clear sign-off checks. Tangensys supports agreed website features, integrations and technical changes, while your team manages the client brief and approves releases.
An agency handover you can review
Your brand, brief and approval route.
- Agreed scopeBrief
- Useful outputDeliver
- Agency approvalReview
Delivery your account manager can explain
A feature request can sound simple while hiding several dependencies. An integration may need an external account, existing code may lack documentation, and a permission mistake can expose the wrong record. Begin with the actual workflow and operating constraints. The result should be a feature your agency can test and explain, with the release and recovery responsibilities clearly assigned.
- Agency briefScope and client context
- DeliveryTangensys completes the agreed work
- Agency reviewYour team checks it first
- HandoverShared with your client under your brand
Where this support fits your agency
Design agencies with custom requirements
Commission the functionality that sits beyond a standard page build. Bring the approved interface, user roles and expected actions so the technical scope can be separated from ongoing design feedback.
Agencies inheriting an existing website
Start with code, access and environment discovery before promising a repair. A small, clearly defined first change helps reveal undocumented dependencies and establishes how the agency will review and approve releases.
Teams connecting client systems
Map what data moves, which system owns it and what happens when a request fails. The delivery plan needs permissions and exception handling as well as the successful connection.
What the agreed web development work can include
Use these areas to shape the brief. Your proposal identifies the actual outputs and who implements, approves and maintains them.
Workflow and technical discovery
Review the relevant code, environment and business workflow. Identify user roles, data ownership, existing dependencies and the first sign-off cases. Unknowns are recorded so your agency can decide whether discovery is sufficient for a fixed scope or further investigation is needed before committing to a build.
A specification that can be tested
Translate the agreed feature into expected actions, permissions, error states and test data. Include what should happen when a request is repeated or an external service is unavailable. The agency receives a scope that can be reviewed by the client and used to distinguish a defect from a new requirement.
Implementation and integration work
Develop the approved feature in the agreed environment. External services require supported access and current provider documentation. Configuration and credentials are handled through the agreed access route; production secrets should not be embedded in public browser code or casually circulated in a project chat.
Staging review and controlled release
Test the agreed successful, failed and permission-restricted actions before release. Your agency consolidates the client’s sign-off decision. The release plan identifies who deploys, what backup or recovery route is available and what needs checking afterward. Production access does not remove the need for approval.
Technical handover and maintenance
Provide the agreed code, environment notes, dependencies and operating instructions. Document unresolved issues and the route for future changes. Hosting administration, monitoring, urgent support and ongoing updates need defined ownership and commercial scope so a delivered feature has a workable operating plan.
Deliverables
What your agency receives
Each white-label web development engagement produces records your team can check before anything reaches your client.
Each month or milestone
- A staging link at each milestone, so your team can review progress
- Code in your agency’s or client’s repository
- A testing checklist covering browsers, devices, forms and accessibility
- Handover notes explaining how the site is built and maintained
Approvals
How handover and client approval work
Your agency stays in charge of the client relationship. Our general process is explained on the white-label services page.
Approval steps
- Designs are signed off by your agency and client before development starts.
- Each staging review has an agreed number of revision rounds.
- Launch happens only after written sign-off from your agency.
- A post-launch support window for fixes is agreed in the proposal.
Communication and data
- Most coordination happens by email and your project board, with calls arranged during working hours in India.
- Access to client accounts and data is limited to what the work needs and is documented.
Pricing
What affects the quote
Invoices are raised in rupees and include GST where it applies.
Main cost factors for white-label web development
- Number of page templates and custom features
- Platform (WordPress, Shopify, Laravel, React and others)
- Integrations with CRMs, payments or other systems
- Content migration from an existing site
- Accessibility, performance and post-launch support requirements
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.
How is white-label web development priced?
Each project is quoted in rupees against agreed milestones: templates, custom features, integrations, content migration and post-launch support. You receive a custom quote within 2 working days of reviewing the brief.
How soon can work start?
Work starts once the brief, access and approval contacts are agreed. The proposal confirms the start date and the timing of the first deliverable, which depends on the scope and your client’s availability.
Will Tangensys appear in the site credits or code?
No, unless you ask for it. The work is delivered under your agency’s brand.
Which platforms do you build on?
Commonly WordPress, Shopify, Webflow, Laravel and React. We confirm the right fit for each project before quoting.
How are bugs after launch handled?
Bugs found within the agreed support window are fixed as part of the project; later changes are quoted separately or covered by a maintenance plan.
Can you work in our repository and process?
Yes. We can follow your branching, review and deployment process.
Do you sign NDAs?
Yes, on request, before any client details are shared.
What happens if a client changes the brief?
We pause the affected work, agree the change with your agency and confirm any effect on scope, timing or cost before continuing.
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