Pricing on the page: why consulting firms hide the number — and what happens when you don't

We published seven fees on the public site. Three things happened that we did not expect. None of them were about pricing.

Consulting firms hide their numbers for the same reason poker players hide their hands: they think information asymmetry is the product. It is not. It is a cost the buyer pays for the privilege of being sold to. Every quote-to-quote conversation, every ‘tell us your budget’ dodge, every SOW that lands after three weeks of scoping calls — all of it is motion, not progress. The buyer is always paying for that motion, just not on an invoice.

We tried the other thing. Seven engagements, each with a number on the public website, ordered smallest to largest. It did three things we did not expect.

Every enterprise procurement lead we've talked to in the last year has said some version of this: ‘I shortlist priced-upfront vendors first because I can do budget authorisation in parallel with the technical eval.’ Without a price on the page, the procurement lead has to schedule a call, then a quote, then internal authorisation, then the technical eval. Four sequential blockers. With a price on the page, those four blockers become two parallel ones. Across our six-month window, priced-upfront shortlisting happened at roughly 2.1× the speed of RFQ-style engagement.

If a ₹60-lakh engagement scares your prospect, the scoping call wasn't going to produce a deal anyway — it was going to produce four wasted hours and a polite decline. Publishing the number filters in advance. Roughly 40% of our inbound does not convert to a call; the people who do book a call have already self-qualified against the fee. That is a massive efficiency gain for a small firm.

“The number on the page is the first proof of discipline. If you can’t produce a number, the buyer concludes you don’t know what the engagement costs you — and they’re probably right.”

This is the counter-intuitive one. We expected the price to be primarily an efficiency lever. It turned out to be primarily a trust signal. The number on the page, reinforced on every service page, reinforced in every case study (‘₹8 crore first-year ACV, two-week Spark engagement that unblocked it’), tells the buyer: we know what our time is worth; we don't hide the cost; we don't gouge. That is a cheap signal that most of our category refuses to send.

Priced-on-the-page only works for productised engagements — tight scope, repeatable shape, known-good playbook. Seven of our services are productised (Spark, Forge, Build, Helm, Prism, Shield, Pulse). Custom platform work is not. We publish the structure of custom pricing (named milestones, per-milestone fee) on the Build page, but the absolute amount depends on scope.

Pricing-on-the-page also requires commercial discipline you don't have on day one. When we started, Spark was ₹4L. Twelve engagements in, we knew it was actually ₹6L of work. We raised the number publicly. That is hard the first time. It gets easier.

If you are a consultancy right now: publish one number on one service. The lowest-risk productised shape you ship. Watch what happens to your inbound quality over the next 60 days.

If you are a buyer and every consultancy you evaluate wants a scoping call before showing you a number: that is information. It is probably the only information you need.