Do I need a specification or an approved budget?

No. Those are outputs of a discovery phase rather than entry requirements for a conversation. A description of what is slowing the business down is enough to make the forty-five minutes useful.

Can we sign an NDA before the call?

Yes. Send yours or ask for ours, and mention it in the booking notes — it does not delay the slot. Share only what you are comfortable with until it is in place.

What if it turns out you are not the right firm?

We say so on the call rather than afterwards, and where we can we name someone better placed. You still get the written read on the problem.

Who else will be on it?

An architect, and usually the founder. No account executive and no panel — the people on the call are the people who would do the work.

Forty-five minutes on the problem.

Discovery calls are run by architects, not account executives. Bring the problem; leave with a considered read on it — whatever you decide about us.

No deck
No account executive
A written read either way

Send a brief Book a call

How the forty-five minutes run

You talk, we interrogateTwenty minutes on the problem: where the friction is, what you have tried, what success looks like. Expect precise questions.
We think out loudFifteen minutes of our read — how we would architect it, what the phases look like, where the risks hide. Answered live rather than taken away.
You leave with a directionTen minutes on next steps: a discovery proposal if it fits, a pointer to someone better placed if it does not. You leave knowing which.

Slots are confirmed personally — you will hear from us within a few working hours. An NDA before the call is welcome; mention it in the notes.

Or reach us directly

hello@brihatinfotech.com
+91 62021 26679
Message us on WhatsApp
Ranchi, Jharkhand · Noida, Delhi NCR
Mon–Sat, 10:00–19:00 IST

An architect, and usually the founder.

The people on the call are the people who would do the work.

A principal architect

Whoever is closest to the problem you describe. They will ask about constraints and integrations before they say anything about solutions.

The founder, usually

On most first calls. The firm is small enough that this is possible, and the practice is deliberate enough that it stays that way.

Nobody else

No account executive, no note-taker, no panel. Two people and forty-five minutes is enough to work out whether there is anything here.

Bring these. Nothing else.

You do not need a specification, a budget approval or an internal consensus. Those are outputs of the process, not entry requirements.

A description of what is slowing the business down — in your words, not in requirements language.
What you have already tried, including the things that did not work.
Roughly what systems are involved and roughly how old they are.
Who inside the organisation would have to agree before anything happens.
Any hard constraint: a regulator, a deadline, a system that cannot be touched.

What you leave with

Our read on whether this is a software problem at all.
The shape of an approach, and roughly how long it would take.
The two or three risks we would worry about most.
A written summary within the week, yours to circulate or to hand to another firm.

All of that regardless of what you decide about us — including a straight no if that is the right call.

Before the call

Nothing, and there is no obligation attached to it. The written summary that follows is yours to circulate internally or to hand to another firm.