Understanding the Different Types of Tech Quotes: Which One Is Right for Your Project?

When engaging a tech provider, one of the first discussions will be about the cost of the project. However, not all quotes are created equal. Different types of quotes serve different purposes, offer varying levels of accuracy, and come with their own risks for both the client and the tech provider. Understanding these quote types can help you make an informed decision about the scope, timing, and budget for your project.

In this post, we’ll break down the most common types of quotes you’ll encounter when working with tech providers: Rough Order of Magnitude (ROM), Ballpark, Quote, Fixed Price Quote, and Statement of Work (SoW). Each has its own pros, cons, and ideal use cases, so let’s dive in.

1. Rough Order of Magnitude (ROM)

A Rough Order of Magnitude (ROM) estimate is the least accurate type of quote. It’s often used in the very early stages of a project when there are many unknowns. Typically, ROM quotes are expressed using T-shirt sizes—a simple method of categorising estimates as small (S), medium (M), large (L), or extra-large (XL). This type of quote gives a high-level, rough approximation of cost, but it’s not meant to be precise.

Pros:

• Quick and Easy: A ROM quote can be produced quickly with minimal information.
• Good for Initial Planning: It provides a rough idea of the potential project size, which is useful when you’re evaluating multiple options.
• Low Cost to Produce: Because ROM doesn’t require detailed analysis, it’s low-cost to generate.

Cons:

• Highly Inaccurate: It’s not reliable for budgeting purposes since it’s based on limited information.
• Vague: With so many unknowns, it’s difficult to trust this figure for making decisions.

Risks for the Client:
Clients may underestimate the complexity and cost of a project if they take the ROM as a serious budget figure. There’s a risk of substantial increases as more details become known.

Risks for the Tech Provider:
A tech provider might get stuck in a difficult conversation if the client views the ROM as a firm commitment, even though it’s not intended to be.

When to Use a ROM:
ROM estimates are best used in the very early stages of a project, when you’re trying to get a feel for the scope or compare different potential solutions. It’s a high-level figure to help guide your initial thinking but should never be used as the basis for a budget.

2. Ballpark Estimate

A Ballpark estimate is more insightful than a ROM and is usually expressed as a range (e.g., £100,000 – £150,000). It offers a somewhat more refined look at the potential cost but still leaves room for flexibility as unknowns are clarified. The range indicates a bit more confidence but acknowledges that some details are yet to be fleshed out.

Pros:

• More Accurate than ROM: While still not definitive, a ballpark estimate gives a better sense of what the project might cost.
• Useful for Decision-Making: It helps clients start planning and deciding if the project is feasible within their budget.
• Provides Flexibility: Since it’s a range, it leaves room for scope adjustments.

Cons:

• Still Not Precise: It can be frustrating for clients who are looking for a more concrete figure.
• Broad Range: The gap between the low and high ends of the estimate can still be significant.

Risks for the Client:
Clients might start planning around the lower end of the range, only to find that the final cost ends up at the higher end or even exceeds it.

Risks for the Tech Provider:
There’s a risk that clients will hold the tech provider to the lower end of the range, even though it was presented as a ballpark figure.

When to Use a Ballpark Estimate:
Ballpark estimates are ideal when the project has taken shape but there are still some details that need to be worked out. It’s often used when discussing potential scope and options with stakeholders and provides a more tangible range to work with than a ROM.

3. Quote

A Quote is a more detailed estimate of the project costs. It’s based on a better understanding of the project requirements and usually includes some assumptions about the scope and complexity. While more accurate than a ROM or ballpark, a quote still allows for flexibility if certain assumptions change.

Pros:

• More Detailed: A quote is based on more detailed analysis of the project scope and requirements, so it’s more accurate than earlier estimates.
• Can Be a Foundation for Negotiation: Since it’s based on assumptions, both parties can adjust the scope to meet the budget.

Cons:

• Still Includes Assumptions: A quote can still change if the assumptions turn out to be incorrect.
• Not Fully Fixed: It’s not as binding as a fixed price quote, so there’s room for fluctuation in costs.

