Before You Pick a Tool, Ask Yourself These Questions
Every week someone asks me some version of the same question. “Should I use Dubsado or HoneyBook?” “ClickUp or Monday?” “Do I even need a CRM?”
And every single time, my answer is: I don’t know yet — and honestly, neither do you.
Because it’s not the first question to ask. The first question is about your process. And most people skip it entirely.
I’ve sat across from (or on Zoom with) a lot of business owners who came to me frustrated, overwhelmed, and convinced that the right tool would fix everything.
A podcast production company already paying for a CRM that wasn’t solving any of their actual problems. A social media agency managing a whole team on Monday.com but still holding critical client context entirely in their head.
A bookkeeper who had watched previous system setups disintegrate the moment the consultant left, because no one had actually built the process — they’d just installed software on top of the chaos.
The tool wasn’t the problem in any of those cases. The process was. And you can’t choose the right tool until you understand the process it’s supposed to support.
First, Let’s Get Clear on What We’re Actually Talking About
Before we talk about tools, we need to talk about four words that get used interchangeably but mean very different things. Getting clear on them will change how you make decisions about your business software.
System
A system is the whole — the interconnected parts of your business that work together to produce a result. Your client experience is a system. Your content creation is a system.
Systems don’t live in any one tool; they span across multiple tools, people, and processes. When someone says “I need a better system,” they usually mean something much smaller and more specific. Which is great! But it’s worth knowing the difference.
Process
A process is the series of steps within a system. It’s the what — what needs to happen, in what order, to move something from start to finish. Your client onboarding process. Your invoicing process. These are sequences of decisions and actions. A process exists whether or not you’ve documented it. Right now, it might just live in your head.
Workflow
A workflow is how the process gets executed. It’s the process in motion — who does what, when, and how it flows from one step to the next. If the process is your recipe, the workflow is what actually happens in the kitchen. This is where delegation lives. A workflow can be manual, partially automated, or fully automated.
Tool
And finally — the tool. The tool is just the software. It’s the platform that supports your workflow. The tool doesn’t create your process. It carries it. This is the last thing you should choose, not the first.
The order matters: System → Process → Workflow → Tool.
When you reverse that order — when you buy the software first and figure out the rest later — that’s how you end up paying for tools you barely use and wondering why nothing feels streamlined.
Start with Curiosity (Not a Google Search)
The work I do with clients is question-led. Not because I don’t have opinions about tools (I do), but because a tool recommendation is only useful when we’re starting from the same conditions. And we’re almost never starting from the same conditions.
I tell clients at the start of almost every exploration conversation: “I’m going to ask a lot of questions. We’re not looking for tech solutions yet — we need to figure out exactly what needs to happen at every stage, and then we’ll figure out the right tools.”
That reframe matters. Because most people arrive wanting to talk about software, and what they actually need to talk about first is their process. And the fastest way to get there is curiosity — genuine, unhurried curiosity about what’s actually happening.
What This Actually Looks Like in a Real Conversation
Here’s a real example (details anonymized). A social media agency owner came to me with a full Monday.com setup already in place. Her team was using it. Clients were being managed in it. From the outside, it looked like they had the tool thing sorted.
But when I asked her to walk me through how her team actually used it, the cracks appeared immediately. She had boards organized by task type on one side and by client on the other, and she couldn’t figure out how to get them to talk to each other. Client-specific details — things like one client hating exclamation points, another always wanting pink heart emojis — were scattered across documents, spreadsheets, and, still, a lot of her own memory. Her team was constantly asking her for information because they didn’t know where to find it.
When I asked her why she’d moved from ClickUp to Monday, she said: “Visually Monday is just easier for me to look at. I know they do the same thing, but I can just see better in Monday.”
That’s a completely valid reason to choose a tool. But notice — it’s not a process reason. It’s a you reason. And both matter. Her Monday setup wasn’t broken because she’d chosen the wrong platform. It was incomplete because the process — how client information flows from intake to the team doing the work — had never been fully designed. The tool was fine. The workflow underneath it needed work.
“Walk me through what happens when a client says yes.”
This is usually my first question. And it is genuinely remarkable how often it surfaces things people didn’t know they needed to say out loud.
One client, a 15-year veteran of her industry, walked me through her onboarding sequence and I heard: “I send them an invoice... unless I forget. And then I realize I haven’t sent the contract yet, so I do that next. Then I ask for their info, but not all at once, so they usually email me back with some details but forget others.”
I asked: “So right now, onboarding is entirely manual. How often do you find yourself following up for missing information?”
“All. The. Time.”
That conversation didn’t start with tools. It ended with a mapped workflow and a plan for which of her existing tools could handle it — without signing up for anything new.
“What’s frustrating about your current setup?”
I asked this question to a podcast production team that had already invested in a CRM. They’d paid for it. They were trying to use it. And then the answers started tumbling out.
One team member: “I hate that I have to dig through forms to find what clients wrote when they first booked.” Another: “It doesn’t block out my Google Calendar automatically.” The founder: “We’ve literally never added anyone from it to our email list because it doesn’t integrate well.”
None of those are personality complaints. They’re process complaints dressed up as tool complaints. The tool wasn’t doing what they needed it to do — but more importantly, they hadn’t yet clearly defined what they needed it to do.
Once we mapped the process (one intake point, structured follow-up sequences, lead routing based on budget and readiness), it became obvious that the tool they had wasn’t the right fit. We found one that was.
The Questions I Ask Before I Ever Mention a Tool
If you want to run yourself through this process, here’s roughly how I approach it with clients. These aren’t a checklist to sprint through. Sit with them.
Walk me through what happens when [the triggering event] occurs. What’s the very first thing you do?
What steps do you absolutely cannot afford to forget?
Where do things slow down or fall through the cracks right now?
What do you have to personally remember vs. what lives somewhere you can find it?
What does “done” look like at the end of this process?
If someone else were doing this, what would they need to know to do it without asking you?
What’s the most frustrating part of how this works right now?
By the time you’ve answered those questions honestly, you have something more valuable than a software recommendation.
You have a process map. And once you can see the process, you can see the gaps — and you can see what a tool actually needs to do to support it.
Then, and Only Then: Pick What Fits You
Once the process is clear, there’s still one more layer before you pick a tool: does it fit you? Your brain, your budget, your team, and your actual capacity to learn something new right now.
The Monday vs. ClickUp conversation I mentioned earlier is a good example. Both platforms can do almost everything the other can do. The deciding factor for that client wasn’t features — it was how the visual layout mapped to how her brain worked.
Another client I’ve spoken to made the same switch specifically because Monday’s task completion animation gave her ADHD brain more of a dopamine hit. That’s not a trivial reason. That’s sustainability.
Tools also have to fit your team. One client was holding client-specific context — preferences, brand voice notes, quirks — across scattered documents and her own memory.
The fix wasn’t a new platform. It was linking SOPs directly inside the relevant task templates in the tool they already had, so her team could find what they needed without asking her. The tool was already there. The workflow design was missing.
Before you commit to something, ask yourself:
How much time do I realistically have to learn this right now?
Does the way this tool organizes information match how I actually think?
What’s my full budget — not just the subscription, but the setup time and learning curve?
Does my team need to use this too, and will it make sense to them?
What tools am I already paying for that I’m not fully using?
That last one. It comes up constantly. The answer is almost never “you need something new.” It’s usually “you have what you need — let’s figure out how to actually use it.”
So, Should You Use X or Y?
Maybe. I genuinely don’t know yet — and neither do you, until you’ve done the process work first.
The answer depends on your process, your team, your brain, and what you’re actually trying to accomplish.
There’s no universal best CRM for boutique agencies. There’s no single best project management tool for creative service providers.
There’s only the right tool for your specific process, in your specific business, used by you and your specific team.
So the next time you catch yourself heading to Google to compare platforms, pause. Open a notebook first. Ask yourself: what is the process I’m trying to support? What actually needs to happen? Where is the friction coming from?
Get curious. Map the process. Then — and only then — pick the tool.
If you want to go deeper, I’ve written about what to do when you’ve already bought the wrong tool, and why system strategy always comes before tool selection.
Both are good next reads if this one landed.
Like this post? Subscribe to my email list for more:
https://www.jackihayes.co/subscribe
Ready for support? Learn how I can help:
