What to prepare before you talk to a design and development studio

You do not need a specification, a wireframe or a budget spreadsheet. You need to be able to describe a normal day in the business. A good studio can work out the rest.

What should I bring to the first call?

• One normal day, start to finish. Who does what, in what order, using which tools.
• The thing that went wrong last week. A missed order, a double booking, a late payment. Real examples beat general complaints.
• Who would use the product. Staff, customers, drivers, managers. Roughly how many of each.
• What you already pay for. Any software, even if you dislike it.
• What "worth it" would mean. Hours saved, fewer mistakes, faster payment.

What should I ask the studio?

• Who will actually design and build this, and will I talk to them?
• Can I see a clickable version before you write code?
• Is the price fixed, and what exactly is in scope?
• Who owns the code, the designs and the accounts?
• What happens after launch?

What should make me cautious?

A quote without questions. A studio that prices your project before understanding how the business works is pricing a guess. So is one that will not put the scope in writing.

If you would like to try this with us, send a few lines or ask Nur on any page. The first call is fifteen minutes and free.