How We Assess Your Requirements Before Quoting
Before providing a quote, we need to understand your requirements well enough to scope the work accurately. An inaccurate scope leads to inaccurate pricing — which is not in your interest or ours. This article explains our pre-quote process.
Stage 1: Initial Conversation
The first step is an introductory call (typically 30–60 minutes) with your Account Manager. We explore:
- What you are trying to achieve and why
- The current situation and any existing systems
- Constraints: budget range, timeline, team size
- Technical requirements at a high level
- Success criteria — how will you know it worked?
Stage 2: Requirements Gathering
Depending on complexity, we may conduct additional sessions:
- A written requirements questionnaire
- A structured discovery workshop
- Review of any existing documentation, wireframes, or specs you have
- Technical assessment of existing systems (if integration is needed)
Stage 3: Quote Preparation
We prepare a written proposal including scope, methodology, team, timeline, and pricing. For larger or more complex requirements, we may provide a quote for a paid Discovery phase first, producing a detailed specification before committing to a full project price.
Common Reasons for Inaccurate Quotes
- Requirements that are vague or not yet finalised at quote stage
- Undisclosed integrations with existing systems
- Assumptions about data quality that turn out to be incorrect
- Stakeholder disagreement discovered mid-project that requires redesign
The more information you share at quoting stage, the more accurate (and fair) the quote will be. Do not worry about sharing confidential information — our standard engagement is covered by mutual confidentiality obligations from first contact.