Every engagement we take on starts with the same thing: a real conversation. Not a sales call, not a discovery deck, not a questionnaire. Thirty minutes (or sometimes longer) of you walking us through your business — and us shutting up and listening.
That part isn't a loss leader. It's the work.
Why so much software is built for the wrong problem
Walk into most small businesses being sold a new tool, and you'll see the same pattern:
- A vendor showed up with a polished presentation.
- They asked about features — what does the tool need to do?
- They never asked about day-to-day — what does running this business actually feel like, hour by hour?
- The owner bought something based on features. Six months later, it's half-used, the data is a mess, and the original bottleneck is still there.
The tool wasn't bad. The conversation before it was.
What listening actually looks like
When we sit down with a small business for the first time, the questions we care about aren't about software. They're about the business:
- Walk us through a typical Monday morning.
- What's the part of running this that you like least?
- Who else on your team spends hours on things you wish they didn't?
- What was the last surprise that cost you real money? How would you have seen it sooner?
- If a new hire started tomorrow, what would take them the longest to figure out?
- What's one thing you'd change about the business if you could snap your fingers?
None of these questions are about tools. They're about what's actually happening. Almost every time, the real problem is different from the one the owner thinks they're hiring us to solve.
The pattern we keep seeing
After doing this enough times, we've noticed: small businesses usually arrive asking for a thing and leaving with a different thing. And that's fine. It's the point.
- An owner asks for a new website. After listening, we realize the site is fine — the problem is that leads drop into a shared inbox that nobody owns. A $500 inbox workflow fix earns them more than a $15K rebuild would have.
- An owner asks for a custom app. After listening, we realize their existing software would do 90% of what they want if it were configured differently. A half-day of configuration saves a $40K build.
- An owner asks for an automation. After listening, we realize the underlying process is broken in ways an automation would just lock in. We help them redesign the process first, then build the automation on top.
In each case, leading with the tool would have been a mistake. Leading with the listening got us to the actual answer.
The consequence
Listening first changes what you end up building — and sometimes whether you end up building anything at all. That's an uncomfortable business model on its face, because we make more money when we build more stuff. Saying "you don't need us right now" isn't a great short-term move.
But the long-term math works. Clients who get told "you don't need this" come back later, when they do need something — and they send friends who trust them. Clients who get sold the wrong thing don't.
The principle
If you're weighing whether to hire us (or anyone), the single most important thing to ask them is: how much time do you plan to spend understanding my business before recommending anything?
If the answer is "we already have a solution" — walk away. If the answer is "as much as it takes" — keep talking. The quality of the recommendation is directly proportional to the time spent before making it.
That's it. That's the whole pitch.