Working with clients across three continents +91 70009 59676 info@tanmayisoft.com
Discuss your project

Process

How a project actually runs

Eight stages. You see working software on a staging URL from stage four onwards, not at the end. Below, what happens at each stage, what you receive, and what we need from you.

Start a project How pricing works
01 1–2 weeks

Discovery

We work out what the project has to achieve commercially, what constraints exist, and how success will be measured. This is where most of the risk gets removed — a wrong assumption caught here costs an hour, the same assumption caught in development costs a fortnight.

What you receive

  • A written brief with the goal, scope and success measure
  • A list of open questions and who owns each one

What we need from you

Access to whoever knows the business problem, and any existing analytics or search data.

02 1 week

Strategy

Architecture, stack and delivery plan. We decide what gets built custom and what is bought, then write down why. The decision points that will need your input are scheduled now rather than discovered later.

What you receive

  • Technical approach and stack, with the trade-offs stated
  • Sitemap and URL structure
  • Delivery plan with milestones

What we need from you

A decision on the engagement model and a single named approver on your side.

03 2–3 weeks

Design

Wireframes first, so structure is agreed before anyone argues about colour. Then the interface, reviewed against the commercial goal rather than personal taste. Two rounds of revision are built into the estimate.

What you receive

  • Wireframes for every page type
  • Designed interface, desktop and mobile
  • A component set the build will follow

What we need from you

Consolidated feedback in one pass per round, not drip-fed.

04 3–8 weeks

Development

The build runs in weekly cycles against a staging URL you can open at any time. You are not waiting for a reveal — you watch it come together and can flag something in week two rather than week eight.

What you receive

  • Weekly builds on staging
  • A short written update each week
  • Access to the repository from the first commit

What we need from you

Content and images as agreed in the plan. This is the thing that slips most often.

05 1 week

Testing

Cross-browser, real devices, every form path including the failure paths, keyboard navigation and a screen reader pass. Performance is measured against a budget agreed in stage two, not hoped for.

What you receive

  • Test report covering browsers, devices and forms
  • Accessibility findings and fixes
  • Performance measurements against the budget

What we need from you

A round of testing on your side with real users, not just the project sponsor.

06 1–2 days

Launch

Migration, redirects, analytics, Search Console and DNS, done in one planned window rather than piecemeal. For a rebuild, the redirect map is agreed with you before anything goes live.

What you receive

  • Redirect map applied and verified
  • Analytics and conversion tracking live
  • Sitemap submitted and indexing requested

What we need from you

A launch window, and access to DNS and any existing analytics accounts.

07 4–8 weeks after

Optimisation

What happens after launch matters more than the launch. We watch the real numbers — where people drop out, what search terms arrive, what the Core Web Vitals field data says — and fix what the data shows rather than what we assumed.

What you receive

  • A review at 30 and 60 days with real figures
  • A prioritised list of fixes and quick wins

What we need from you

Nothing. This is on us.

08 Ongoing

Support

Updates, backups, monitoring and changes. Either a monthly retainer with fixed hours and priority response, or on demand at an hourly rate. There is no lock-in either way — the code and hosting are yours.

What you receive

  • Security updates and backups
  • Uptime monitoring
  • A named person who knows your project

What we need from you

Tell us when something changes in the business. Most support requests are really new requirements.

Communication

How we work together across time zones

Overlapping hours

We work 11:00–19:00 IST, which is 05:30–13:30 UTC. That covers the UK morning, the full working day in the Gulf and the European afternoon. For US clients we schedule calls and keep everything else asynchronous.

One weekly written update

Every Friday: what shipped, what is next, what is blocked and what we need from you. Short enough to actually read.

Direct access

You talk to the developer building your project. No account manager relaying messages, and no ticket queue for a question that takes a minute to answer.

Questions

About how we work

That is normal, and it is the single most common reason projects slip. We plan for it: the content each page needs is listed in stage two, with a date. If writing is the blocker, say so early and we can help structure it or bring in a writer.

Next step

Start with a conversation

Describe what you are trying to build. We reply within one business day.

Discuss your project