By KYN AI Advisory Team — AI implementation specialists, Singapore
Per-seat software is rent that rises with headcount. Custom software is a one-off build fee plus a monthly retainer, and you own what is built. Neither is cheaper in general. The answer depends on how many people use a tool, how stable the workflow is, and whether the tool does anything you cannot get elsewhere. A one-afternoon audit of your licences and bottlenecks tells you which side each workflow falls on.
Why does the software bill keep climbing?
Three mechanisms, none related to how complex the work is.
- Headcount. Per-seat pricing charges per user. Hire three admin staff and the bill moves. The workflow does not.
- Duration. A subscription continues as long as you use the tool. There is no end date and no asset left over.
- Currency. Software billed in a foreign currency exposes a ringgit budget to exchange-rate movement over the year.
None of these is unreasonable. They are the cost shape of rented software.
How do you audit your licences in an afternoon?
- List every tool and its seat count. Write down what each licence does for each user.
- Mark what you will still pay for in three years. Treat those as permanent costs, not project costs.
- Flag the sales bottleneck. Steady inbound enquiries by website, WhatsApp or email that the team cannot follow up fast enough.
- Flag the admin bottleneck. Contracts, approvals, expenses and reconciliation that eat into the week.
A workflow is a rebuild candidate if few people pay per seat for a repetitive task, it touches two or three systems, and the process rarely changes. Keep renting the rest.
Is custom software cheaper than licences?
Compare the structure of the costs before comparing quotes.
| | Per-seat licences | Custom build with KYN | |---|---|---| | Cost shape | Recurring fee while you use the tool | One-off build fee, then a monthly retainer of at least twelve months | | What grows the bill | Headcount | Scope agreed after the review | | What you hold at the end | Nothing | Rights in the custom code and configuration, on full payment | | If you stop paying | Access ends | Everything keeps running; you can revoke KYN's role | | Quote | Public price list | After the review; no price list |
Do the sum over three years for one workflow: seats times fee times months, against build fee plus retainer. Include the staff hours the tool does not remove.
A custom system is not a route to zero subscriptions. It often runs on a CRM or accounting system you already pay for.
Can a custom system sit on top of the CRM I already use?
Yes. Sales and operations layers can read from and write to HubSpot, Salesforce or your accounting platform instead of replacing them. For an insurance brokerage, outreach with one checkable first line costs about S$0.02 per email, and replies are sorted at about S$0.01 each, written back to the existing CRM.
A custom layer makes sense where you need rules your CRM does not support: approval routing, contract generation from templates, expense capture, or a morning report that joins several systems. For a manufacturer, eleven systems became three on one AWS account, and each department gets a 06:30 report on WhatsApp at about S$0.05 per report.
Who owns the code and the accounts?
Ask this of any vendor, not only KYN. Our terms:
- Every system runs in a cloud account in the client's name.
- Rights in the custom code and configuration pass to the client on full payment.
- The client can revoke KYN's role and everything keeps running.
Ask for the same in writing from any alternative. Without it, a custom build is only a more expensive subscription.
How is it kept secure?
- Named accounts through the cloud provider's identity service. No shared logins.
- Row-level security in the database.
- One restricted account per user per session.
- Agents have their own restricted accounts.
- Every action is logged with the actor.
- Outbound messages, money, filings and deletions wait for a named person.
For personal data, check Malaysia's Personal Data Protection Department for current rules on collecting and transferring customer data.
A worked three-year comparison
The figures below are illustrative. They are not KYN prices and not any vendor's price. Replace them with your own invoices.
Take one workflow: expense claims and approvals for a 40-person company. The finance team rents an expense tool at an assumed RM 30 per user per month.
| Item | Per-seat tool | Custom build | |---|---|---| | Year 1 | 40 users x RM 30 x 12 = RM 14,400 | Build fee plus twelve months of retainer (quoted after the review) | | Year 2 | RM 14,400, plus any new hires | Retainer continues; no build fee | | Year 3 | RM 14,400, plus any new hires | Retainer continues, or you stop it and the system keeps running | | Headcount grows to 60 | RM 21,600 a year | No change from seats; a change request if the workflow changes | | Hours not removed | Staff still key in approvals by hand | Rules route approvals; named person confirms payment |
Read the table in three steps. First, fill the left column from last year's invoices. Second, ask for a quote after a review and fill the right column. Third, add the cost of staff hours each option leaves in place. The option with the lower three-year total is the answer for that workflow. It may differ for the next workflow.
Which workflows should stay on licences?
Not every tool should be rebuilt. Use this table as a first sort.
| Workflow | Keep the licence if | Consider a custom build if | |---|---|---| | Email and calendar | Always | Never | | Accounting ledger | The package fits your reporting and your accountant uses it | You need data from three systems joined in one report | | CRM | Fields and reports fit how you sell | Routing, approvals or handover rules do not exist in the package | | HR and payroll | Statutory rules are handled by the vendor | Almost never; the vendor carries the rule updates | | Quotes and contracts | Few templates, few approvals | Many templates, several approvers, links to inventory or finance | | Operations reporting | One system holds all the data | Data sits in several systems and spreadsheets |
Statutory work, such as payroll and tax filing, usually belongs with a vendor who updates the rules. Custom work pays back on workflows that are specific to how you operate.
What do you ask a vendor before you sign?
Ten questions, for KYN or anyone else. A vendor who cannot answer them in writing has told you something.
- In whose name is the cloud account?
- Who holds the source code, and from what date?
- What happens to the system if we stop the retainer?
- What is the minimum term, and what does the retainer cover?
- How do I export all my data, and in what format?
- Who has access to production, and how is it logged?
- Which actions can the system take without a named person?
- How are backups taken, and when was the last restore tested?
- Which third-party services does the system depend on?
- What does a change request cost, and how long does it take?
What are the risks of a custom build?
- Scope creep. A build that grows without a decision costs more than it was quoted. Agree the scope after the review and hold changes to a written change request.
- Key-person risk. If one engineer knows the system, a resignation is a risk. Ask for documentation and a second named person.
- Poor requirements. If the workflow is not understood, the system automates the confusion. This is why the first 14 days are interviews and an inventory, not building.
- Over-building. Some workflows are better left manual or on a package. A fair review says so.
What does a first project look like?
Choose one workflow with these traits: the same steps every time, two or three systems involved, a clear owner, and a measurable delay. Common first projects for Malaysian SMEs are enquiry follow-up, quotation generation, expense capture and a daily operations report. Agree three numbers before the build starts: current time per task, current error count per month, and the number of people who touch the task. After launch, compare against those three.
Start small. A first system that works earns the decision to build a second. If the three numbers do not move after ninety days of use, review the workflow with the team before you extend the system or pay for more changes.
How do you plan an exit before you start?
An exit plan is a short document written at the start, not a dispute at the end. It has five lines.
- Accounts. The cloud account is in your company's name, with your administrator listed as owner.
- Code and configuration. A copy sits in a repository you control, updated at each release.
- Data. A full export in open formats, such as CSV and SQL dumps, can be run on request. Test it once in the first quarter.
- Credentials. A list of every service key the system uses, with the owner of each.
- Handover notes. One page per workflow saying what it does, what it reads and writes, and which actions wait for a named person.
If you revoke KYN's role, the system keeps running because it never depended on KYN's accounts. The notes tell the next engineer where to start. Ask for the same plan from any other builder, and test the data export before you need it.
How long does a build take?
The first 14 days are a review: an inventory of your stack and interviews with your team. A full build ships in under 90 days. After launch, the monthly retainer covers changes, monitoring and fixes. The minimum term is twelve months.
KYN is a Singapore company and works remotely with teams in Malaysia, which shares a working day with Singapore. See pricing and integrations.
Frequently asked questions
Is it cheaper to build custom software than to pay per seat?
It depends on seats, stability and lifespan. Compare three years of licences with the build fee plus retainer for one workflow. Include the hours the licence does not remove.
Do I own the code if KYN builds it?
Rights in the custom code and configuration pass to you on full payment. The system runs in a cloud account in your name, and you can revoke KYN's role while it keeps running.
How does KYN charge?
A one-off build fee, then a monthly retainer of at least twelve months for changes, monitoring and fixes. It is quoted after the review. There is no price list.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
