By KYN AI Advisory Team — AI implementation specialists, Singapore
This is the first entry in KYN's monthly changelog, so it records the baseline: what runs today, what each unit of work costs, and the rules every change follows. Later entries list only what changed since the last one. We publish the baseline first because a changelog without a starting point cannot be checked. Where a number appears, it is a unit cost from our own live systems. It is not a promise about yours.
What is a changelog, and why publish one?
A changelog is a dated list of changes: what was added, altered or removed, and why. We publish ours for two reasons.
- Buyers can verify claims. If we say a reply is sorted for about S$0.01, you can see when that figure was last measured.
- We hold ourselves to our own standard. Every system we build for clients has a log with the actor and time. Our public record should meet the same bar.
We will not list a change we cannot attribute to a date. We will not list a result we did not measure.
What runs at KYN today?
The baseline below is the state of the systems at 30 October 2026. Client systems are described by industry only.
| System | Industry or owner | What it does | Unit cost | |---|---|---|---| | Morning report | Manufacturer | Sends each department a report on WhatsApp at 06:30 | About S$0.05 per report | | Ledger | Manufacturer | 3,309 reconciled rows with zero duplicates | Not applicable | | Vendor quote migration | Manufacturer | 10,210 vendor quotes moved | Not applicable | | Outreach | Insurance brokerage | Email with one checkable first line | About S$0.02 per email | | Reply desk | Insurance brokerage | Sorts each reply by intent | About S$0.01 per reply | | Benefits comparison | Insurance brokerage | Group benefits comparison to a client PDF | About S$0.03 per comparison | | Document platform | Estate planning | Runs on Google Cloud with Microsoft Entra sign-on | Not applicable | | Receipts, claims and GST | Finance software startup | Built to production in six weeks on Google Cloud | Not applicable | | Article engine | KYN | Produces articles | About S$0.06 per article | | AI search check | KYN | Runs a check across 22 prompts | About S$0.05 per check | | KYN books | KYN | Bills from Gmail, receivables chased at 3, 14 and 30 days, payroll on 2026 CPF rules | Not applicable |
Unit costs depend on the model used and the length of the text. We re-measure them when a model or a prompt changes, and the changelog will record the new figure and the date.
Which numbers deserve extra care?
Two figures in the table carry context that a bare number hides.
The ledger. A ledger of 3,309 reconciled rows with zero duplicates means every row matched a source document and no row appears twice. It does not mean the underlying business was error-free. It means the reconciliation found no unexplained difference. Our explanation of the method is in automate bank reconciliation in Singapore.
The 06:30 report. About S$0.05 per report is the model and messaging cost of producing and sending one report. It excludes the build and the monthly retainer. Count those if you are comparing against a person doing the same task.
The other figures follow the same rule: they are per unit of work, not totals.
What counts as a change?
Not every edit belongs in the log. We list four types.
- Added. A new capability, system or article series. Example: a new agent role.
- Changed. An existing behaviour altered, including a limit, a threshold or a model.
- Fixed. A defect corrected, with what was wrong and how long it was live.
- Removed. A capability retired, with the reason.
Each entry follows one template:
Date:
Type: Added | Changed | Fixed | Removed
System:
What changed (one sentence):
Effect on cost or accuracy (a number, or "not measured"):
Approved by (a named person):The last two lines matter most. "Not measured" is an honest entry. A guess dressed as a number is not.
What rules does every change follow?
Whatever the system, a change passes the same gates. They are the same rules we apply to client systems.
- Named accounts. Everyone who changes a system signs in through the cloud provider's identity service. No shared logins.
- Row-level security. The database enforces who can read and change each record.
- Restricted accounts. One restricted account per user per session. Agents have their own restricted accounts.
- Logging. Every action is logged with the actor and time.
- Waiting for a person. Outbound messages, money, filings and deletions wait for a named person.
A change that weakens any of these does not ship. See security for the full list.
How do we handle changes in a client's system?
Clients on a retainer receive the same kind of log for their own system. The retainer covers changes, monitoring and fixes, and runs for at least twelve months after the build. Each month the client sees what changed, who approved it and what it did to cost or accuracy.
Because the system runs in a cloud account in the client's name, the client can check the log against the cloud provider's own records. That is the point of owning the account. A vendor's changelog that you cannot verify is a claim. One you can check against your own account is evidence.
How should you read the next entries?
Treat each future entry as a diff against this baseline. Look for three things.
- Unit cost movements. A change in the S$0.05 report cost tells you whether newer models help or hurt.
- Fixes. The number and age of fixes shows how fast we find our own faults.
- Removals. What we stop doing is as informative as what we add.
If an entry lacks a date, an owner or a measurement, treat it as marketing and tell us.
What stays out of this log?
Three things never appear in a public changelog. Client names, because we describe clients by industry only. Client data, including amounts from client ledgers beyond the counts listed above. Security details that would help an attacker, such as account identifiers or the layout of a client's network. If a change touches one of these, the entry says what type of change it was and leaves out the specifics.
A change that cannot be described without those details goes into the client's own log instead, where the client controls who reads it.
Where KYN fits
This article is itself an example of how KYN works: state the facts, name the owner, record the date. In a client project, the first 14 days are a review of your stack and interviews with your team, and a full build ships in under 90 days. A one-off build fee is followed by a monthly retainer of at least twelve months, quoted after the review.
Rights in the custom code and configuration pass to you on full payment, and you can revoke KYN's role while everything keeps running. For worked examples, see case studies. For pricing structure, see pricing.
Frequently asked questions
How often will this changelog be updated?
Monthly. The next entry will list changes since 30 October 2026. A month with no change will say so.
Are the unit costs prices I will pay?
No. They are costs of running a unit of work in our own live systems. Your cost depends on your volume, your model choice and your text length. We quote after the review.
Where do I see changes to my own system?
In the monthly log delivered with the retainer, and in your cloud account's own records. Both show the actor and the time.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
