Contact us

Quote review

Got a Development Quote? Have a CTO Check It First

A quote is a plan, a price and a set of technical decisions you are asked to accept. Have someone on your side read it before you sign. You get questions to send back, red flags and a plain-English view on whether the plan fits your product.

What the Discovery includes
  • You pay for the assessment. It is not a sales call
  • No Valletta development proposed unless you ask
  • Keeping your chosen vendor is always an option

Why have a CTO review a software development quote?

A vendor writes a quote to win the work, and you cannot easily check it yourself. A CTO reads it against your goals. They check whether the scope matches what you need, whether the estimate has a visible basis, and which technical decisions are already made for you inside the price.

Search for help with a quote and you mostly find contract templates and gig listings. Neither tells you whether this particular plan is sound.

The useful moment is before you sign. After that, every gap in the quote becomes a change request.

What should a software development quote contain?

A sound quote lists the scope and what is out of scope, the assumptions behind the estimate, a breakdown by feature or milestone, payments tied to things you can test, how changes are priced, who owns the code and accounts, and what happens after launch. Missing items usually come back later as cost.

A checklist to hold any development quote against
ItemWhat good looks likeRed flag
ScopeFeatures listed one by one, with what is out of scope stated“As discussed” or a one-line summary
AssumptionsWritten down: platforms, integrations, data volumes, who supplies designsNone stated, so every surprise is billable
Estimate breakdownEffort per feature or milestone, with uncertain parts markedOne total with no basis
TeamRoles and seniority named, plus who leads technicallyHeadcount only, or a team that changes after signing
Milestones and acceptanceEach payment tied to something you can testPayments for time passed
ChangesA written process for pricing and approving changesNot mentioned
TestingWho tests, what is tested and how you accept it“QA included” with no detail
Running costsHosting and paid third-party services listedOnly build cost shown
Code and IPOwnership transfers to you. The repository sits in your accountCode stays in the vendor’s account until a final payment
Accounts and accessCloud, domain, app stores and payment accounts in your nameVendor registers them for you
After launchBug-fix period and support terms written downSilence
ExitHow the handover works if you part waysNo handover terms

A checklist for reading a quote, not legal advice. Contract terms should be reviewed by a lawyer in your jurisdiction.

Rewrite vs refactor, build vs buy: decisions a quote hides

Many quotes carry a decision you were never asked about. A rewrite where a refactor would do. A custom build of something you could buy. A new stack your current team cannot maintain. A CTO names each decision, explains the alternative and tells you which one fits your stage and budget.

In the four AI-built products we audited for founders, the answer was refactor every time. A rewrite is sometimes right. It should come with a reason you can check.

  • Rewrite vs refactor. Rebuilding from scratch resets everything that already works. Refactoring keeps it and fixes what is broken.
  • Build vs buy. Sign-in, payments, admin panels and notifications often exist as services. Building them yourself is sometimes right, but it should be a choice.
  • Stack choice. A technology only the vendor knows makes you dependent on that vendor.
  • Team shape. Senior people on the proposal and junior people on the work is a common gap between quote and delivery.

Rewrite vs refactor: how to tell which one a quote should propose

Refactor when the data model can carry the product and the problems sit in code you can fix piece by piece. Consider a rewrite only when the data model cannot carry what the business needs, and the vendor can show why. The burden of proof sits with whoever proposes the rewrite.

SignalPoints to refactorPoints to rewrite
Data modelFits the product and its next year of growthCannot represent what the business needs
What works todayCore flows work, problems are localLittle works, and fixes break other parts
StackSupported and known by developers you can hireAbandoned or known only by one person
Users and dataLive customers whose data must move safelyNo live users yet
EvidenceFindings ranked by risk, with fixes estimated“The code is bad” with no specifics

How much does software development cost?

No honest single number exists. Cost depends on scope, integrations, the team’s seniority, quality expectations and how much is still unknown. A useful check is whether the quote explains its number. A breakdown per feature with stated assumptions can be judged. A single total cannot.

Two quotes for the same brief can differ a lot. Often they describe different products, because each vendor filled the gaps in the brief differently. A review puts them side by side on the same scope.

How much does a CTO review of a development quote cost?

A first look at the quote is free on the 30-minute call: bring it and the CTO tells you what stands out. A detailed review comes as part of the Fractional CTO Discovery, $4,990 at a fixed price, which also gives you an MVP cost estimate to hold the quote against.

What the Discovery includes

How a CTO reviews a development quote

You share the quote, your brief and any contract draft. The CTO reads them against what you are trying to achieve, lists gaps and risks, and drafts the questions to send back to the vendor. You finish with a clear choice: sign, negotiate specific points, or get another quote.

  1. Share the documents

    The quote, the brief or specification you sent, and the contract draft if there is one.

  2. Read against your goals

    Scope, assumptions, estimate, team, milestones, ownership and the decisions inside the price.

  3. Questions for the vendor

    Specific questions you can send back, so the vendor fills the gaps in writing.

  4. Verdict

    Sign, negotiate named points, or get another quote. In plain English, with the reasons.

What does a quote review look like in practice?

A six-person UK marketplace startup held a fixed-price agency quote of $212,000. Our CTO found seller onboarding priced twice and a custom payouts system that the existing payment provider could handle. He rewrote the scope around what a seller needed to list an item and get paid. The same agency signed for $128,000.

  • Fixed-price quote reduced from $212,000 to $128,000

    The same agency signed for $84,000 less

    A six-person UK marketplace startup was about to spend most of its seed round on an agency build. Our CTO mapped the quote against the first customer journey and found that the agency had priced seller onboarding twice and included a custom payouts system that the existing payment provider could handle. He rewrote the scope around what a seller needed to list an item and get paid. The same agency signed the revised $128,000 contract.

    Client name withheld.

Who reviews your quote?

Vitaliy Makarov usually takes this situation. He runs engineering and delivery at Valletta, a distributed division with more than thirty product engagements behind it, and wrote the delivery framework it works by. He reads quotes from the side that has to deliver them, so he knows where they tend to be thin.

Earlier he took six fintech and blockchain startups from zero to MVP and set up the corporate IT project office for a national airport holding.

The review is independent. No Valletta development is proposed afterwards unless you ask, and keeping the vendor you chose is always an option.

Is your situation a little different?

A quote review often leads to a wider question. Who owns technical decisions once the work starts? Or the work already started and stalled. These pages cover both, and the hub explains the diagnostic and the four technical leaders on the team, so you can see who would answer for your project.

Frequently asked questions

Yes. Send the quote, your brief and the contract draft if you have one. A CTO from our team reads them against your goals and gives you gaps, risks and questions to send back. The first look happens free on a 30-minute call. A detailed review is part of the Fractional CTO Discovery.

A total on its own cannot tell you. Check whether the quote breaks the cost down by feature, states its assumptions and names the team. A high quote with a clear basis can be fair. A low quote with gaps often grows. A CTO compares what you are paying for with what you need.

At minimum: scope, milestones with acceptance criteria, how changes are priced, code and IP ownership, who holds the accounts, confidentiality, support after launch and handover terms if you part ways. This is a general checklist, not legal advice. Have a lawyer in your jurisdiction review the contract itself.

No. You pay for the assessment, so the advice is the product. No Valletta development is proposed afterwards unless you ask, and keeping the vendor you chose is always an option in the review. If the quote is sound, we say so and you sign it.

Send the quote before you sign it

Tell us what you are building, who sent the quote and when you need to decide. On a 30-minute call a CTO takes a free first look at the quote. A detailed review is part of the Fractional CTO Discovery.

Prefer to talk?

Let’s talk