How we calculate prices: where ranges come from

In short. The range in the calculator is not a guess. The calculator takes the nearest row of our price list, splits the description into modules, adds the add-ons from the price list — an admin panel, online payment, urgency — and a margin for uncertainty. The range never goes below the minimum project (3 000 ₴) or below the “from” of its row, and it goes above the row's top only by add-ons we wrote down ourselves. The more details, the narrower the range.

The calculator on the site shows a price range, a timeline and a breakdown by module in half a minute. A fair question: where do these figures come from? The short answer: from our price list, not off the top of our heads. Below — how exactly a task description becomes a range, what the result shows and what to do to make the range narrower. The prices by type are in the articles on Telegram bots and Mini Apps; this one is about the mechanics.

Where the figures come from: our price list

It all starts with the price list — the same one our assistant in Telegram quotes from. Each row is a typical project: the “from”, the typical range and the minimum timeline. For example, a booking bot is 6 000–14 000 ₴, from 2 days; a Mini App storefront — 25 000–60 000 ₴; a landing page — 8 000–17 000 ₴. The full list is on the pages for bots, Mini Apps and websites.

We keep the price list ourselves and edit it by hand when we see a range drifting away from reality. The calculator picks up a change within a minute, without a new release of the site. Even the amounts in this article are not typed by hand: they are taken from the same price list.

Six steps from a description to a range

1. Modules. The calculator looks for familiar blocks in the description — a catalogue, a cart, payment, booking, an account, an admin panel — and takes the amount of work for each from our table. No amount here is made up.
2. A price-list row. The nearest row is chosen by the product type and the modules: a catalogue bot, a booking bot, a Mini App storefront, a landing page. It sets the “from”, the top of the typical range and the minimum timeline.
3. The base. The amount of work of the modules is multiplied by our rate — the calculator shows it in the “What it is made of” block.
4. Add-ons. An admin panel is +20–40 %, online payment +5 000–15 000 ₴, AI features +10 000–30 000 ₴, an extra interface language +10–15 %, the “Urgent” box +20–50 % depending on complexity. If the row already includes payment — a bot with payment, a Mini App with payment, a shop — payment is not charged a second time.
5. A margin for uncertainty. The less is known about the task, the wider the range. The calculator judges how complete the description is and shows it on the “Confidence” gauge.
6. Limits and rounding. The range never goes below the minimum project — 3 000 ₴ — or below the “from” of its row. It goes above the row's top only by add-ons from the price list: the margin for uncertainty does not lift the price beyond the list. Finally the amounts are rounded — and it is always “from … to …”, never one number.

The timeline is worked out from the same amount of work: the calculator shows it in weeks and never sets it shorter than the minimum timeline of the price-list row.

What the calculator does not know: how many external systems need connecting and what their API is like. It notices a CRM, delivery or spreadsheets in the description as modules, but the price-list add-on for each integration — +5 000–15 000 ₴ — we add after the brief, once the list of systems is clear.

What the result shows

• The range and the “by the price list” marker. A bar from the minimum to the maximum, and the marker on it shows where the price-list calculation lies before the margin for uncertainty.
• Confidence. Low, medium or high: the higher it is, the narrower the range.
• A timeline in weeks — with a demo every Friday.
• Modules. An amount for each block; together they make up the whole range.
• What it is made of. The price-list row, the rate, the add-ons, urgency, the margin for uncertainty, the minimum project — every value the range came from.
• Not included. What the price does not cover or what needs clarifying.

What no range includes: hosting and a domain, the content — texts, photos, products. For some rows also the payment provider's fees or the API costs of AI. We say so before the start, not at delivery.

How to narrow the range

• Tick the product type — a bot, a Mini App, a website. Without it the calculator guesses the price-list row from the text.
• Describe the scenario in a few sentences — what the client does step by step. A short description gives low confidence and a wide range.
• Name the modules directly — a catalogue, a cart, payment, booking, an account, an admin panel, languages, a CRM or spreadsheets.
• Attach the spec if you have one — materials in hand raise the confidence.
• Tick the options. Online payment and “Urgent” move the range, while “The design is ready” gives no discount: it only means there is no add-on for a custom design.

What to describe and how, so that the estimate is accurate — in the article how to prepare a project brief.

From a range to a fixed price

The calculator gives a ballpark estimate, not a commercial offer, which is why it is marked beta. Then it goes like this:

1. You send the estimate to Telegram — the estimate code keeps the context — or fill in the brief.
2. Within a day you get a range and an indicative timeline from us — now with what did not fit into the calculator: integrations, roles, non-standard scenarios.
3. We write the spec together and fix the exact amount and timeline, which do not change unless the scope does.
4. The start is after a 50 % prepayment; projects from 20 000 ₴ are split into stages paid 40/30/30, each ending with a demo and a payment.

The whole route in detail is in the article how we work.

The figures in this article come from our price list: they are filled in automatically and match the calculator. It will work out the range for your task in 30 seconds.

← All articles