Skip to content
SimpleSmith

You already have
a system. It’s you.

Every missed handoff, every forgotten change.
It keeps coming back to you.

SimpleSmith helps move little pieces of it out of your head and into something your business can actually use.

One problem. One simple fix.

Why I’m building this
A note from Bruce

Why I’m building SimpleSmith

I run Walden Homes, a residential construction company in Toronto. For years, I was the system. If something changed on site, I had to make sure the office heard about it. If something needed ordering, I was often the one checking that it happened.

We tried the big industry systems. They did a lot, but they made us work their way. They were complicated, everyone on the team had a lot to learn, and it got hard.

So we built our own systems and processes. They fit us better, but over time they became expensive to run and added overhead of their own.

Then I tried something different: fix one small problem at a time, and make the fix simple enough for the team to accept and work with. It saved our guys time, made their work easier, and saved us money. Because it was simple, it started spreading through the rest of what we do.

That’s what led to SimpleSmith. You don’t need to know what software you need. You don’t even need to know exactly what’s wrong. We can find a place to start together.

I’m testing SimpleSmith with a handful of business owners. Construction is where I started; the approach is for anyone whose business depends on too much living in their head.

— Bruce

The approach

Start small.
Make something useful.

A simple tool should fit the way you and your team already work. We start with one problem, agree on the smallest useful fix, and build from there.

  1. Bruce invites you

    We start with a conversation. If it’s a fit, I’ll invite you into SimpleSmith. We’re working with a small group of businesses while we develop the approach.

  2. You outline one problem

    Intake is where we work through what happens today, where it gets stuck, and what would make it easier. SimpleSmith checks whether a focused first version fits. I step in when the request needs more scoping.

  3. We agree on what to build

    You review the final brief and can request changes. Your approval confirms the scope; a separate build decision starts the work. Once the tool is ready, you try it in practice and we improve it together.

Curious about SimpleSmith?

Let’s jump on a call.

We can talk about your business and see whether SimpleSmith could help. No need to prepare in advance.

Arrange a call

Already invited? Sign in to your workspace.