Insights · 4 min read
What to send a developer before asking for a quote
By Austin Hunter ·
You don't need a technical spec to get a useful quote. You need to explain the problem clearly. A page or two covering the points below lets a developer give you a real number instead of a wide range, and it makes the first call much more productive.
1. The problem, in your words
What's slow, manual, error-prone or missing today? "We track 300 volunteers in three spreadsheets and double-book shifts every month" is more useful than "we need an app."
2. Who will use it
List the types of users (staff, customers, members, admins), roughly how many of each, and whether they'll use phones, computers or both.
3. Must-haves and nice-to-haves
Split your feature list in two. The must-haves set the first version and the price; the nice-to-haves can be quoted as later phases.
4. Examples you like (and don't)
Links to apps or sites that work the way you want, with a note on what you like about each. Screenshots of what you use today help too.
5. What it has to connect to
Payment processor, accounting software, CRM, email platform, an existing database or website. Integrations often drive cost more than screens do.
6. Anything you already have
Existing code, designs, a domain, hosting or app store accounts, and who has the logins. If a previous developer built part of it, say so.
7. Budget range and timing
A rough range isn't a trap; it tells the developer whether to propose a lean first version or a fuller build. Include any hard date, such as a grant deadline, an event or a season.
8. Who decides
Who approves the quote and the work? If a board or committee is involved, mention when it meets.
Send it to us
Our first call is free, and we send a fixed quote after it. If you send these points ahead of time, we can often come to the call with a rough plan already sketched.