Melbourne, Australia.

[email protected]
SignalMoney18 November 2026

What to have ready before you call a developer

You need less than most owners expect: the one job you want off your plate, a rough count of what it costs today, and the name of the person who can say yes. A good developer works out the rest with you, and asks for anything else once, in one list.

Plenty of owners put off the call until they have written a full brief. That brief usually describes a solution they have pictured, and leaves out the part a developer needs most: how the work runs now.

What do you need before the first call?

Three things. None takes more than an hour.

  • The job. One sentence, in your own words, on what you want handled. "Every enquiry gets a proper reply the same day" is enough. You do not need to know how.
  • What it costs now. How often it happens, and roughly how long each one takes. A guess will do for the first call. A count over one working week is better.
  • Who decides. The person who can say yes to the work and to the money. If that is two partners, both should be on the second call.

What helps, if you have it?

  • A list of the tools you pay for. The name, what it is for, and who uses it. List what you pay for before you add a tool shows a one-page way to do it.
  • Three real examples. Recent enquiries, quotes or bookings that show the job on a normal day. Show them on screen during the call rather than emailing them, so customers' details stay with you.
  • The person who does the job. A developer will want to talk to them, or watch them do it once. They know where the exceptions are.
  • One number you want to move. Replies sent within the hour, quotes followed up, evenings back.
  • How fast you want it, and a rough budget. Neither is a promise. Both help size the first piece to fit.

What can wait?

  • A written specification. Setting down how the software should work is the developer's job, after they have seen how the work runs.
  • Screens and designs. They come after the job is understood, never before.
  • Which tools to keep. Most should stay. That is worth working out together.
  • Technical knowledge. You need to know your business. That is the hard part, and you already have it.

Which logins should you check?

Your own. Before the call, make sure you hold the admin login for each tool the job touches, or know who does. A tool still tied to the email address of someone who has left the business turns into a wait the day the work starts.

Check, too, that each account is in the business's name. If one is in a former supplier's name, find out now how to move it.

What should you ask the developer?

Four questions sort them quickly.

  1. What do you need from us, and by when? A clear list is a good sign. "We will let you know" is a timeline with holes in it.
  2. What will we count before and after? One number, measured before anything is built and again after it is running.
  3. What happens to our records if we part ways? You want them returned in a file another tool can open, and the answer in writing.
  4. Who looks after it once it is live? A name, and how they will know if it stops working.

What do we ask of an owner?

As little as we can. Our rule since October 2026: nothing we send after a first meeting asks the owner to go and do something for us. What we need goes in one list. We ask once, and each message ends in a decision or a date.

We also pick the first piece of work ourselves, from what the owner has told us, and say what the choice rests on. Owners hire someone to make that call. Handing them back a menu of options is handing them homework.

So the honest answer to "what should I prepare?" is the job, the number and the person who decides. The rest is our work.

Where does it go wrong?

  • Bringing the solution instead of the job. "We need an app" starts a conversation about apps. "Parents wait two days for a reply" starts one about the parents.
  • Leaving out the person who does the work. The owner describes the job as it should run. The person doing it knows where it goes off course.
  • Waiting for the perfect brief. A month spent writing a document is a month the job keeps costing what it costs.
  • Choosing on the first number. A quick quote with no questions behind it has priced a guess.

In short

  • Bring one sentence on the job, a rough count of what it costs now, and who decides.
  • A list of your tools, three real examples and the person who does the job all help.
  • A specification, designs and technical knowledge can wait.
  • Check you hold the admin logins for every tool the job touches.
  • Ask what the developer needs from you, once, and by when.

One step for this week

Write the one sentence. Then count the job for five working days: how many times it happens and how long each one takes. Last, open the admin settings of each tool it touches and check whose name is on the account.

Those three things are a complete start. If the job you wrote down needs custom software, that sentence is all our first call needs.

OBSERVE.

ORCHESTRATE.

OUTPERFORM.

Every system we build starts with one call.