How We Estimate a Project With Half the Requirements Missing
A working note on estimating with unclear requirements — what matters, what does not, and where these projects usually go sideways.
Most conversations about estimating with unclear requirements start with a tool comparison. They should start with the workflow. This post walks the order we actually use.
What breaks first
With estimating with unclear requirements, the first failure is almost never technical. It is a mismatch between what the team thinks was agreed and what a customer expects.
Engineering then absorbs the gap, quietly, until a release slips.
Two real shapes this takes
One common pattern we see: the product works and the process around it does not. Nothing in the code needs changing, but three people are doing manual repair work every day.
The other pattern is the reverse. Process is fine, the system cannot hold the shape the business now needs.
The fixes have almost nothing in common, so guessing is expensive.
The mistakes that repeat
A mistake teams often make with estimating with unclear requirements is starting from the most complex customer. Build for them and the simple case gets buried in configuration.
- Designing for a customer you have not signed yet.
- Copying a pattern from a company with fifty engineers.
- Deferring the boring part — permissions, exports, error states — until it blocks a deal.
- Measuring activity instead of outcome.
The engineering view
From inside the codebase, estimating with unclear requirements reduces to three questions. What happens when a step fails halfway. Who finds out. How you reverse it.
Design for partial failure before you need it. Step three fails after one and two already succeeded, and that is the case people skip.
Give retries a ceiling and some jitter. A retry storm is an outage you built yourself.
The sequence we use
- Map the workflow on one page, including the manual steps people are embarrassed about.
- Mark where money, time, or trust is being lost.
- Choose one of those, not three.
- Define what "better" means numerically before building.
- Ship a narrow version behind a flag.
- Compare a two-week window either side, then decide.
What good practice looks like here
- One owner, named, with time actually cleared.
- Limits enforced in code so a bad day cannot become a bad invoice.
- A short written record of why the choice was made.
- Alerts that a human reads, not a dashboard nobody opens.
- A scheduled review, because every decision here has a shelf life.
The trade-offs nobody puts in the proposal
Every option here buys you something and charges you elsewhere. Faster now often means a rewrite later, and that can still be the right call.
What matters is naming the bill in advance so it is a decision rather than a surprise.
Where the common advice is wrong
“Do it the way the big companies do.” Their constraint is coordination across many teams. Yours is probably two engineers and a deadline.
“Automate everything.” Automate the repeated, boring, high-volume part. Leave judgement to people.
“Wait until we have more data.” Ship something small and the data arrives.
Frequently asked questions
When is the right time to revisit the decision?
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
How long does estimating with unclear requirements take to get right?
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
What is the most common mistake with estimating with unclear requirements?
Scoping too wide. Covering every case in version one delays feedback and raises cost without a matching benefit.
Is it cheaper to buy a tool instead?
Often yes for the first version. Build when the workflow is a genuine differentiator or no tool fits the data you already hold.
How much should we budget?
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
Conclusion
The useful move on estimating with unclear requirements is almost always the smaller one. Ship a narrow slice a real user can touch this month, measure it, then decide what earns the next four weeks.
Everything gets easier once something is live.
Related reading and next steps
- AI product engineering — how we run this kind of work.
- AI automations — where this often connects.
- More writing from the team.
Want a second opinion on estimating with unclear requirements for your setup? Book a 30-minute call. If it is not worth building, we will say so.
FAQ
Frequently asked questions
When is the right time to revisit the decision?+
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
How long does estimating with unclear requirements take to get right?+
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
What is the most common mistake with estimating with unclear requirements?+
Scoping too wide. Covering every case in version one delays feedback and raises cost without a matching benefit.
Is it cheaper to buy a tool instead?+
Often yes for the first version. Build when the workflow is a genuine differentiator or no tool fits the data you already hold.
How much should we budget?+
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
Building something similar?
Let's talk in 30 minutes.