By KYN AI Advisory Team — AI implementation specialists, Singapore
A 30-person company in Southeast Asia typically runs its work across six jobs, each with its own tool: mail and documents, accounting, customer records, messaging, project or stock tracking, and spreadsheets that fill every gap. This is an observation from our stack reviews, not a survey, and we publish no percentages. The pattern is consistent. The tools are sound individually. The cost sits in the places where one tool ends and a person retypes into the next.
How reliable is this picture?
Fact: KYN reviews the stack of each client in the first 14 days of an engagement. Fact: we do not hold a statistical sample, and we do not publish counts of which products appear how often.
View: the categories below recur often enough to be useful as a checklist. The specific products vary by country, industry and who set the company up.
Use the picture to find your own gaps. Do not use it to prove that "most companies" do anything.
Which tools recur, by job?
| Job | Typical tools | Usual state | |---|---|---| | Mail, calendar, files | Google Workspace or Microsoft 365 | Works. Shared drives grow unmanaged | | Accounting | Xero, QuickBooks, Accurate, local packages | Works for the ledger. Poor at everything upstream | | Customer records | A CRM such as HubSpot, or a spreadsheet | Often incomplete; WhatsApp history lives outside it | | Messaging | WhatsApp Business app or platform | Where customers actually write | | Operations | A spreadsheet, a stock tool or an ERP module | The most varied layer | | Reporting | Spreadsheets pulled by hand | Rebuilt monthly |
Local conditions change the column. Local accounting packages appear alongside Xero in Indonesia. Hong Kong companies often keep a mix of English and Chinese documents. Each market adds its own filing duties. The shape holds: a few good tools plus a layer of spreadsheets.
Where do the tools overlap?
Overlap is the first thing we look for, because it creates two versions of one fact.
- Two places for customer details. The CRM and a sales rep's own sheet. The rep's sheet is current. The CRM is what management reads.
- Two places for stock or job status. The ERP and a warehouse workbook. The workbook wins on the floor.
- Two places for approvals. A message thread and a form. Neither shows the full history.
- Two places for "who owns this". An email thread and a task board.
In one manufacturer we reviewed, the stock position lived in several workbooks and a legacy system. Eleven systems became three on one AWS account. The point is not that eleven is bad. The point is that each extra system multiplies the places a fact can differ.
For the general problem see why small businesses struggle with fragmented software tools.
Where do the gaps cost the most?
Gaps are the jobs no tool does, so a person does them by hand. In order of cost, from our reviews:
- Document capture. Bills, receipts and delivery notes arrive by mail, WhatsApp and paper. Someone types them in.
- Reconciliation. Bank lines against ledger entries. Someone matches by eye.
- Chasing. Overdue invoices, missing documents, unanswered quotes. Someone remembers.
- Reporting. Numbers from three systems pulled into one sheet each week.
- Handover. A lead becomes an order becomes an invoice. Someone retypes at each step.
Each gap is rule-based and repeated. That makes each a candidate for automation. They are also the gaps that grow with volume, so the cost rises as the business does.
How many tools is too many?
There is no correct number. Use these tests instead.
- Retype test. Count the times a person types the same fact into a second system. Each is a cost and an error source.
- Owner test. Every tool should have one named owner who knows what it holds and who has access.
- Exit test. Can you export your data in a usable form? If not, you are renting your records.
- Access test. Does each person have their own login? Shared logins break the audit trail.
A tool that passes all four earns its place, however many you have.
When should you replace a tool, and when should you connect it?
Replace a tool when it fails the exit test, when the vendor no longer supports your use, or when its limits block growth. Connect tools when each does its job well and the problem is the handover.
Connecting is cheaper and less risky than replacing in most cases. Your accounting package holds years of history and your auditor knows it. Keep it. Build the layer that feeds it and reads from it. Our article on custom CRM versus HubSpot and the one on off-the-shelf versus custom WhatsApp systems set out the trade-offs for two of the common layers.
What does a minimal connected stack look like?
For 30 people, a workable shape has four parts:
- System of record per domain. One ledger, one customer table, one stock or job table. Each fact has one home.
- A connecting layer. It moves data between records, applies rules and logs each action.
- A front end shaped to the team's work. Staff see their queue, not the database.
- Agents for the repeated steps. Document capture, matching, chasing and reporting, with a named person approving anything outbound, financial or irreversible.
The connecting layer is the part most companies lack. Without it the first two items are only a list of tools.
How do you run your own stack review in one afternoon?
You need one person who knows the business and one blank sheet. Do it in four passes.
- List every tool, paid or free, including personal accounts staff use for work and the chat groups where decisions get made.
- For each tool, write the owner, the data it holds, the monthly cost and the number of logins. Gaps in this row are findings in themselves.
- Draw the handovers. For one order, one hire and one invoice, trace the facts from first touch to final record. Mark every place a person retypes.
- Rank the handovers by volume times effort. The top three are your work list.
Expect to find tools nobody owns and logins nobody can account for. Fix those first, since they are the security risk. Then pick the handover with the most volume and the clearest rule, and automate that one before you touch the rest.
Where KYN fits
KYN builds that connecting layer and the agents on top of it, and leaves your accounting package, mail and file tools where they are. For a manufacturer, we moved 10,210 vendor quotes into one place and built a ledger of 3,309 reconciled rows with zero duplicates. For KYN's own books, bills arrive from Gmail and receivables are chased at 3, 14 and 30 days.
The first 14 days are the review: an inventory of your stack and interviews with your team. A full build ships in under 90 days. The systems run in a cloud account in your name, with named accounts, no shared logins and row-level security in the database. See integrations and infrastructure.
Frequently asked questions
How many software tools does a 30-person company use?
We do not publish a count, because our reviews are not a survey. Count your own, including spreadsheets and chat groups, since those carry real processes. The number matters less than the number of places one fact is typed.
Should a small company move everything to one ERP?
Sometimes. An ERP reduces overlap and increases switching cost. Check the exit test and the fit with how your team works before you commit, and compare it with connecting what you have.
What is the first gap to close?
Usually document capture, because every later step depends on it. If bills and receipts reach the ledger without retyping, reconciliation and reporting get easier.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
