In more than twenty years in the software world, I have seen the same thing in dozens of organizations: it is not tools that are missing, it is clarity about how to use them together.
Here are the five principles that guide every engagement I take on.
1. Simplify before automating
The temptation is usually to automate an existing process. But if that process is badly designed, you are automating a problem — faster, and more often.
Before anything else, I start by understanding how you actually work: which tools, which files, which back-and-forth between people. Then we strip things down. What is useless disappears. What remains becomes clear.
In practice:
- Audit of your current tools and processes
- Identification of redundancies, blind spots and friction points
- Logical reorganization of your data and your flows
- Prioritized action plan, based on impact and urgency
2. Automate what does not need a human
Once the foundations are clear, some tasks no longer need to be done by hand: follow-ups, repetitive data entry, synchronization between tools, report generation. These tasks eat up time and generate errors.
I set up reliable automations with no-code or low-code tools — Make, Power Automate, Zapier, n8n depending on the case. Solutions your teams can understand and maintain without depending on a developer.
In practice:
- Automation of repetitive, low-value tasks
- Real-time synchronization between your applications
- Automatic notifications, reminders and approvals
- Fewer data-entry and transfer errors
3. Connect your tools so there is a single version of the truth
In many small and mid-sized companies, the same piece of information exists in several places: an Excel file, a record in the CRM, a spreadsheet on the drive. Everyone works from their own version. Decisions get made on data that is no longer current.
I connect your tools to each other so information moves without friction — and so everyone starts from the same place.
In practice:
- Integration between your existing applications (SharePoint, Airtable, Google Workspace, and others)
- Centralized data, without duplicates
- Access rights matched to each role and each team
- One reliable source for your whole organization
4. Train people so it lasts
A tool nobody really uses is worth nothing. Resistance to change within teams is not irrational — it usually comes from a lack of explanation or support.
I make sure every solution deployed is understood, adopted and mastered by the people concerned. The goal is not to create a dependency on my work — it is the opposite.
In practice:
- Hands-on training matched to each team’s level
- Clear, reusable documentation (guides, short videos, procedures)
- Step-by-step support during the transition
- Full autonomy for your teams once the engagement ends
5. Choose solutions that do not lock you in
Some tools are powerful but expensive to leave: high migration costs, data that is hard to get back, dependency on a single vendor. That kind of choice can look harmless at the start and become a constraint a few years later.
I favor open, scalable solutions that you stay in control of — so your organization can grow and adapt without starting over.
In practice:
- Tools selected for their longevity and their interoperability
- No dependency on a single provider
- Exportable, portable data
- Predictable costs, kept under control over time
What this changes in practice
An organization whose tools are clear, connected and properly used makes better decisions — because the information is reliable. It loses less time — because repetitive tasks are automated. And it is less fragile — because the data does not sit on one person’s machine.
If you recognize your own situation in what you have just read, let’s talk.