Planning
What to prepare before your first call with a software team
You don't need a technical brief to start a software project. A few notes about your goals, your users and your current tools are enough to get real value from a first call.
Atrosot4 min read
Many business owners put off talking to a software team because they think they need a detailed specification first. You don't. A first call is where the specification starts, not where it has to be finished.
That said, a little preparation makes a first call far more useful. Here's what helps, in plain terms.
1. What you want to achieve
The most useful thing you can bring is a clear goal, in business terms. For example:
- "We want customers to book and pay online instead of calling us."
- "We want one place to see every order, from enquiry to delivery."
- "We want to sell our process to other companies as a subscription product."
A goal like this lets the team suggest the simplest way to get there. Sometimes that's a full system, sometimes a small tool, and sometimes a change to what you already use.
2. Who will use it
Think about the people on the other side of the screen:
- Your customers, your staff, or both?
- How comfortable are they with technology?
- Will they use it on a phone, a computer, or both?
- Roughly how many people will use it at first, and in a year?
You don't need exact numbers. "About ten staff now, maybe fifty later" is plenty.
3. How you work today
Describe your current process, even if it's messy. Spreadsheets, paper forms, WhatsApp groups and email chains are all useful clues. If you can, note:
- Which tools you already use, and which ones you'd like to keep.
- Where things go wrong or take too long.
- Any steps that must happen in a certain order, or need someone's approval.
Screenshots or photos of the spreadsheets and forms you use today are often more helpful than a long description.
4. Examples you like (and don't like)
Links to apps or websites you like help a lot, even if they're from a different industry. Say what you like about them: how simple they are, how they look, a feature you'd love. Examples you dislike are just as useful.
5. Budget and timing
It's normal to feel unsure about budget. Still, a rough range helps the team suggest an approach that fits, instead of designing something you can't afford. If you have a deadline, such as a launch, an event or a busy season, mention it early.
If you really don't know, say so. A good team will explain what drives the cost and offer options at different sizes, such as a smaller first version that you can grow later.
6. Questions to ask the team
A first call is also your chance to judge the team. Useful questions include:
- Who will actually build the software, and will I talk to them directly?
- How will I see progress while it's being built?
- Who owns the code when the project is finished?
- What happens after launch if something breaks?
- Can you sign an NDA before I share details?
Clear, direct answers are a good sign.
What you can leave out
You don't need to choose a programming language, design a database or write technical documents. That's the software team's job. You also don't need to have every feature decided: good projects are planned in stages, so you can learn from real use before building the next part.
What happens after the call
After a good first call you should know whether the idea makes sense, roughly what it involves and what the next step is. On our free 30-minute call, we listen, ask questions and suggest the simplest way forward. If you'd like to go ahead, we follow up with a written scope, timeline and price, so you can decide with everything in front of you.
If you have an idea or a problem in mind, those few notes are all you need to book a call.
Have a question about your own project?Ask us on a free 30-minute call. We'll give you an honest answer, at no charge.
Get free advice