Onboarding & timezones

The first week, step by step

Day 1, kickoff call. Thirty to forty-five minutes, scheduled in your working hours. We walk the brief, kill ambiguities, and lock the milestone list. You leave with a one-page summary of everything decided; it goes in the project doc.

Day 1–2, access setup. You create (or grant) access under the model below: your accounts, our scoped seats. If nothing exists yet, we register the domain and hosting in your name, with you holding the logins from minute one.

Day 2–3, environment and staging. Repository, staging URL, project channel. The staging link works from this day until long after launch, you can watch everything build.

Day 3–5, structure and design direction. Sitemap, page structure, and the design direction for your approval. This is the week's one required decision from you; the method asks for decisions on a schedule, and this is the first one.

End of week 1, you have: a live staging link, a locked milestone list, access documentation, and a demo of the first working slice. No project in history has regretted starting this way.

The access model: you own, we operate

Every account, domain registrar, hosting, CMS, analytics, email, is registered to you, paid by you, owned by you. We work through collaborator and delegated seats with exactly the permissions the work needs, nothing broader. At handover or exit, you revoke our seats; nothing else changes because nothing else was ever ours. This model exists because the alternative, developer-owned accounts, is the single most common trap in this industry, and refusing it is the cheapest insurance you will ever get. The full list of what you should hold personally: the handover checklist.

Timezones, honestly

we work from IST. Here is the real overlap math for the regions we serve, no marketing spin, just the clock:

The pattern across all of them: async-first with scheduled overlap. Decisions and demos are written; calls happen in the shared window when a call is genuinely worth one. Twelve years of remote-first tooling means distance stopped being the constraint, communication discipline took its place, and that is a trainable habit on both sides.

What we ask of you in week one

Three things, none of them technical: the kickoff call, the access setup (fifteen minutes of clicking), and the first design-direction decision on schedule. That is the entire client-side cost of onboarding. Everything else, environment, structure, build, is ours to carry. See how the money side runs: payments & terms.