Insight · What should I send a development company in my first message?

What to send a development company to get a useful quote

A short checklist for your first message, so the reply is a real estimate with real questions rather than a generic price.

Most first messages say “I want an app like X, how much?” The honest answer is a range so wide it does not help. A few more sentences get you a much better reply, and you do not need any technical knowledge to write them.

The checklist

The product

  • Who will use it? Be specific: “drivers at our depot” tells us more than “users”.
  • What are the three to five things they must be able to do in the first version?
  • Which of those would make the product pointless if it were missing?

What exists today

  • Any code, designs, a website, or a prototype, including one made with an AI builder.
  • Whether you still hold the source code and accounts.
  • Any existing system it must connect to, such as a CRM, ERP, payment provider or your own database.
  • Any hardware. If there is a device, say what connection it uses and who owns the firmware.

The limits

  • iPhone, Android, web, or a mix? “Not sure” is a fine answer.
  • Your budget range. If you would rather not say, at least say whether you are thinking in thousands or tens of thousands of dollars or pounds.
  • Any real deadline, and what happens if it is missed.
  • Any rules that apply, such as health, payment or children’s data.

After launch

  • Who will look after it? Do you need a team to stay on, or do you plan to bring it in-house later?

A made-up example

We run three clinics in the UK. Patients phone to book, and our reception team spends hours on it. We want patients to book and reschedule on their phones and get reminders. Staff need a screen to see the day. We have an existing patient database with an API, and no app or designs. We handle patient data, so UK GDPR applies. Our budget is in the tens of thousands of pounds. We would like to launch by next summer, but the date is flexible.

A message like that takes a few minutes. It lets a company give you a first view of scope, ask the right questions, and tell you if it is the wrong fit.

What you should get back

A useful reply includes questions about your project, a view on what to leave out of version one, and a clear next step. Be wary of an exact price with no questions at all. It usually means the scope was guessed, and that the cost will come back later as change requests.

Comparing several quotes

Quotes can differ several times over because they describe different things. Before you compare prices, check each one for:

  • Design: is it included, and how much?
  • The back end and admin panel, not only the app.
  • Testing, including on real devices.
  • Store submission and hosting setup.
  • What happens after launch, and what that costs.
  • Who owns the code and accounts.
  • Who works on it, and how many of them are senior.

If one quote is far lower, ask what it leaves out. If it leaves out nothing, ask how.

Send it to us, if you like

Our project form has one box for this. Paste your few sentences in, and add your budget range if you are happy to share it. We reply with questions about your scope.

Want a recommendation for your product?

Tell us what it does and what exists today. We reply with the questions that matter and what we would do.