Most business owners have heard a software horror story: the project that took twice as long, cost three times the quote and still didn’t do what was needed. It’s rarely because the developers couldn’t code. It’s because nobody agreed, in enough detail, what was being built.
Here’s how to plan an app project so that doesn’t happen to you.
Why software projects go wrong
- The brief is one paragraph, so everyone imagines a different app.
- The price is given before anyone has mapped the process.
- The business only sees the app at the end, when changes are most expensive.
- New ideas keep getting added halfway through, with no change to time or budget.
- Nobody planned for training, moving the old data or support after launch.
Seven steps to a project that delivers
1. Start with the problem, not the features
Write down the process you want to fix and what it costs you today: hours of capturing, errors, missed orders, slow reports. “Our branches email stock sheets every Friday and it takes a day to combine them” is a far better starting point than “we need an inventory app with dashboards”.
2. Map how the work flows today
Who does what, in what order, with which information? Sit with the people who do the work. They know the exceptions and workarounds that never make it into a brief, and those are what make or break an app.
3. Agree the scope and the screens before anyone builds
Sketch every screen: what it shows, what you can do on it, who can see it. Simple wireframes are enough. Everyone can point at a screen and say “yes, that” or “no, we also need this”. It is the cheapest moment to change your mind.
4. Fix the price for a defined scope
With the screens agreed, a developer can give a fixed price and timeline instead of an open-ended estimate. That is why we start every project with a short, paid App Plan: it produces the screens, scope, price and timeline, and it’s yours to keep whoever builds the app.
5. Build in stages and look at working screens often
Break the build into stages of a few weeks each, ending with something you can click through. Problems show up early, while they’re small, and you can steer as you go.
6. Handle changes deliberately
New ideas will come up; that’s healthy. Write each one down, agree whether it goes in now (with its cost and time) or into a later phase. A “phase 2” list protects the launch date.
7. Plan the launch and what comes after
Budget time for moving data from the old spreadsheets, training staff, a short period of running old and new side by side, and a support plan for fixes and improvements. An app is never finished; the good ones keep getting better.
Questions to ask any developer
- Will we see and agree the screens before the build starts?
- Is the price fixed for that scope, and how are changes priced?
- How often will we see working software?
- Who owns the code and the data, in writing?
- Who supports the app after launch, and how quickly do they respond?
Start with a free scoping call
Tell us about the process you want to fix. In 30 minutes we’ll tell you honestly whether an app is the right answer and what the App Plan would cover. See how our App Plan works or scope your app. Still deciding whether to build at all? Read custom app or off-the-shelf software.
Related services: Software Development
