Key takeaways
- Time is rarely lost inside a system. It is lost at the seams between systems.
- Count the places a number is typed twice. That count is your real integration bill.
- Every seam costs three things: delay, drift, and nobody owning the answer.
- In one system a quote, an order, a delivery, an invoice and a receipt are links, not re-typed copies.
- Ten kinds of document post themselves to the ledger — and posting the same one twice does nothing.
Ask anyone what slows their week down and they will name a system. The CRM is clunky. The accounting package is old. The spreadsheet is a monster. Replace the named villain and the week is somehow still slow.
That is because the time was never really being spent inside those systems. It was being spent in the gaps between them — the moments where one person finishes their part, and another person begins theirs by typing the same information in again.
Count your seams
Here is a short exercise that tells you more than a software demo will. Take one ordinary transaction — a customer asks for a price, you deliver, you get paid — and write down every time a human moves information from one place to another.
A typical version reads something like this. The enquiry arrives by email and someone notes it in a spreadsheet. The quote is written in a document. When it is accepted, someone types the lines into the order system. The warehouse gets a printout. Someone tells accounts it shipped. Accounts types the invoice. At month end, someone reconciles what was invoiced against what was actually delivered, finds three discrepancies, and spends a morning on them.
That is six or seven handoffs to sell one thing once. None of them is anybody’s fault, and none of them shows up as a line item anywhere.
Nobody budgets for re-typing. It is simply absorbed, one afternoon at a time, by the people who are best at their jobs.
What a seam actually costs
Delay. Information does not move at the speed of the business. It moves at the speed of whoever is free to move it. A delivery that happened Tuesday becomes an invoice on Friday because that is when someone got to the pile.
Drift. Two systems that were reconciled last month are not reconciled now. Neither is wrong in any obvious way — they simply learned about the world at different moments, and nothing forces them back into agreement.
Nobody owns the answer. This is the expensive one. When someone asks how much that customer owes, or whether that job was profitable, the honest answer is “let me check with two people and get back to you”. Every question becomes a small project.
Watch out for
The seam that looks like a feature. Exports are the usual disguise. A monthly CSV from one system into another feels like integration, but it is a handoff with a schedule attached: it carries only what the export was built to carry, it is a snapshot of a moment already gone, and when it silently fails nobody notices until the numbers are questioned.
What it looks like without the seams
The alternative is not a heroic integration project. It is a system where those steps were never separate to begin with — where the order knows which quotation it came from, the delivery knows which order it belongs to, and the invoice knows both.
That distinction sounds academic and is not. If the link is real, the second document does not need re-typing: it is created from the first, carrying the customer, the lines, the prices and the terms with it. If the link is a person, the second document needs re-typing every time, and every time is a chance to be wrong.
Every arrow is a real link in the data — not a number somebody re-typed.
The accounting end is where this pays for itself. Ten kinds of document — customer invoice, supplier invoice, goods received, goods shipped, receipt, deposit, payment, card settlement, card statement, import declaration — post themselves to the ledger from the document itself. The posting rule lives in the system rather than in the head of whoever normally does it. And each posting is idempotent: post the same document twice and the second attempt does nothing, which is the difference between a safe process and a nervous one.
Some of what follows is genuinely difficult to do by hand and easy to get quietly wrong. A supplier invoice does not simply become an expense — part of it may capitalise into stock value, part may clear goods that arrived before the invoice did, part may be a fixed asset. Cost of sales gets recognised against the goods that actually left the building. None of that is work anyone should be doing in a spreadsheet at 11pm.
It is not only sales and money
The same handoff problem shows up everywhere else, and it is the reason “we’ll just use a separate tool for that” tends to compound.
A support ticket is the clearest example. A ticket that lives in its own help desk knows about itself. A ticket that belongs to the business knows which customer raised it, which project it belongs to, who it is assigned to, and — this is the part standalone tools almost never have — whether and how it should be billed. That single attribute is the difference between support that is a cost centre by assumption and support that is a cost centre by measurement.
The same is true of the humblest record in the whole system: someone reporting that they did some work. In most companies that record exists in several incompatible shapes — a timesheet for the office, a job card for the field, a note on a maintenance visit, a line on a production report. When they are one record type that can attach to any kind of job, “how much time went into this?” becomes a question with one answer, whatever “this” happens to be — a project task, a service call, a maintenance visit, a production run, or a kind of work that only your business has.
In practice
The test for whether something belongs in your main system is not how important it is. It is how often its data has to meet other data. A tool that never needs to answer a question jointly with anything else is fine on its own. Almost nothing is that tool.
Where Capitán fits
Capitán is one system with the modules already connected, which is a different proposition from a suite of products that integrate.
On the commercial side that means CRM, sales and purchasing feeding inventory and financial accounting without a re-keying step in between, with payroll posting into the same books. On the operational side, projects, help desk, maintenance, facility management, quality control and HR all record work against the same customers, sites and people — and, where it applies, production sits in the same chain rather than beside it.
Where your business does something the modules do not describe, that becomes a record type you define rather than another tool with another seam, and the rules around it are configured rather than remembered. Dashboards then read across all of it, because there is no “all of it” to assemble first.
If you want to know how many seams you actually have, talk to our team — walking one transaction end to end is usually a twenty-minute conversation, and it is a useful one even if you change nothing.
The short version
Count the times a number gets typed twice. That number is what you are really paying, and no individual system on your list is going to reduce it. Only the links between them will.