How we work

A clear process. No surprises.

It starts with your problem, not a solution. Every project then follows the same structure through launch and beyond, and you approve each key step.

  1. Step 1: Discover

    We start with the problem, not a solution. Before any wireframe or line of code, we separate what you've told us from what we're assuming, ask about the gaps, and agree what success actually looks like.

    What we learn

    • Your business model and objectives
    • Your audience and what they need
    • The problems you want solved
    • Timeline and budget expectations

    How we do it

    • Consultation call or chat
    • Discovery questionnaire
    • Competitor and market review
    • Written requirements
  2. Step 2: Plan

    We map out the full structure: which pages or screens you need, what features to build and which technologies fit. You review and approve before anything starts.

    What gets defined

    • Sitemap or screen architecture
    • Features and priorities
    • Technology stack
    • Timeline and milestones

    You receive

    • Project scope document
    • Technical proposal
    • Fixed quote
    • A sign-off point before we proceed
  3. Step 3: Design

    We design the layout, typography, colour and components. The goal is clarity and conversion, not decoration for its own sake. You give feedback and sign off before development begins.

    What we design

    • Page layouts and wireframes
    • Visual design aligned to your brand
    • Mobile and desktop views
    • Navigation and user flows

    How we approach it

    • Conversion-focused layouts
    • Clean, modern visuals
    • Feedback rounds included
    • Your approval before building
  4. Step 4: Build

    We build the website, backend, integrations and any custom functionality in the plan. Code is written cleanly, tested thoroughly and documented, so it can be maintained and extended.

    • FrontendInterface, pages, responsive layout
    • BackendAPIs, business logic, integrations
    • DatabaseData model, schema, queries
  5. Step 5: Launch & support

    We deploy to a live server, run final checks and make sure everything works across devices and browsers. After launch we stay available for support, updates and improvements.

    At launch

    • Server deployment and configuration
    • Domain and SSL setup
    • Cross-device and browser testing
    • Performance checks

    After launch

    • Ongoing maintenance
    • Content updates on request
    • New features as you grow
    • Priority support

How we keep it honest

Fast, and still accountable.

The rules every Nirmaan project runs on, whatever it's building.

  • You approve the key decisions

    Scope and price, the implementation plan, going live and handover each need your sign-off. Nothing irreversible happens on an assumption.

  • Evidence, not “done”

    Every requirement is linked to the tests that prove it. When we say something works, we show the results.

  • Changes in writing

    Anything outside the agreed scope comes to you as a change request with its cost and timeline, before any work starts.

  • AI-assisted, human-accountable

    We use AI to move faster on analysis, code and testing. A person reviews every deliverable and is accountable for it.

Common questions

Before you start.

Do you use AI to build my project?

Yes, where it makes us faster or more thorough: analysing requirements, writing and reviewing code, and testing. It never replaces judgement. A person reviews every deliverable, and the key decisions (scope, plan, go-live, handover) are always yours to approve.

How long does a project take?

It depends on scope. A business website usually takes 1–2 weeks and an online store 3–4. A web application with a custom backend takes 4–8 weeks. You get a realistic timeline during planning, before any work begins.

Do I need to provide design assets or content?

If you have a logo, brand guidelines or existing content, we'll use them. If not, we'll work with what you have and guide you on what's needed. Page content (text, images) usually comes from you, and we can advise on structure and messaging.

What if I want to change something mid-project?

Minor changes within the agreed scope are part of the project. If you want significant new features or a change of direction, we'll talk openly about the impact on timeline and cost before going ahead.

Will I own the code when the project is done?

Yes. Once the project is paid for, you own the code and every deliverable. We hand over everything (source code, database schemas, assets) so you're never locked in.

Can you maintain the website after launch?

Yes. We offer ongoing maintenance and support: regular updates, new features, fixes and general improvements, long after the initial project is complete.

Let's begin

Step one is a conversation.

Tell us what you need. No obligation, no pressure: just a conversation about what you want to build.

Tell us your problem Pricing