Three questions to ask before you build anything

The most expensive software is the kind that gets built before anyone asked whether it should exist. Good technical consulting starts before the building — with a few honest questions.

1. What does success actually look like?

Not "a new app." A number. Faster turnaround, fewer errors, more bookings, less time on a task. If you can't name the metric, you can't tell whether the project worked — and you'll keep adding features hoping one of them helps.

2. What's the smallest version that proves it?

Almost everything can be cut from a first version. The goal is to learn whether the idea works with the least time and money spent. Ship the core, watch real people use it, then decide what's next based on evidence instead of guesses.

3. Who owns it after launch?

Software isn't a one-time purchase; it's a small ongoing relationship. Before building, decide who maintains it, where it lives, and how it gets updated. The answer shapes how it should be built.

---

Answer these three and you've already avoided the most common (and costly) mistakes. That's the part I enjoy most — helping a business spend its effort where it counts. If you're weighing a build-or-buy decision, reach out.