I’ve been building Appointlet since 2012. In that time, I’ve watched hundreds of tools come and go, and I’ve talked to thousands of small business owners about which ones they use, which ones they’ve abandoned, and which ones they’re paying for but haven’t logged into in months.
The pattern I’ve seen is the opposite of what most people expect.
The businesses that operate well, the ones that feel calm, that respond to clients quickly, that have time for new ideas, are almost never the ones with the biggest software stack. They’re usually the ones with the smallest stack that still does the job. Three or four tools, used well, beat fifteen tools, used poorly, every single time.
I’m aware of how strange this sounds coming from someone who runs a software company. We’ve spent the last 12 years building a tool that integrates with dozens of other tools. But my philosophy on having a simple tech stack remains the same.
The pressure to add tools is constant
Every week, there’s a new tool with a launch post, a thread on LinkedIn about how someone’s stack changed their business, or your inbox has a few cold emails from companies you’ve never heard of, telling you their software will save you ten hours.
The implicit message in all of it is that you’re falling behind if you’re not using more.
I think for most appointment-based businesses, the opposite is true. Every additional tool is another login to remember, another monthly subscription, another set of notifications, another place where data lives, another thing that can break, another thing your team has to learn. There’s the cost concern, but there’s also the cognitive overhead of having it in your life at all.
When that cost is small, adding a tool is fine. When the cost adds up across fifteen tools, the math gets bad fast.
What actually happens when your stack grows
A business adds a new tool to solve a real problem, the tool works, then they add another one. That works too. Six months later, they’ve got eight tools, and the original problems are technically solved, but something else has gone wrong.
The team is spending more time managing the tools than the tools were supposed to save them. Information lives in too many places, and people don’t know where to look. New hires take twice as long to onboard because the stack has its own learning curve.
The thing that originally felt like progress quietly turned into its own kind of weight.
I’ve watched a lot of small businesses end up here. The cause is rarely a single bad decision. It’s a hundred small ones, each of which made sense at the time.
The case for a minimum viable stack
If I were starting an appointment-based business tomorrow, here’s what I’d use:
- A scheduling tool.
- A calendar. Google Calendar or Outlook. This should sync with your scheduling tool so you never have to check two places.
- A way to take payment. If your scheduling tool handles this (and many do), you don’t need a standalone invoicing app for simple session-based payments. You might still need one for more complex billing, but most appointment businesses don’t have complex billing.
- A way to communicate with clients. Email, mostly. Maybe a messaging app if your clients prefer texting. The point is to pick one primary channel and actually use it, not to spread conversations across email, Instagram DMs, WhatsApp, and a client portal.
- A way to keep track of who they are. A CRM, or a simple spreadsheet.
- A place to take notes. Google Docs, Notion, or, honestly, a paper notebook. Whatever keeps you from losing important context between appointments.
That’s six things, and depending on the business, some of them can be the same tool. A therapist whose scheduling tool handles intake forms, reminders, and calendar sync is already covering three of these in one place. A consultant who bills per session and collects payment at booking might be covering four.
The extra tools are usually doing one of two things. They’re either solving problems the business doesn’t actually have, or they’re solving real problems in a way that’s heavier than the problem deserves.
Both are worth being honest about.
Why we keep saying no
We’ve been asked to add a lot of features over the years. Some of them we’ve shipped; most we haven’t.
We don’t say no because we think those features are bad. We say no because we know what happens to software when you keep saying yes. You end up with a product that does fifty things poorly instead of ten things well, and the people who came to you because you were simple start leaving because you stopped being simple.
There’s a word for this in the tech world that I’ve started seeing more often. Enshittification. The idea is that software starts good, gets bigger, gets worse, and eventually becomes the thing it was originally trying to replace.
I don’t want that to happen to Appointlet. I’d rather have a smaller tool that stays good than a bigger tool that doesn’t.
Before you add your next tool
Ask yourself these four questions before you commit to anything:
- Does this solve a problem I’m currently solving manually? If you’re not doing the thing manually right now, you probably don’t need a tool for it. A lot of software purchases are aspirational. They solve the problem you think you’ll have in six months, not the one you actually have today.
- Can I get 80% of this from a tool I already pay for? Most software has more depth than the people using it have explored. Before adding a new tool, check whether your existing tool already has them built in.
- Will this create a new place where data lives? Every new data silo is a future headache. If you add a tool and it doesn’t sync with the things you already use, you’re going to spend time manually moving information between them. That time adds up.
- Is this tool light or heavy? Some tools want to be the center of your entire operation, while others do one thing and stay out of your way. For most appointment-based businesses, you want one heavy tool (your scheduling and booking system) and everything else to be light. Heavy tools tend to create more lock-in and complexity than they’re worth, unless they’re genuinely the core of what you do.
If a tool passes all four of those, it’s probably worth adding. If it doesn’t pass at least two, it’s probably going to become one of those subscriptions you’re paying for but haven’t logged into in months.
And when you do add something, give it 30 days of real use before you quit or commit. A lot of tools take a minute to really figure out, so give yourself time to see if it’s going to work.
What I keep coming back to
After 12+ years of building Appointlet and talking to thousands of business owners, the closest thing I’ve got to wisdom on the subject is this: most businesses are paying for more software than they need. The ones that operate well have small stacks they understand deeply, not big stacks they tolerate.
If you’re running an appointment-based business and your stack feels bloated, the fix usually isn’t finding a better tool. It’s using fewer tools, more intentionally.
If you want to talk through what your stack should actually look like for your business, we host office hours every Wednesday at 1:30 PM EST.
