The Budget Line Is the First Thing an Inquiry Email Leaves Blank

An inquiry email usually runs to a line or two: “We want to build something like this.” A shop takes that sentence and fills in everything else on its own, one studio drawing something small and the next drawing something large. Reading a set of quotes side by side once they arrive is covered elsewhere. This is the step before that: what your side can fill in first, before a vendor has to guess.

What Happens When the Budget Line Stays Blank

Owners often leave the budget out on purpose, worried that naming a figure just invites a vendor to spend all of it. The opposite tends to happen. Without a number, a shop defaults to whatever scale of project it handles most often: one studio prices for a small storefront, another prices for a weekend side project, and the same sentence produces two very different pictures. Numbers that come back from different starting pictures cannot be lined up against each other.

You do not need to commit to an exact figure. A range is enough. One line, something like “we can go up to this point, and anything past it needs another conversation,” lets a shop choose what to include and what to leave out inside that range. Naming a range is not an invitation to bill up to it as a matter of course; a vendor who treats it that way is telling you something about themselves, not the other way around.

Decide Who Signs Off Before the Email Goes Out

When the decision-maker is still unsettled at the inquiry stage, progress stalls again once the quote lands. A staff member forwards a quote to the owner, the owner wants something different, and the vendor has to rebuild the estimate from the ground up. A revised quote is not a small edit; it takes about as long as the first one did.

Before the email goes out, settle inside your own team who actually signs off on this project and how many people need to agree. One person with final say is the fastest path. If several people have to agree, get them aligned on priorities before the quote lands rather than after. Narrow the vendor-facing contact to one person too: the same question landing with two different people on your side tends to come back with two different answers.

Send What to Copy, and What Not To

A common inquiry drops a single site or app link with “something like this” attached. If it is unclear whether that link points to a visual style, a screen layout, or the entire feature set, a vendor has to guess which one, and a guess in the wrong direction inflates the number that comes back. A link sent to convey tone alone, read as a request to build every feature on that reference, produces a quote larger than it needs to be.

Naming what you do not want helps just as much. A feature the reference site has that you plan to skip, an approach a previous vendor tried that did not work out: a short exclusion list narrows scope faster than a wish list does. What you are not asking for often does more work than what you are.

List What You Already Have First

If this is a fix or a migration rather than a fresh build, an inventory of what already exists fills in half the quote by itself. Send the names and plans of the tools currently in use, login details, any code or design files a past vendor left behind, and an old quote if one exists. Without that material a vendor prices the job as a build from zero, when reusing what is already there is often the far simpler path.

Pulling that material together sometimes turns up a login nobody remembers or a contact who has already left. In that state, recovering the accounts comes before requesting a quote at all; the order for that is laid out separately in The First Week After a Developer Goes Quiet.

Not Every Blank Needs Filling Before You Call

None of the four above have to be settled before you can reach out. Weple’s development consultation is built to help fill in these blanks in the first place. Send over whatever is in your head right now, how to phrase a budget range, which reference matters most, and we work through it with you. What a session covers and what it costs sits on the pricing page. The write-up that comes out of it works just as well if you end up sending it to a different vendor entirely.