Built for the problems software templates cannot solve.
Organisations bring us the problems that do not fit off-the-shelf software. We bring the discipline to understand them and the engineering to solve them.
See our workFrom building software to engineering answers.
Brihat Infotech began as a development services firm — websites, apps, the full catalogue. Delivering a hundred of them taught us something the industry rarely admits: most software projects do not fail in the code. They fail in the two months before the code, when nobody asked the right questions.
So we rebuilt the company around the questions. Engagements now start with requirement engineering and process discovery, and end with platforms enterprises actually run on — AI systems, custom ERP and CRM cores, and licensed products like Brihat EHS and Brihat Books that we stand behind ourselves.
The work that proves it is IRFC Invest: the application where Section 54EC bondholders view and track their holdings, engineered by our team for one of India's most trusted financial institutions and operated by them ever since.
AP
Animesh Pathak
Founder
“Almost none of the projects that went wrong went wrong in the code.”
I started Brihat building whatever was asked for. Websites, apps, integrations — the full catalogue, and a hundred of them delivered. What that taught me is not a thing the industry says out loud: almost none of the projects that went wrong went wrong in the code. They went wrong in the eight weeks before the code, when nobody asked what the business actually did.
So we stopped taking briefs at face value. Every engagement now starts with someone from our side on your floor, watching the work happen, before a single module is proposed. It costs us four weeks we could have billed as development. It is the reason the platforms we build are still running years later, and the reason I will tell you in a first meeting if a packaged product would serve you better than anything we could build.
The other thing I decided early: you own it. The source from the first commit, the documentation, the decisions and the reasoning behind them. If you want to take it in-house or hand it to another firm, that should be a Tuesday, not a negotiation. A supplier who makes leaving difficult has stopped competing on the work.
If you are weighing a platform decision that your organisation will live with for a decade, I am worth forty-five minutes of your time — even if the answer at the end of it is that you should not build anything at all.
Animesh Pathak
Founder, Brihat Infotech
How an engagement is structured.
01
Discovery is a contracted phase
Two to six weeks, paid, ending in four artefacts: a problem definition, current-state process maps, a constraint register, and a sizing. The build is proposed after that document exists, not before.
02
Architecture is sized for year five
For the transaction volume, integrations and audit obligations of year five rather than the demo needed next month. The cheapest system to build is rarely the cheapest to own.
03
The team that builds it operates it
One team from discovery through to production operations, under SLA. The people carrying the pager are the people who chose the shortcut.
04
Discovery can end in a recommendation not to build
Where a packaged product covers the need, the written recommendation says so. The artefacts are yours either way, and they are written to be buildable by anyone.
What we build.
Five kinds of work. Each one is something we operate afterwards, which is the constraint that decides what goes on this list.
- Platforms an organisation runs on — ERP and CRM cores, investor systems, operator consoles.
- AI that reaches production with an audit trail, not a pilot that impresses a board.
- The integration layer between what you are building and what you already run.
- Operating what we build, under SLA, rather than handing it over at go-live.
- Licensed products we maintain ourselves, so we live with our own decisions.
Small enough to reach, structured enough to carry it.
The quiet question behind a large engagement is whether a firm this size can actually deliver it. Here is the shape of the answer.
Six practices
AI, platform engineering, data and cloud, digital experiences, advisory, and dedicated teams. Each staffed by engineers who ship and then operate.
One delivery method
Five phases, the same on every engagement regardless of practice. A client moving between practices does not learn a new process.
No sales engineers
The people in your first meeting are the people who would do the work. Nobody hands you over after signature.
No reseller agreements
We hold no vendor certifications and take no implementation commissions, so there is no product we are paid to recommend. Every line we ship is ours to maintain.
Your source, from commit one
Code in your repository, infrastructure in cloud accounts billed to you, documentation signed off as a phase deliverable. Nothing is held as leverage at renewal.
Everything we build is yours, from the first commit.
The terms below are the same on every engagement and are in the contract, not on a slide.
- Source from commit one
- In your repository, under your organisation, from the first day of the build. Not delivered at the end, not licensed back to us for runtime.
- Your infrastructure, your billing
- Cloud accounts in your name with our access granted rather than owned. Revoking it is a permission change, not a migration.
- Documentation is a phase deliverable
- Signed off like any other, including the decisions we would revisit. A handover written after the invoice is a handover nobody reads.
- Exit assistance at standard rates
- Taking it in-house or moving to another firm is a transition phase run at normal rates. There is no exit penalty.
- Escrow on request
- Source escrow with a third-party agent where your risk function requires it.
Who signs off on your platform.
Reachable directly during an engagement. Not a relationship manager standing between you and the engineering.
We are hiring engineersAnimesh Pathak
Founder
Leads Brihat's problem-first practice: map how the organisation actually works before proposing anything, then stay on the engagement long enough to be accountable for whether it gets used.
- ISO/IEC 27001 — Information security management
- ISO 9001 — Quality management
- Ranchi, Jharkhand — Headquarters and engineering
- Noida, Delhi NCR — Delivery and client engagement
Where this starts
Bring the problem that did not fit.
Most engagements here began as something a packaged product could not do. If that is where you are, discovery is the cheapest way to find out what solving it would take.
- No sales deck
- An engineer on the call, not an account manager
- NDA before you share anything