One persistent challenge faced by technical professionals in many organisations is the pressure to quickly provide project estimates and quotes before adequate information is available. If you’ve found yourself frustrated by unrealistic timelines and vague project scopes, you’re not alone. so here is a guide to help navigate this common issue effectively.
Why Technical Teams Are Asked for Premature Quotes
Typically, this situation arises from organisational structures where business needs are quickly escalated to IT management, who then require immediate answers. The usual questions from management include:
- Can this be done?
- How long will it take?
- How much will it cost?
Realistically, detailed and accurate answers to these questions can require extensive work: proof of concept development, regulatory checks, and feasibility studies, all of which take considerable time and money. Yet, management and the business often expect preliminary estimates within a very short timeframe.
How to Handle Early Project Estimates
Instead of frustration, here’s how you can approach providing an early, preliminary quote:
1. Use Realistic Assumptions
You will inevitably need to make assumptions. To do this well, aim for assumptions that reflect realistic scenarios. A helpful analogy is the question, “How long does it take to travel to Australia?” Although many variables exist, your immediate reaction should not consider extreme scenarios like walking. Instead, you naturally think about common methods, such as flying, use widely available flight times and costs as your baseline.
2. Clearly Document Your Assumptions and Contingencies
Explicitly document all assumptions and known contingencies. For instance:
- Clearly state if the quote assumes completion only up to a specific milestone (e.g., arriving at an airport versus a specific city or location).
- Highlight known potential blockers such as regulatory or security restrictions.
- This approach helps manage expectations and protect against future misunderstandings.
3. Provide a Reasonable Margin of Error
Include explicit language that highlights the preliminary nature of your estimate. Use clear, standardised statements like:
- “This estimate has a potential variance of up to ±20%.”
- “Final quotation requires a proof-of-concept phase of approximately two months.”
- “Security approvals and regulatory checks may significantly impact timelines.”
If you find these notes are frequently removed from presentations by management, formally document these conditions elsewhere (e.g., in emails or follow-up notes).
Common Pitfalls to Avoid
Avoid Extreme Responses
Resist giving overly pessimistic or overly optimistic quotes, as both extremes tend to be ignored or cause pushback from management. Instead, offer balanced, evidence-based estimates.
Don’t Delegate Estimates to the Most Optimistic Team Member
While it’s tempting to delegate unpleasant tasks like estimation to the most helpful person on your team, this often results in overly optimistic estimates. It’s better to have slightly sceptical or more conservative team members lead estimate preparation to ensure realism and accuracy.
Handling Negotiation and Scope Creep
Be prepared for negotiation. Management teams naturally approach quotes as negotiable, even when your technical estimate is realistically calculated without any intentional padding. Counteract potential scope creep or budget reductions by clearly outlining consequences, such as failing compliance or security standards if corners are cut.
Final Thoughts
Early quoting isn’t ideal, but with thoughtful handling, you can provide meaningful preliminary estimates that guide decision-making effectively. Clearly articulated assumptions, contingencies, and evidence-based reasoning can position you as both helpful and realistic, qualities that reinforce your credibility. This means that when inevitable changes need to be made to quotes further on, people are more likely to assume they are reasonable needs.