The Operations Stack for a Lean Greek SME: CRM, Invoicing, Reporting as One System
Walk into a typical small Greek company and count the subscriptions: an invoicing tool, a spreadsheet pretending to be a CRM, another spreadsheet pretending to be reporting, a shared drive nobody structured, and a founder’s inbox holding it all together. Each tool was a reasonable decision. The pile is not a system, and the pile is expensive in the only currency an SME cannot print: the owner’s time. Turning that pile into one connected operation is the operations integration work we do most often. Here is the blueprint.
The cost of tool sprawl (it is not the subscriptions)
The subscription fees are noise. The real costs are structural. Data entered twice is data wrong once: the client exists in the invoicing tool, the spreadsheet and the inbox, with three different phone numbers. Nobody can answer basic questions quickly: What is our pipeline? Who owes us money? Which service line actually makes margin? And month-end becomes archaeology, assembling numbers from four places to learn what happened five weeks ago, far too late to act. We showed in Cash, Compliance, and Clarity how exactly this blindness kills otherwise healthy young companies.
The stack: four layers, connected
A lean SME needs four layers, and the connections between them matter more than the brand names:
1. CRM: the single truth about customers. Every contact, deal and conversation in one place, from first enquiry to signed engagement. The test of a real CRM is brutal: if the founder disappeared for two weeks, could someone else pick up every open deal from the record alone? A spreadsheet fails that test the day it is created.
2. Invoicing and expenses: cloud-based, myDATA-aligned. In Greece this layer is non-negotiable: invoicing data must flow to AADE’s myDATA platform, and the sane way is a cloud tool that does it natively, not a retrofit at audit time. As we noted in our ΙΚΕ formation guide, this belongs in place before invoice #1. The same layer should show, at a glance, who has paid and who is overdue; receivables chasing is a workflow, not a memory exercise.
3. Documents: structured, shared, permissioned. Contracts, proposals and deliverables in a shared cloud structure with naming conventions, not in personal inboxes. Boring, decided once, enormous compound returns.
4. Reporting: the monthly hour that replaces the monthly weekend. Cash position, receivables, pipeline, revenue by service line, pulled from the layers below, not re-typed into a new spreadsheet. When the layers are connected, management reporting is an hour of reading, not a weekend of assembly.
Connection is the product
Each layer alone is a subscription; connected, they become an operating system. The deal marked “won” in the CRM becomes the client in the invoicing tool, entered once. The invoice issued becomes a line in receivables and a number in the monthly report, automatically. The proposal in the document store links from the CRM record. Modern SME tooling connects through native integrations and lightweight automation platforms; the technical lift is genuinely small. What is hard, and what determines success, is process: who enters what, where, once. That is a design decision, and it is exactly the business-process design work described on our consultancy services page.
The build order that works
- Map how work actually flows today: enquiry to cash. One page. The gaps will be obvious and slightly embarrassing; that is the point.
- Fix invoicing first. Compliance and cash visibility are the survival layer.
- CRM second, populated in one honest afternoon, with a rule: if it is not in the CRM, it does not exist.
- Documents third. Structure and migrate.
- Reporting last, because now the data exists to report on.
Resist the temptation to do all four simultaneously; sequenced, each step pays for the next.
AI, quietly
We practice what we preach: our own company runs on exactly this stack, with AI layered on top for drafting, reporting summaries and content operations. The connected stack is what makes AI useful: a model reading clean, connected data produces insight; a model reading four contradictory spreadsheets produces confident nonsense. Foundation first.
Getting there without stopping the business
The whole transition, done properly, is a short engagement, not a transformation programme: assessment, design, setup, migration, and a handover the team actually understands. Our business consultancy services run it end to end, by operators who built and run their own lean Greek company on the same stack we recommend. The deliverable is not software. It is a company where the owner’s evenings belong to the owner again.
Frequently Asked Questions
What tools does a lean SME actually need?
Why is tool sprawl expensive?
In what order should an SME fix its operations stack?
Where does AI fit in a small company’s stack?
Editorial note — This article was researched and drafted with the assistance of Claude (Anthropic), and reviewed and approved by Amazing Projects before publication.
