От халепа... Ця сторінка ще не має українського перекладу, але ми вже над цим працюємо!
Hi! This website uses cookies. By continuing to browse or by clicking “I agree”, you accept this use. For more information, please see our Privacy Policy
Free AI project estimator
Your project, estimated in minutes
Upload the document that describes what you want built. Our AI reads every page, breaks the scope into work blocks and prices each one against the 250+ projects we have delivered — then hands you a full breakdown in hours.
No account. No email required. The estimate appears on screen.
What you get back
Not a number in an email. A breakdown you can take into a planning meeting.
A range, not a guess
Minimum, likely and maximum hours across every discipline. The distance between them is a fair measure of how much your document still leaves open.
A breakdown by discipline
Every work block, grouped by design, engineering, QA and management — with its own hours, not one lump sum.
Where each number came from
Each block is labelled: anchored to historical data, inferred by AI, or derived from our delivery formula. You can see which half of the estimate is the soft half.
The open questions in your brief
Decisions your document leaves undecided — the ones that actually move the total once somebody answers them.
Possible missing scope
Work your brief implies but never explicitly asks for. Listed separately, and deliberately not counted in the totals.
A PDF you can forward
Leave an email and we send the full document — method, breakdown, assumptions and risks — written for the person who has to approve the budget.
Estimated effort
- Minimum420
- Likely610
- Maximum840
hours
- Onboarding and authentication 96–140
- Booking flow and calendar 160–230
- Admin dashboard 48–80
- QA and release management 70–110
Illustrative only — your estimate is generated from your own document.
How the estimate is produced
A number is worth only as much as the method behind it. Here is exactly what happens to your document. The whole run takes a few minutes — larger documents take longer, and you can leave an email at any point and get the finished estimate sent to you instead of waiting on the page.
1.
We read the whole document
Every page, not a sample. The description, platforms and user roles we found are printed back to you first, so you can check we read you correctly before you look at a single number.
2.
We split the scope into work blocks
One feature is rarely one cost — it usually needs design, engineering, QA and management time, and pricing it as a single line is how estimates go wrong. So the scope is broken into discrete blocks and assigned to disciplines.
3.
We price each block against work we have already delivered
Every block is matched against our delivery history — 250+ launched projects — before anything is inferred. Where a real comparable exists, its recorded hours anchor the block. Where none exists, the block says so, in the breakdown you get.
4.
We give every block a range, not a number
Minimum, likely and maximum per block, then totalled. A single number would hide the uncertainty that actually drives a budget decision.
What the numbers rest on — and where they stop
Every block carries its basis
- Historical data Anchored to hours actually recorded on comparable work in past projects. The firmest part of the estimate.
- AI-assisted No close comparable existed, so the hours were inferred from your scope description. Treat these as the softer half.
- Delivery formula Derived from our standard delivery ratios — the QA, management and release overhead that applies to any block of engineering work.
And a confidence level
- High The scope is described clearly enough that we would defend this figure in a planning meeting.
- Medium The scope is understood, but it leaves choices open that move the number.
- Low Your document says what is wanted but not enough about how. Expect this figure to move once the open questions are answered.
What this method cannot do
It cannot estimate what your document does not say. Nobody has spoken to your team, seen your existing codebase, or tested any of the assumptions the estimate lists. Nothing here accounts for a fixed deadline, a fixed budget, or an integration whose API we have not read. This is a preliminary estimate, not a quote: it does not commit you, and it does not commit us.
What to upload
Anything that describes what you want built — a spec, a brief, a pitch deck, a feature list. The more your document says, the tighter the range comes back.
PDF, DOCX or PPTX · up to 25 MB
A brief that estimates well usually says:
- What the product does, and who uses it
- Platforms — web, iOS, Android, backend
- User roles, and what each one is allowed to do
- A feature or screen list, even a rough one
- Integrations, and anything that already exists
- Constraints you already know: deadline, budget, compliance
Missing half of that? Upload it anyway. A thinner document simply comes back with a wider range and a longer list of open questions — which is useful information in itself.
No document yet?
That is normal this early. Half an hour with our tech lead is usually enough to turn an idea into something worth estimating — or a short Discovery phase will produce exactly this kind of document, along with a validated backlog and a plan.
Your document stays yours
No account, no email gate
You upload a file and the estimate appears. An email address is only ever asked for if you want the PDF sent to you.
The upload is deleted as soon as it is estimated
Your file is used to produce your estimate and removed once the job leaves the queue, with an automatic sweep as a backstop.
The estimate itself is not kept forever
Finished estimates stay readable from your link for 30 days, then they are pruned automatically.
Sensitive scope? Ask first
If your document needs an NDA in place before it goes anywhere, write to us and a human will answer.
Who is doing the estimating
The delivery history behind every number: a product engineering team that runs its own delivery, so the hours in your estimate are the same hours we plan and track against.
9 years
building software products since 2017
250 +
projects launched
150 +
clients worldwide
80 +
engineers, designers & AI specialists on our team
$ 535M
total funds raised by our clients
Questions people ask before uploading
-
Is it really free?
Yes. No account, no card, no mandatory sales call. We built it because a fast, honest first number is a better introduction than a brochure.
-
How accurate is it?
It is a preliminary estimate produced from your document alone, so the range is a planning tool rather than a quote. Blocks anchored to comparable past work are the firmest part; blocks marked AI-assisted are the softest — and the estimate tells you which is which, block by block.
-
Is this a quote? Does it commit me to anything?
No, to both. It is not a commitment on either side. It is the number we would start a conversation from, and you are free to take it and never speak to us.
-
What happens to my document?
It is processed to produce your estimate and deleted once the job leaves the queue. The finished estimate stays readable from your link for 30 days and is then pruned automatically. If you need an NDA before uploading, write to us first.
-
What file types can I upload, and how big?
PDF, DOCX and PPTX, up to 25 MB.
-
How long does it take?
Usually a few minutes. Large documents take longer — if yours does, leave an email and we will send the finished estimate rather than making you wait on the page.
-
What if I do not have a scope document?
Talk to us instead, or start with a Discovery phase — it produces the document, a validated backlog and a delivery plan you can budget against.
-
What happens after I get my estimate?
Nothing automatic. If you want to go further, you can book half an hour with our tech lead to walk the breakdown and close the open questions we can close for free.
What happens after your estimate
Talk it through with the people who would build it
Half an hour with our tech lead: we walk the breakdown, answer the open questions we can answer for free, and tell you which numbers we would defend and which we would not. No slides.
Book a callOr start with Discovery
If the open questions are the blocker, a short Discovery phase is the shortest path from your document to a fixed scope, a validated backlog and a plan.
Explore Discovery phase
Drop your scope. Get your estimate.
Free, automated, and yours in minutes — with the method printed alongside every number.
Start my estimate
