Software quote review
Send me the proposal before you sign it.
Email or upload the software proposal you received and I read it the way the people who wrote it hope you will not. Not to make it cheaper, but to find the risks, the assumptions and the gaps that turn into extra cost once the work starts.
What the review does
What happens when I review a proposal.
- 01
I review software proposals from agencies, studios and freelancers.
- 02
I identify the risks hidden in scope, planning and price.
- 03
I challenge the assumptions the quote quietly depends on.
- 04
I help you avoid spending budget on the wrong thing.
- 05
I check who ends up owning the code, accounts and infrastructure.
How it works
From proposal to clarity.
- 01
You send the proposal.
Forward the quote, statement of work or estimate by email, or upload it. A few lines of context about what you are building helps.
- 02
I read it independently.
I have no stake in the build, so I read for what is missing as much as for what is written: scope, assumptions, ownership, responsibility.
- 03
You get a clear next step.
A short call or written reply with the questions to ask, where the price can grow, and whether to sign, renegotiate or re-issue the request.
What you leave with
What you get back.
- 01
A list of concrete questions to put to the supplier before you sign.
- 02
Visibility into where the price and timeline could quietly grow.
- 03
A workable recommendation: sign, renegotiate or re-issue the request.
Relevant frameworks
Read up before we talk.
Reviewing a Software Quote
Most founders review the price first. Experienced founders review the assumptions first. A decision framework for evaluating a software quote before you sign.
Choosing a vendor
The biggest vendor risk is rarely technology. It is dependency. A decision framework for founders evaluating software vendors with the cost of leaving in mind.
Ready to talk?
Not sure about that software quote?
Before spending thousands on software development, let’s look at what is actually in the proposal.