Skip to content
Brihat InfotechBrihat Infotech

There is no price on this page. Here is what determines it.

Scope drives cost, and a figure without scope is a guess one of us has to defend later. What we can tell you is exactly what moves the number — and roughly where it goes.

How we engage

The short answer

Brihat Infotech prices engagements after a fixed-price discovery phase rather than publishing rate cards. Cost is driven mostly by integration surface, process variance and data condition — not by headcount or feature count. A first call will give you an honest band before you spend anything.

Six things that move an estimate, in order.

Notice what is not on this list: number of screens, number of users, and how many features are in the spreadsheet. Those correlate with cost far less than people expect.

01Largest

Integration surface

How many systems must keep working, and how well documented they are. The largest driver by a distance and the one most often missed — usually by whoever wrote the requirements.

02Large

Process variance

One way of working across five sites costs a fraction of five ways across five sites. Harmonising first is frequently the cheaper project.

03Large

Data condition

Migrating clean data is a task. Migrating data two departments disagree about is a project, and the reconciliation nobody scoped is where months go.

04Medium

Regulatory obligation

Audit trails, retention, residency and the review you have to pass. Cheap at architecture, expensive at acceptance.

05Medium

Non-functional targets

Concurrency, latency and uptime. The gap between 99.5% and 99.95% is an architecture and an on-call rota, not a configuration setting.

06Underrated

Your availability

The one driver on your side of the table. Decisions that wait a fortnight for a committee slot lengthen an engagement more reliably than any technical difficulty.

Roughly how a platform budget splits.

Indicative proportions rather than a rule — but if a proposal has no Prove phase and no hypercare, that is where the risk went, not where the saving came from.

Discovery
10–15%
Process mapping, architecture, the phased plan. Separately priced so you can buy only this.
Build
55–65%
Engineering, design and delivery management through to the first production release.
Prove
10–15%
Security testing, performance, UAT and the cutover rehearsal.
Hypercare
5–10%
The weeks after go-live at build intensity, because that is when reality arrives.
Contingency
10%
Named, not hidden in the estimate. Unused contingency is not invoiced.
Asked in every first call
More commercial questions

Because ballparks anchor. A number given before discovery is either padded for the worst case, in which case you overpay or walk away, or optimistic, in which case one of us is disappointed in month four. What we will do on a first call is tell you which of the drivers above dominate your situation, and roughly how far apart the cheapest and most expensive credible shapes are. That is a band, not a quote, and it costs nothing to ask for.

Ask for a band

Describe the scope and we will tell you which drivers dominate it.

A band, not a quote — roughly where the number lands and what would move it. A figure without scope is a guess one of us has to defend later.

  • No sales deck
  • An engineer on the call, not an account manager
  • NDA before you share anything