How a Brihat project runs, from first call to live system

1. 01

   Typically 2–6 weeks

   1. Understand

   An architect and a business analyst map how the work happens today, at your site or at our Noida office. You receive a written problem statement, process maps of how things run now, a list of constraints and a size for the opportunity. We ask for time with the people who do the work, and one sponsor to back it. Discovery is paid, self-contained and yours to keep.

2. 02

   Length set in the plan after discovery

   2. Define

   The architect from discovery is joined by a designer and the delivery lead. Together they produce the target architecture, a phased roadmap, success measures and service levels, and the commercial structure. One decision-maker for scope and one technical contact from your side keep this phase moving.

3. 03

   Length set in the plan after discovery

   3. Build

   The delivery lead and engineers ship a release each fortnight to a live environment, so your team tests working screens. Scope is versioned and a test suite runs on every release. Your product owner gives a couple of hours a week, and reviewers join as modules land.

4. 04

   Length set in the plan after discovery

   4. Prove

   A small team checks the system before go-live: threat model, penetration test and dependency audit; load and failover drills with a written report; user acceptance sign-off; runbooks. You give us a test environment to work in and one reviewer.

5. 05

   Ongoing

   5. Operate

   The architect who built the system stays on. A reliability pod, with a named first and second person on call, runs it round the clock to an agreed service level. You get a quarterly architecture review and a roadmap cycle. Handover to your own team is available whenever you ask.

Stop after any phase and the documents and code from it stay with you.

Fixed scope

The blueprint from Define is the baseline. We price phase by phase, and a change request is priced in writing before any work on it starts.

Dedicated team

You pay monthly for a team that works in your repositories and your process. Changing direction costs nothing extra. A pod has a three-month minimum, and either side can end it with a month's notice and no exit fee.

Build-operate-transfer

We build and run a team or a system for an agreed period under a service level, then transfer it to you. The transfer fee is fixed in the first contract.

You can move from one model to another mid-project by contract amendment, with no penalty.

Dedicated teamsDedicated team or staff augmentationBuild, operate, transfer

We publish no price list. A fixed-price discovery comes first, and your quote follows from it. Six things drive the figure:

• how many systems the new one connects to
• how much your process varies from site to site or case to case
• the condition of your existing data
• the regulations you report against
• your performance and uptime targets
• how much time your people can give each week

Status

a written report every fortnight, and a monthly steering meeting where the project needs one.

Your tools

the work sits in your code repository, task board and build pipeline.

Access

each person gets the least access they need in each environment. Access is revoked when the phase ends.

Scope

every change is priced in writing before work begins.

Decisions

architecture decisions are recorded as short written notes in the repository.

Escalation

issues go to the delivery lead, then the architect, and last the founder.