Frequently asked questions
Straight answers before the first call
50 questions, grouped by what you are actually worried about. If yours is not here, ask it — the answer usually ends up on this page.
- Questions answered
- 50Questions answered
- Groups
- 6Groups
- Published pricing — and why
- NoPublished pricing — and why
8 questions
Choosing a partner
For anyone comparing us against other firms.
Brihat Infotech builds custom enterprise platforms for Indian organisations — ERP and CRM cores, AI systems, investor and operator platforms — and then operates them. We work across six practices, but the common thread is software a business cannot switch off for a week.
9 questions
Commercials and contracts
Money, models and the clauses that get tested.
We do not publish prices, because scope drives them and a figure without scope is a guess one of us later has to defend. What we will tell you is what moves the number: integration surface, process variance, data condition, regulatory obligation, non-functional targets, and your own availability.
9 questions
Technology and delivery
Stack, architecture, and how the work actually happens.
It is chosen per engagement against your existing estate, not from a house preference. In practice: TypeScript, Node and React on the front, Python for data and AI, Postgres, and AWS or Azure. If your team already runs .NET or Java and will maintain it, that weighs more than our preference.
8 questions
Security and compliance
The questions your risk and procurement functions will ask.
Least-privilege access requested per environment and revoked at phase end. Where your policy requires it we work inside your network on your devices, and production data is not copied to developer machines.
8 questions
Working together
What the engagement feels like week to week.
A delivery lead and an architect, both named at kickoff and both present through to operations. There is no account manager between you and the engineering, and no hand-off after signature.
8 questions
After go-live
Support, ownership and how you leave.
You do, from the first commit, in your repository under your organisation. There is no runtime licence back to us on custom work. Licensed Brihat products remain ours and you hold a perpetual licence — that split is explicit in every agreement.
Still not answered?
Ask it directly. Questions that come up more than twice end up on this page, which is how it got to 50.
Ask usNext step
Bring us the problem. We will bring the architecture.
A discovery call takes forty-five minutes. You leave with our read on the problem, the shape of the system we would propose, and a straight answer on whether we are the right team for it.
- No sales deck
- An engineer on the call, not an account manager
- NDA before you share anything