How to start a software project: a practical guide for business owners

Custom software can save hours of work every week. It can also cost a lot and disappoint if the project starts on the wrong foot. Many problems come from unclear goals rather than from technology. Here are six steps that help, whoever you work with.

1. Describe the problem, not the solution

“We need an app” is a solution. “Our sales team loses an hour a day copying orders from email into a spreadsheet” is a problem. Start with the problem: who has it, how often, and what it costs you today. A good developer will often suggest a simpler solution than the one you first had in mind.

2. Define a small first version

List everything you would like the software to do, then sort the list into three groups:

• Must have: without it, the software is useless.
• Should have: important, but it can wait a few weeks.
• Nice to have: ideas for later.

Build the first version with the “must have” list only. You will use it sooner, learn from real use, and spend the rest of the budget on what actually matters.

3. Know your users and your data

Write down who will use the software (staff, customers, partners), on which devices and in which languages. List the data it needs: where it is today (spreadsheets, an old system, paper), who owns it, and whether it includes personal data that falls under the GDPR.

4. Be open about budget and deadlines

Sharing a budget range is not a risk. It lets your partner propose a solution that fits, instead of an ideal one you cannot afford. The same goes for deadlines: say which dates are fixed (a trade fair, a new law) and which are only wishes.

5. Choose your partner with the right questions

Price matters, but these questions tell you more:

• How will we work together, and how often will I see progress?
• Who owns the code, and will I receive all the access and documentation?
• How do you handle security and personal data?
• What happens after launch: updates, bugs, hosting?

6. Plan for after launch

Software is never finished. Operating systems, browsers and libraries change, and security updates are needed. Plan a small budget for maintenance from the start, and decide who will host the software and who to call if something breaks.

In short

1. Describe the problem, not the solution.
2. Start with a small first version.
3. Know your users and your data.
4. Share your budget range and your real deadlines.
5. Ask about process, code ownership, security and support.
6. Plan for maintenance after launch.

Have a project in mind? This is exactly how we start: a conversation about the problem, then a written proposal. See our software engineering service.