We get asked for a price before a project's been discussed in any detail more often than you'd expect, and we understand the instinct — but a number given before scoping is just a guess wearing a price tag. Here's what actually happens before we quote.
We start by asking about the goal, not the feature list
The first conversation is usually less about "we need a website with X, Y, Z pages" and more about what the business is actually trying to achieve — more enquiries, a way to sell online, a tool to replace a manual process. The right scope often looks different once the underlying goal is clear.
We identify what's actually custom vs standard
Most projects are a mix of standard, well-understood work (a marketing site, a typical e-commerce setup) and a smaller number of genuinely custom requirements. Separating these matters, because the custom parts are where timeline and cost risk actually lives.
We agree scope in writing before development starts
Once we understand what's being built, we put the agreed scope, timeline, and price in writing before any code gets written. This protects both sides — you know what you're getting and when, and we're not guessing at requirements mid-build.
Why this leads to fewer surprises later
Projects that skip proper scoping are where "scope creep" and budget disputes usually come from — not because anyone acted in bad faith, but because nobody agreed on the boundaries upfront. A slower start with real scoping consistently leads to a smoother, more predictable project overall.