Narrow tools beat broad suites

Earlier in this series we wrote about software that does one thing — why we build narrow tools, and where a suite is the better answer. That piece was about principle. This one is about practice: what actually happens over two or three years when you choose a set of narrow tools instead of one broad suite.

The title overstates it a little. Suites win sometimes, and we say when below. But in the areas where narrow tools fit, they tend to win in ways that only show up over time.

1. Each part can be replaced on its own

In a suite, every function arrives and leaves together. If the suite's image editor is excellent and its file manager is mediocre, you keep both — replacing the file manager means replacing the image editor too, or running two overlapping products.

With narrow tools, a better renamer replaces your renamer and nothing else changes. Over a few years, that compounds: each slot in your toolkit ends up holding the best option available, rather than the best compromise available when you first chose.

2. Price changes hit one tool, not everything

When a suite changes its pricing — moves to a subscription, raises the price, removes a tier — you face the change for everything at once, with no practical alternative in the short term.

When one narrow tool changes its pricing, you decide about that one tool. If it is no longer worth it, you replace one thing.

3. Your data stays in ordinary places

Suites tend to keep data in their own storage, because integration between their parts depends on it. Contacts in the suite's database, files in the suite's cloud, projects in the suite's format.

Narrow tools are more likely to work on data that already exists in ordinary places — files in folders, the system's own contacts database — because they have no other parts to share a private store with. That is what makes each of them replaceable.

4. Smaller surface, fewer permissions

A suite that manages files, contacts, calendars and messages legitimately needs access to all of them. Any vulnerability, bug or policy change touches all of them.

A narrow tool needs only what its job requires. A renamer does not need the network. A keyboard-sound app does not need to see keystrokes. The permissions list is short and easy to reason about.

5. Updates are smaller and more predictable

Suites ship big releases. Interface overhauls, moved features and new defaults arrive together, and you learn them together.

Narrow tools change less, because there is less to change. The renamer next year works like the renamer this year, with fixes and a feature or two.

When the suite genuinely wins

Being fair about it:

• Deeply shared data. When several jobs work on the same records at the same time — a team's tasks, documents and discussions, or a writing tool with citations and layout — integration is the product.
• Team administration. One place to manage accounts, permissions and billing for many people is worth a lot to an organisation.
• Consistency for beginners. One interface to learn.
• One vendor to trust. For some organisations, fewer vendors is a compliance requirement.

If those describe your situation, a suite may be right, and no amount of elegance in narrow tools changes that.

A checklist before committing to a suite

Questions that expose the hidden costs:

1. Which of its functions will I actually use? List them. If it is two out of twelve, you are paying for ten.
2. Can I use the parts I want with data from outside the suite? Or must everything move in?
3. What does leaving look like? Export everything once, before you depend on it.
4. What happens to my work if I stop paying? Read the pricing page's small print.
5. Which function is weakest, and could I live with it for three years?
6. Who else in my organisation will depend on it? Suites spread, and the switching cost grows with every person.

Making narrow tools work together

The honest weakness of narrow tools is the joins between them. Three things make those joins cheap:

• Ordinary files in ordinary formats, so one tool's output is another's input without conversion.
• The system's own data — Contacts, Photos, the file system — rather than private stores.
• Automation the system provides — Shortcuts, Finder Quick Actions, Services, the command line — so tools can be chained without knowing about each other.

What this means for us

It is why our apps stay small. RenameDeck renames files where they are. Ziploom creates and opens archives. Compact Contacts works on the macOS contacts database rather than keeping its own. Garfi and Miyu Paint export standard video and image formats. ClackSmith plays sounds and asks for no sensitive permissions.

Each can be replaced without disturbing the others — including by something that is not ours. We think that is a feature worth building for.