Most small business owners would never use the word “sovereignty” for this problem, and that is fine. In practice, it comes down to a few boring questions: Can you get your files out? Do you know where they live? Would the business keep moving if a vendor account disappeared tomorrow?
Most small businesses cannot answer all three confidently, and that is not because they are careless. It is because the tools they depend on were not designed to make these questions easy.
What sovereignty gaps look like
Consider a consulting firm that keeps all client documents in Google Drive. It works well: sharing is easy, the price is right, the mobile apps are decent. But the firm’s Google Workspace account is tied to a single administrator’s email, and one day that administrator’s account gets flagged for a policy violation they do not understand. Access is suspended. Client files are inaccessible. Appeals take days or weeks.
This is not a hypothetical. Account suspensions happen regularly on every major platform, and the recovery process rarely moves at business speed.
Or consider a photographer whose entire portfolio lives on a website builder. The template looks great, the editor is intuitive, and then the builder changes its pricing tier or discontinues the plan. The photographer wants to move — but exporting the site produces a zip file of garbled HTML that no other tool can use. Two years of work, effectively starting over.
Or an accountancy practice using free email — say, info@firmname.gmail.com instead of info@firmname.ie. The Gmail account works fine until a client’s email system flags it as unprofessional, or until the practice wants to switch to a different provider and realises the address cannot follow.
These are not catastrophes. They are friction points that compound over time, and each one traces back to the same structural issue: someone else controls the infrastructure your business depends on.
What sovereignty actually means in practice
Sovereignty does not mean running your own servers. It does not mean rejecting cloud services. It does not mean spending weekends configuring Linux machines instead of doing your actual work.
It means understanding what you control and what controls you.
In practical terms:
Own your domain. Your domain name is the one piece of digital infrastructure that is genuinely portable. If you own yourbusiness.ie, you can point it at any website host, any email provider, any service — and switch any of them without losing your address. If your “domain” is a subdomain of someone else’s platform, moving means starting over.
Keep local copies of important files. Cloud storage is fine for day-to-day access. But if every copy of your client files exists only on someone else’s servers, you have a single point of failure that you do not control. Periodic local backups are not paranoia; they are basic risk management.
Use exportable formats. Before committing to a tool, check how your data comes out. Can you export to standard formats — CSV, PDF, Markdown, plain text? Or does the export produce something only the original tool can open? This single test tells you more about a vendor’s intentions than any marketing page.
Know what you are renting versus what you own. Software subscriptions give you access, not ownership. That is fine for most tools. But for the things that matter most to your business — client records, financial data, intellectual property, the content you publish — renting access to someone else’s system deserves more thought than defaulting into it.
The gradual approach
You do not fix everything at once. Sovereignty is not a switch you flip; it is a direction you move in.
Start with what matters most. For many small businesses, that means three things: own your domain, control your email, and keep local copies of client files. Those three changes take a few hours total and cost less than a typical SaaS subscription. Everything else — migrating to better tools, choosing providers that respect export, reducing single-vendor dependency — can happen over months, one piece at a time.
The point is not to become a technology company. The point is to stop being surprised when a vendor decision disrupts your work.
The trade-offs, honestly
More ownership means more responsibility. If your email is self-hosted, you handle the DNS records. If your files are local, you handle the backups. If your website is on your own infrastructure, you handle the uptime.
Not everyone needs or wants that level of control, and that is a legitimate choice. A freelance writer who keeps everything in Google Docs and is comfortable with the trade-offs is not making a mistake. The mistake is not knowing the trade-off exists.
Where Leanersoft fits
This is what we work on. Not selling fear about cloud services, but helping people understand what they control and what controls them — then building the systems that shift the balance.
Semnote is part of that: a document environment where your files stay on your device, in a format you can read and move. Our services are the other part: practical engineering work that helps small businesses move toward ownership at their own pace, without pretending the destination is the same for everyone.
If any of this sounds relevant to your situation, that is probably a good starting point for a conversation.