Skip to main content
WEB TATTVA
Working Principles · Clear Engagements

Working Principles

Good digital work benefits from clear expectations. These principles explain how we generally approach ownership, communication, billing, handover and support.

A practical foundation for collaborative, predictable digital projects.

Core Framework

Our working principles.

These principles reflect how we approach engineering, collaboration, milestone structuring, and project delivery.

01/ Bespoke Code & Licences

Ownership & Access

Ownership and access to bespoke deliverables are handled according to the applicable proposal, statement of work or agreement. Third-party software, open-source libraries, licensed assets and external services remain subject to their respective terms.

Upon fulfillment of agreed commercial terms and final settlement, rights to bespoke project deliverables are transferred or granted under the applicable contract. Third-party software, open-source libraries, stock assets, fonts, APIs and external services remain governed by their standard public or proprietary terms.

02/ Clear Expectations & Cadence

Communication

We aim to communicate clearly and respond within the expectations established for the relevant project or service.

Healthy collaborations depend on transparent, predictable channels. Communication schedules, review check-ins, and response cadences are aligned at the start of each project to keep work flowing smoothly without ambiguity.

03/ Scope-Defined Hypercare & Care

Post-Launch Support

Any warranty, bug-fix period or post-launch support commitment is defined by the applicable project scope or agreement.

Post-launch stability is an integral part of modern web delivery. Any warranty window, bug-fix resolution, or ongoing maintenance arrangement is specified in your project agreement, with continuing support available via structured care plans.

04/ Predictable Schedules

Clear Payment Milestones

Payment milestones are communicated before work begins and may vary depending on the project, package and commercial arrangement.

Commercial clarity protects both parties. Milestones and invoicing stages are clearly outlined prior to kickoff. If requirements evolve during development, scope adjustments and associated fees are agreed upon before additional work begins.

05/ Standard Handover & Modern Tooling

Maintainable Technology

We prefer standard technologies and documented handover arrangements that make future maintenance easier.

We build with mainstream, widely supported web technologies (such as Next.js, React, TypeScript, and clean CSS). Standard tooling, documented repositories, and clear environment setups ensure your team or future developers can inspect and extend the site with ease.

06/ Independent Hosting & Long-Term Care

Flexible Support

Hosting and domain costs depend on the provider, plan and infrastructure selected.

We design architectures that give you flexibility over where and how your website runs. You maintain control of your infrastructure accounts, and ongoing maintenance or retainer support is optional rather than a mandatory lock-in.

Mutual Collaboration

Client responsibilities.

Successful web development relies on active, mutual collaboration. Engagements proceed smoothly when clients support the project through:

Providing accurate content, business details, and project assets.
Ensuring supplied content, trademarks, and materials can legally be used.
Reviewing deliverables within agreed review and staging windows.
Providing timely, consolidated feedback to maintain scheduled delivery.
Maintaining account credentials, registrar logins, and keys securely.
Purchasing required third-party services, domains, and subscriptions where applicable.
Project-Specific Terms

Governance & Project Agreements

These principles describe our general approach. The applicable proposal, statement of work, order, licence or agreement determines the specific scope, fees, ownership, timelines, warranty, support and responsibilities for each engagement.

No statement on this page should be interpreted as an unconditional contractual guarantee outside the written terms executed for your specific project.

Ready to structure a clear engagement?

Let’s discuss your project scope, milestones, and technical architecture with complete clarity.