Risks for the Client:
If the assumptions are inaccurate, costs can increase, which might require additional budget approval.

Risks for the Tech Provider:
The provider may underestimate certain complexities, leading to scope creep or additional costs if assumptions need to be revised.

When to Use a Quote:
A quote is best used when the project scope is clearer, but there’s still room for negotiation or scope adjustments. It’s useful for budgeting and getting stakeholder buy-in before moving into more detailed planning.

4. Fixed Price Quote

A Fixed Price Quote provides a single, solid figure for the entire project. This type of quote is usually based on a clear understanding of the project’s requirements and scope and is underpinned by detailed assumptions and conditions. Once agreed upon, the price doesn’t change unless the scope changes.

Pros:

• Clarity and Certainty: The client knows exactly what they will pay, which makes budgeting easier.
• Low Risk for the Client: The risk of overruns falls to the tech provider, not the client.

Cons:

• Rigid: Fixed price quotes leave little room for flexibility if the project’s requirements change.
• Higher Cost for the Provider: The tech provider must factor in the risk of overruns, which can make the quote more expensive.

Risks for the Client:
The main risk is scope limitation. If the project evolves or if new requirements come up, the fixed price may not cover them, leading to additional change requests and costs.

Risks for the Tech Provider:
All of the risk falls on the provider. If the project runs over budget or takes longer than expected, the provider absorbs the additional cost.

When to Use a Fixed Price Quote:
A fixed price quote is best used when the project scope is well-defined and unlikely to change. It’s ideal for clients who want clarity and are working with a set budget. However, both parties must be clear on the assumptions and conditions to avoid misunderstandings.

5. Statement of Work (SoW)

A Statement of Work (SoW) is a highly detailed, contractual agreement that outlines the specific deliverables, timelines, costs, and conditions of the project. While SoWs are traditionally used for larger projects, at Atomise, we don’t limit them to just big engagements. We use them across projects of various sizes to ensure clear expectations and deliverables. Importantly, any changes to the scope or cost during the project often require a formal change control process to be approved.

At Atomise, we understand that flexibility is critical to maintaining momentum and avoiding friction. Our SoWs are designed with that in mind, giving you the flexibility to adapt where necessary without always having to invoke formal change requests. This ensures that we can keep velocity high while reducing unnecessary back-and-forth between parties.

Pros:

• Contractual Clarity: A SoW outlines clear deliverables and costs, making it a legal document that both parties must follow.
• Change Control: Provides a structured process for managing changes, ensuring that any adjustments are well-documented and agreed upon.
• Built-in Flexibility: At Atomise, our SoWs are designed to include flexibility, allowing changes to be managed more smoothly, which increases efficiency and keeps the project on track.

Cons:

• Rigid and Formal: SoWs can be rigid, and changes can be time-consuming due to the formal change control process.
• Higher Cost of Adjustment: If changes are necessary, the client may face additional costs, as the process for amending the SoW is more complex.

Risks for the Client:
The client is locked into the terms of the SoW. If they want to change the scope, it requires a formal change control process, which can be costly and delay the project.

Risks for the Tech Provider:
If the SoW isn’t clearly defined upfront, the provider may find themselves caught in disputes about deliverables or expectations, making it critical to have clear terms and conditions.

When to Use a SoW:
A SoW is best used for projects where clarity, accountability, and structured change management are crucial. While ideal for complex or longer-term engagements, SoWs can also be applied to smaller projects to ensure expectations are aligned and the project is delivered efficiently, with room to adjust when needed.

Picking the Right Type of Quote

Each type of quote serves a different purpose and carries different risks for both the client and the tech provider. At Atomise, we work closely with our clients to understand their needs, the project scope, and their comfort level with risk before deciding on the right approach. Whether it’s a ROM for early-stage planning, a ballpark estimate for strategic discussions, a detailed quote for budgeting, a fixed price for well-defined projects, or a Statement of Work for large engagements, we believe in full transparency and clear communication every step of the way.