← Guides

What to prepare before you ask for a software quote

You do not need a technical document to ask for a quote. A few clear answers help any software house give you a more accurate scope, timeline and price.

Last updated: · 1 min read · Draft guide: to be reviewed and rewritten by the team.

What do you want to build, in one or two sentences?

Say what it is and what it should do. "A booking website for my clinic" is a good start.

Who will use it?

Customers, your team or both? Roughly how many, and on what devices? If most will use a phone, say so.

How is it done today?

Describe the current process: spreadsheets, paper, messages. It tells us what to replace and what to keep.

What would a good result look like?

Fewer phone calls, faster reports, more enquiries. One clear result is easier to design for than a long list of features.

Do you have examples?

Links to sites or apps you like, a logo, existing documents. Examples save many rounds of explaining.

When do you need it, and what is your budget range?

A deadline and a rough range let a team suggest a realistic first version. If you are not sure, say so.

Who decides?

Name the person who approves the work. Projects move faster when there is one clear decision-maker.

Ready to start?

Our short conversation asks exactly these questions and turns your answers into a brief we can start from.

Want help answering these for your project?

Tell us what you have in mind. We will tell you honestly how we would approach it.