Agile embraces uncertainty. An agency must give a price and deadline. These worlds collide in every agile project. The goal isn’t to choose — it’s to build a process that reconciles both.
Why It Hurts
Story points don’t convert to currency. They measure relative complexity, not time. Converting points to money requires velocity — which varies by team, technology, and phase.
Velocity isn’t a constant. It drops at project start, changes with team rotation (normal in agencies), depends on backlog quality. Linear extrapolation kills accuracy.
Scope changes destroy margin. In agencies, every scope change is margin pressure.
Client pressure for one number. If you can’t convert uncertainty into a defensible number — you’ll do it under pressure and get it wrong.
How to Fix It
Step 1: Estimate in Ranges, Not Points
For clients, use three-point estimation: “4–8 months depending on decisions we’ll make.”
Step 2: Separate Sprint Estimation from Contract Pricing
Two different activities with different tools.
Step 3: Build a Learning Curve
After every project, compare estimates vs actuals.
Step 4: Design Contracts for Agile
Fixed budget, variable scope. Milestones. Explicit change workflow.
Step 5: Sanity Check Every Estimate
Does it cover all cost categories? Is it consistent with history?
Where Apropo Comes In
Apropo connects agile estimation with contract pricing. Changes go through a workflow: request → impact estimate → client approval → automatic update.
Summary
Stop choosing between “agile but no price” and “price but no agility.” Build ranges, separate sprint/contract estimation, use historical data, design contracts for variable scope.