You are not buying hours: why fixed scope wins
Hourly billing shifts all the risk to the client. In BEAM every stage has a fixed price and a defined outcome. Here is why we price this way.
The hourly model has one hidden property: the longer a project takes, the more the vendor earns. You do not need bad intent for that mechanic to work against the client. A missing plan is enough.
What you really buy at an hourly rate
You buy time, not outcomes. The risk of poor planning, scope drift and rework sits with you: every surprise is another invoice. The vendor has no economic reason for the project to finish sooner.
Setting the two models side by side shows where the risk really sits:
| Hourly billing | Fixed scope (BEAM) | |
|---|---|---|
| What you buy | Time | A defined outcome |
| Estimation risk | On the client | On us |
| Vendor incentive | The longer it runs, the more they earn | Finish in scope and on time |
| Price upfront | Unknown, grows with surprises | Known before the start |
The billing model decides whose side the risk is on.
Takeaway: a fixed scope demands a proper plan before the build and our own tooling that removes from-scratch work. You pay for the outcome, not the time spent looking for it.
How BEAM is priced
Each BEAM stage has its own billing model:
- Blueprint: a fixed fee, you pay for a plan, a scope and a recommendation.
- Launch or migration: a fixed price for a defined outcome, a working platform on a concrete date.
- Maintenance & Growth: a retainer with an optional success fee.
- Feature Sprints: bigger features priced separately.
Fixed pricing demands two things from us that are healthy anyway: a proper plan before the build (hence the Blueprint) and our own tooling that removes from-scratch work (hence the Platform Starter and the AI Content Engine). We take the estimation risk because we have data from previous deliveries.
When fixed price does not work
Honestly: a fixed scope does not survive changing your mind mid-build. That is why the MVP scope is locked before the start, and everything beyond it lands in the backlog as a future sprint. It is not a limitation, it protects the date you care about.
FAQ
Why do you not bill by the hour?
Because hourly billing shifts the risk of planning and rework onto the client, and the vendor has no reason to finish sooner. We take the estimation risk because we have data from previous deliveries.
What if I change my mind mid-build?
The MVP scope is locked before the start. New ideas are priced separately as a Feature Sprint, to protect the date you care about.
How is the fixed price set?
After the Blueprint: the plan and scope turn a range into a concrete number, and we take the estimation risk on ourselves.
What does each BEAM stage cover?
Blueprint is a fixed fee for a plan, Launch or migration is a fixed price for a working platform, Maintenance & Growth is a retainer, and bigger features are Feature Sprints.
Journal
Co-founder of Seedlight · eCommerce platforms, AI, SEO and GEO
Newsletter
The Journal, straight to your inbox
New articles and lessons from real builds, every now and then. No spam, unsubscribe with one click.
