An estimate that shows its working, like a receipt
Three questions, one range, and a rule that the range can never print a number the pricing page does not. How the estimator is built to be honest.
Valentir Engineering Desk
The estimate on the estimator page is a receipt, not a quote. It prints what it was asked, what it assumed and what is excluded, so you can disagree with the line you disagree with. This note is about how it is built, because the way an estimate is built decides whether it is honest.
Three questions#
What is being built, roughly how big, and how soon. That is all. The time model behind it still has seven factors (kinds of user, screens, a mobile app on top, payments, integrations, an admin panel, AI features), but their answers now follow from the first two questions instead of being asked one by one. A long form looks more precise than it is. No short form can price a build. The point is that a visitor can learn the order of magnitude without booking a call, and can see what it assumes.
The model holds no price#
The size picks the package: small is the first package, large the last, medium the one in the middle. The kind of build only positions the range inside that package's published band. A website sits low in it, internal software high, an app in the middle. That is a weight, not a price.
The range is that position, plus or minus a spread, rounded outward to a fixed rupee band, and then held inside the published prices. So it can never print a number the pricing page does not. A package with no public number, the custom-priced one, gives a result with no number at all: the types make it impossible to attach a low, a high, GST or payments to it.
The prices themselves come from the same list the proposals use, which another note describes.
Honest about not knowing#
The spread is plus or minus 22 per cent, and every "not sure yet" answer widens it by one step. Narrower would imply a precision that three questions cannot support. The weeks are the site's own planning range. The price list gives no weeks, so they are shown as a note and never as a charge. GST appears as its own line, from the single rate.
The result is announced politely to screen readers and updates as you answer. The form is a plain GET form that works without JavaScript. It prints as one A4 page with nothing but the receipt on it.
What the tests refuse#
Two source checks do most of the work. One fails if any figure finer than the band is rendered, so no rounding trick can leak a false-precise number onto the page. The other fails if any estimate surface carries a price of its own: the estimator, the home page's small estimate and the hero card all call the same function, and nothing else is allowed to price.
Limits#
It is coarse on purpose. A real quote needs a conversation and a written scope, and the receipt says so in as many words: "A rough guide, not a quote." The planning weeks come from the site's model, not from an average of delivered projects, because the studio was founded in 2026 and does not publish a delivery history. For the reasoning behind the ranges, read the cost guide.
Valentir Technologies LLP is a software studio in Noida.
Get our notes by email
We email our notes when we publish something worth your time.
Search on Google and want more notes like this in your results? Add Valentir as a preferred source on Google.
If you want to argue with any of this, that is what hello@valentir.in is for.
