Before I write a line of code, I want to know two things: what the business is trying to achieve, and what its customers can't do without. Everything else can wait for evidence.

That's the same question I asked in How to Scope an MVP: does it need brakes or a stereo? When the software already runs the business, there's a second rule. Protect what works every day while you fix what doesn't.

The scenarios below are hypothetical examples illustrating our approach. They do not describe client engagements or measured results.

We don't start by writing code

Apps, websites, customer systems or software that ties tools together: the first conversation is never about features. It's about these questions.

  • What does success look like? What the business needs, and how we'll know we got there.
  • Who will use it? The real customers, the real problem, and what they do about it today.
  • What can't it live without? The must-haves. Without them, nobody would bother using it.
  • What would make it better? The important improvements that make it easier or faster.
  • What can wait? The nice-to-haves, saved until customers actually ask for them.
  • What's the smallest useful version? Build that first, try it with real people, then decide what's next.

Two examples

Launching a new app

The short version: Find out what customers actually need before paying to build everything they might want.

Picture a company that inspects rental properties and wants to turn its know-how into an app. The founders arrive with a wish list of over forty features. Building all of it would take most of the budget and many months, before a single customer pays. And nobody knows yet which features people will use.

What we'd do

  1. Listen first. We talk to property managers and inspectors. The real headache: reports take days to reach owners, and photos go missing.
  2. Turn wishes into clear goals. For example: an inspector can finish a report on a phone with no training, and the owner gets it the same day.
  3. Build only the essentials. A simple checklist, photos attached to each item, a version that works with no signal, and a report that's easy to share.
  4. Put it in real hands. A few friendly property managers use it on real inspections. We watch, see where people get stuck, and ask what they think every week.
  5. Test choices once there's enough traffic. With more users, we can show two versions of a screen and keep the better one. Early on, a conversation teaches more.
  6. Polish, then launch. Fix what we learned, confirm people would pay, then fund the launch.

What goes in first

  • Must have: Checklist on the phone, even offline, photos for each item, a report the owner can open
  • Important: Reusable inspection templates, scheduling and reminders
  • Nice to have, later: Custom branding for every client, fancy dashboards, links to every property system

The catch: Some early customers will ask for missing things. Good: requests from paying users beat guesses from a meeting.

What the business gets: Money goes into what customers have shown they want, and the app reaches real people sooner.

Improving the systems a business already runs on

Four business systems joined by clean connections, with a taped-together spreadsheet bridge being replaced.
Improve what matters without disrupting what already works.

The short version: Improve what matters without disrupting what already works.

Now picture a home services company running on a customer database, a booking website, a quoting tool and links to accounting and texting. Staff patch the gaps with spreadsheets, and someone suggests starting over. The business depends on these systems every day. Starting over would risk bookings, customer history and invoices, when the real complaints are about a few gaps.

What we'd do

  1. Learn how everything connects. Which system talks to which, and what would break if one stopped.
  2. Know what must never stop. Booking, quoting, sending technicians and invoicing keep working throughout.
  3. Protect it before touching it. Fresh backups, an access check and automatic tests on the key steps, so data stays safe and correct.
  4. Find the real gaps. Staff and customers point to three: quotes typed in twice, no way to reschedule online, and forgotten follow-ups.
  5. Fix what matters most first. Each gap is ranked by time saved, mistakes avoided or bookings kept. A new website look can wait.
  6. Change one thing at a time. Each improvement is tried on a copy first, watched closely after release, and can be undone if needed.
  7. Write it all down. How it's built, how the pieces connect and how to run it, so nothing depends on one person's memory.

What goes in first

  • Must have: Quotes flow into the customer database on their own, bookings and invoices never stop
  • Important: Customers can reschedule online, automatic follow-up reminders
  • Nice to have, later: A website redesign, new reports

The catch: Going step by step keeps some older parts a little longer. In return, the business never bets its daily operations on one big switch-over.

What the business gets: Less double typing, happier customers and a business that keeps running the whole time.

The short of it

Same habit both times: understand first, build the smallest thing that proves its worth, and spend more only when the evidence says so.

However the work starts, we prefer a clearly scoped project: defined deliverables, a practical budget, documentation and a proper handover, so your team can run what we build without needing us.

This is the thinking behind PreciseMP's Software & Application Development service.

Related reading: Build or Buy? When Custom Software Makes Sense.