Case Studies

How a Feature Matrix Saved a Kelowna Business From Building the Wrong App

Before writing a line of code, we mapped every feature against effort and value. Half the wish list quietly disappeared and the client saved months.

October 7, 2026
6 min read
By BoostBC
How a Feature Matrix Saved a Kelowna Business From Building the Wrong App

The most expensive sentence in software is "while we are at it, can we also..."

A growing Okanagan business wanted a custom platform to replace a tangle of spreadsheets and group chats. They arrived with a wish list of 31 features. Every one of them felt essential. That is normal. It is also how budgets die.

Platform planning feature matrix document
Project #157: the planning matrix that ranked every requested feature before development started.

The situation

Nobody on their team could agree on what to build first. The owner wanted reporting. The office manager wanted scheduling. The field staff wanted something that worked on a phone with one thumb. All valid. All competing for the same first dollar.

What I built

Before touching code, I built this matrix. Each feature got scored on three things:

  • Business value. Does this make or save money, or does it just feel nice?
  • Effort. Days, not months. Honest estimates.
  • Dependency. Does something else need to exist first?

Then the features were grouped into phases. Phase one is the smallest thing that replaces the spreadsheets. Phase two is what makes it pleasant. Phase three is the stuff that sounded great in the meeting and can wait until the business proves it needs it.

The document itself is a table with colour coding so anyone on the team can read it in a minute. No technical jargon. If the owner cannot explain a row to a new hire, the row gets rewritten.

Why it works

Eleven of the 31 features moved to phase three. Four were cut entirely because, once written down next to their cost, nobody wanted them. Phase one shipped in weeks instead of the quarter it would have taken to build everything.

More importantly, the team stopped arguing. The matrix became the referee. When someone wanted to add something, the question was no longer "is this a good idea" but "where does this go in the table."

The takeaway for your business

If you are considering custom software, an app, or even a big website rebuild, insist on this step. Anyone who starts building before ranking features is spending your money to figure out what you want.

Want something like this for your business?

I plan before I build, and I show you the plan. If you have a software idea and a wish list, let me help you find the version that ships this year.

Book a free 20 minute chat or browse more case studies. No retainers, no account managers, no mystery invoices.

BoostBC branded hoodie in an Okanagan vineyard
BoostBC. Kelowna born, Okanagan proud, working with businesses across BC.
case study
custom software
app development
planning
Kelowna
Share this post:
More Success Stories

See How We've Helped Other BC Businesses

Explore our collection of client success stories, case studies, and real results from businesses just like yours across British Columbia.

Blog Alerts

Get an email when we publish a new post

Blog posts only — this is separate from our monthly newsletter. One short email per new article, unsubscribe anytime.