Small businesses don't need perfect systems. They need systems that work reliably and that someone can explain to them clearly.
Over roughly eight years working in a small technology services company, I supported dozens of SMEs with their technical needs. Here is what that taught me.
Most problems are not technical
The majority of support requests I handled were not really about broken software. They were about confusion, mismatched expectations, or missing documentation. A client who cannot find their DNS settings is not experiencing a technical failure — they are experiencing an information design failure.
The most useful skill I developed was not troubleshooting. It was learning to explain things simply, without condescension, in a way that gave the client confidence to act.
Reliability beats sophistication
SMEs do not need cutting-edge solutions. They need email that works, websites that load, and domains that resolve. When I set up a Microsoft 365 tenant for a client, the measure of success was not how elegantly it was configured. It was whether the team could send emails without thinking about it six months later.
This shaped my approach: choose boring technology, document everything, and test the obvious paths first.
Documentation is delivery
I learned early that delivering a solution without documentation is only half-delivering. If the client cannot maintain or understand what was set up, the value degrades quickly. Every DNS change, every hosting migration, every M365 configuration got documented — not for me, but for whoever would need it next.
What I would do differently
I would have invested more in structured knowledge management earlier. A lot of what I knew lived in my head or in scattered notes. Building repeatable processes and shared documentation would have saved time and made handovers smoother.
I would also have started building my own projects sooner. Supporting clients taught me a great deal, but building something from scratch teaches different lessons — about architecture, about decisions with long-term consequences, and about owning the outcome end to end.