A calm, transparent process. Every phase has a clear scope, and deliverables you can sign off in writing. No month-three surprises, no scope creep on our side, no late-night Slack threads.
We start with a discovery stage. A kickoff call, a short questionnaire, and a written brief we send back for your approval.
Understand of your business (45–60 min)
Competitor and reference audit
Written brief, sent for approval
02
— Architecture
Sitemap & wireframes.
We map the site and wireframe every unique template. This is where we quietly kill bad ideas and protect the ones worth keeping.
Sitemap & content model
Wireframes, 2 rounds of revisions
Content plan and who owns what
03
— Design
Visual direction & screens.
Visual directions, then scaled across every unique template. We review each stage with clear, commented screens.
Visual directions
High-fidelity screens for every template
Component library & elements
04
— Build
Development.
We build in the browser the same week design starts. Staging URLs are commentable from day one, so review happens in context, not in a deck.
Staging URL from week one of build
CMS setup & editor training
Integrations: bookings, commerce, analytics
05
— Launch
QA & go-live.
Launch week is quiet on our side and calm on yours. We run a full QA pass, migrate content, redirect URLs, and stay on-call through deployment.
Accessibility, performance, cross-browser QA
Redirect map & DNS cutover
Launch-day support and a handover call
06
— Care
Ongoing partnership.
Most clients stay on a care retainer. Monthly improvements, quarterly reviews, and a team that already knows your site by name.
Managed hosting, backups, patches
Monthly improvements (2–4 hours)
Quarterly review call
FAQ
Questions we often get.
Timelines vary depending on project scope, since each of the six phases, from discovery through launch, includes its own review and approval steps rather than a fixed universal timeline. What stays consistent is visibility throughout: a staging URL is shared from week one of development onward, so progress can be reviewed in context rather than waiting until the end. Sending a short brief is the fastest way to get a timeline specific to a particular project.
Yes, alongside the Delhi studio, there is also a studio location in Osaka, Japan, reflecting work with clients beyond India. The written brief and discovery process used at the start of every project works the same way regardless of location, with a short kickoff call and a written brief sent back for approval before moving forward.
Copy ownership is addressed directly during the Sitemap & Wireframes phase, where a content plan is created and it is clarified who owns what, rather than assumed by default in either direction. This is decided early so there is no ambiguity once design and build begin, and the approach can be discussed as part of the initial brief.
This is assessed during the Brief & Discovery phase, where the business, competitors, and existing setup are reviewed before a written brief is finalized. Whether existing hosting or a CMS can be kept depends on the specific platform and project requirements, so this is confirmed early rather than assumed, and can be raised directly as part of the initial brief.
Every phase has a clear scope and deliverables signed off in writing, so if a project needs to extend beyond what was originally agreed, this is handled through the same written approval process rather than informal scope creep. The goal, as stated upfront, is no month-three surprises and no late-night back-and-forth, meaning any extension is scoped and agreed on clearly before work continues.
The process begins with a kickoff call to understand the business, typically 45 to 60 minutes, followed by a competitor and reference audit. The outcome is a written brief sent back for approval, ensuring both sides agree on direction and expectations before any design or development work begins.
Wireframes include two rounds of revisions during the Sitemap & Wireframes phase, and during Visual Direction & Screens, two distinct visual directions are presented before one is chosen and scaled across every unique template. This structured approach keeps feedback focused at each stage rather than open-ended.
A staging URL is made available from week one of development, so progress can be reviewed directly in a live, working environment rather than only through a deck or final presentation. This applies alongside CMS setup, editor training, and any integrations such as bookings, commerce, or analytics being built in.
Most clients move into an ongoing partnership after launch, which includes managed hosting, backups, and patches, along with monthly improvements scoped to 2 to 4 hours and a quarterly review call. This is treated as the sixth phase of the process rather than a separate afterthought, so the transition into ongoing care is planned from the start.
✦Start a project · Desiment · Delhi
Ready when you are.
Send a short brief — the business, the goal, the rough budget and timeline. We'll reply within a working day with a note on fit and next steps.