Hide the Complexity, Don't Remove It: Our Design Philosophy

Simple software and basic software aren't the same thing, and most tools built for small businesses confuse the two. Basic software leaves out the features a growing business actually needs. Simple software includes them, but doesn't make you look at them until you do.

Where does this idea come from?

It's the same principle behind why a phone can do a thousand things and still feel obvious to use on day one: the complexity is there — encrypted messaging, a full camera system, dozens of settings — but none of it is in front of you when you just want to make a call. Most business software does the opposite. It puts every setting, every field, every permission on the screen at once, because that's the easiest thing for the software team to build, not the easiest thing for the person using it.

What this looks like in practice

A 4-person shop and a 40-person shop both need the same underlying features eventually — role permissions, quote versioning, flexible invoicing. But the 4-person shop shouldn't have to see a permissions matrix just to send their first quote. Complexity should surface when a business grows into needing it, not before. That's a harder thing to design than exposing every option up front, and it's the standard we hold ourselves to.

Why it matters more for trade businesses specifically

Nobody running a fabrication shop, HVAC company, or service business has time to sit through onboarding training. If the core of the product isn't usable in the first five minutes, on a phone, standing on a job site, it doesn't matter how powerful the rest of it is underneath.