External website; opens in a new tab.

Working with YBT

How do you compare software quotes with very different totals?

Normalise scope, assumptions, evidence and ongoing responsibilities before comparing price; an estimate and a capped commitment are different offers.

Working with YBT

Source review 21 November 2026

A large difference in quoted price may reflect scope rather than efficiency. One supplier may include discovery, permission controls, testing, migration, training and handover; another may price only a prototype. Ask each to explain the deliverables and exclusions in language the business can evaluate.

Compare the decision you are buying

A discovery assignment should produce useful findings and options even if no build follows. A prototype tests an idea and may deliberately omit production reliability. An operational system needs its agreed security, data, recovery and support controls. Do not compare those three as though they were the same product.

Create a simple comparison table: outcomes, users/volumes, features, integrations, supported platforms, data migration, accessibility, test evidence and acceptance criteria. Identify customer content/data inputs and decisions. If the requirements are uncertain, a smaller bounded first stage can be more honest than a precise whole-project number.

Understand the charging mode

Fixed price buys the stated scope, subject to separately agreed changes; internal overspend does not automatically change the customer amount. Time-and-materials needs agreed rates, reporting, minimums and authority. A cap is a spending boundary and needs a clear stopping/review point. An estimate is not a cap unless the agreement makes it one.

Check payment stages, tax wording, supplier subscriptions, travel and ongoing service charges. Do not assume “plus VAT” is appropriate for every trader or that every third-party cost is recoverable. Compare total customer commitments, not an initial deposit alone. Hardware or other supplier commitments may need specific prepayment and returns treatment.

Ask for proof and portable ownership

A proposal should state how the supplier will verify the system and what remains outside its test scope. Ask about error/permission paths and recovery, not only a polished success screen. Keep engineering verification, delivery approval and customer contractual acceptance separate. A production release also needs its own authority and recovery prerequisites.

Clarify ownership of customer-specific source, reusable supplier tools, third-party/open-source licences and primary accounts. Ask what a replacement maintainer would receive and what continuing costs are unavoidable. “You own it” is incomplete if a necessary component sits in a private account the customer cannot access.

Finally, compare who will deliver and support the work, actual capacity and escalation. AI assistance may be a useful part of a controlled process, but it does not remove the supplier’s agreed verification or confidentiality responsibility. Avoid both a promise of infallible automation and a blanket permission to send confidential material to any tool. The best quote is understandable, supportable and matched to the actual business need—not simply the lowest number.

Sources and review

Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.

Next review: 4 May 2027

Related services

How Yellow Brick Tech can help.

Next step

Need to apply this to a real situation?

Ask a question or choose the closest project route. A short conversation can often clarify the next step.