For a year and a half I ran a thirty person team across five products. Slack for talking. ClickUp for projects. Zendesk for customer support. Email for clients. Spreadsheets for everything the other four could not hold.
Individually they were fine. Some of them were very good. The problem was never any one of them, it was the space between them.
Nothing in that stack knew about anything else, so I did. Or my team did. A deal closed in one place and somebody typed it into another. A client's details changed and somebody updated two systems and forgot the third. Every week ended with an export and an import, and every export and import was a person moving information by hand between two things that should have already agreed.
That work is invisible while it is happening. Nobody logs it. Nobody complains about it, because it feels like the job.
Here is what it actually costs.
On a good day it costs time. Somebody spends an hour on Friday reconciling a spreadsheet against a project board, and that hour is not billed to anyone.
On a normal day it costs detail. Something gets missed in the copy across, and nobody notices it was missed, because the only proof it existed was in a system nobody is looking at anymore.
On a bad day it costs money. Somebody is tired or busy or does not feel like doing the transfer, and it does not get done. Then support answers a client who is angry about work they were never told about. Or an invoice goes out wrong. Or a client is quoted by someone who cannot see the four open tickets on their account.
None of that is carelessness. The person answering the ticket cannot see the deal. The person sending the invoice cannot see the tickets. The person doing the work cannot see either. Everyone is looking at a different copy of the same customer, and the copies drift.
I tried the ordinary fixes first. Automations between tools. Paid integration tiers. All of it moves data between systems, and moving data between systems is not the same as having one system. Two copies that sync are still two copies, and when they disagree you have no way to know which one is right.
I also looked at the all in one products. Most of them are five separate apps behind a single menu. The billing does not know what the CRM knows. You get one login and one bill, and you still have five databases.
So I stopped shopping and started building, on one rule. One customer record. Every part of the product reads and writes to the same record. Not five tools that sync, one tool that never had to.
Six months of planning, building, throwing work away and building it again.
What the rule made possible
Take one client, from the first enquiry to the money landing.
An enquiry arrives through a form I built myself, with the fields I actually need, not the fields a form product decided I needed. It becomes a lead. I choose who on my team can see it, because not everyone should see everything.
When that lead becomes a client, nothing is re-entered and nothing is copied. The same record changes state.
The work is set up as projects and tasks against that client and assigned across the team. As I assign it, workload calculates itself, because the people side of the product is reading the same records the projects are. I do not keep a capacity spreadsheet and I do not ask anyone how busy they are.
When the work is done the amount becomes an invoice, and billing picks it up from there. Income, expenses, what is outstanding, in one view, without a reconciliation at the end of the month.
If that client raises a support ticket, whoever answers it can see the deal, the projects and the invoices. They know who the client is and what they are worth before they type a word.
Everything the team needs to know about how we work sits in a wiki inside the app, searchable, next to the work itself, instead of in a document nobody opens twice.
That is not five tools with better integrations. It is one set of records, seen from five angles.
I was not the only one
Before I committed to building it, I talked to other owners and managers running businesses the same size as mine. Same stack, near enough. Same two complaints every time.
The bill. Five products priced per person, and every hire raises all five.
The switching. Nobody could tell me how much time their team lost moving between tabs, but every one of them knew it was a lot.
That was the point I stopped treating this as my own problem.
I am not going to claim it is finished. But the thing I set out to fix is fixed. I run my business from one place, and the parts of it know about each other.
Spodus is open to everyone from today. I am shipping new features every week and improving what is already there, and I would rather hear what is missing than what is good. If you run a service business and you are paying for four or five products to do it, I want you in this early.