The slowest thing in Kova is the moment it takes you to release a payment.
Most buying at a fashion brand happens in email and on WhatsApp, and the books find out afterwards.
The software that promised to make finance faster made money move faster than the rules that govern it.
Press and keep holding.
What a brand does today
The founder's inbox and a spreadsheet
Nothing to set up, and everyone already knows where the quote is.
Nothing is written down before money moves. The accountant learns about the purchase from the invoice.
Card-first spend tools
A card is a wonderful thing for software and travel, and the controls are real.
The mill wants a wire against a pro forma. The order, the match and the vendor are outside the card's view.
Procurement suites
Every control a procurement department could want, and an audit trail to match.
You do not have a procurement department, and you are not going to hire one to run the software.
The ERP's purchase module
The order and the stock live in one place.
Buying still happens in email, and someone types it in afterwards, so the module records what was already decided.
What it would look like if it were right
- Buying stays where the team already talks.
- Every purchase is written down before money moves.
- The rules are readable, and they say who decided.
- Nobody wonders.
Write your purchasing policy
Seven sentences. The numbers are yours. A purchase runs through them as you type.
We are people and of us approve. Today says yes.
We buy about times a month, mostly , and vendors give us .
Our books are in . We pay from .
Sixty-two rules come with Kova, compiled and sealed at build. They cannot change at runtime.
Above $5,000 a second person is required.
Every canonical order is checked to within one cent before it is written.
Your agent, under a name you choose, on your own domain.
She reads the quote, drafts the order, matches the invoice and writes to the vendor, with a line in every message saying she is an agent on Kova.
Approving and releasing money cannot be expressed in her tools. Not refused. Not expressible.
If the model returns an amount that is not a whole number of cents, the amount is thrown away.
Facts you can check
- Releasing a payment takes a deliberate hold. Let go early and nothing happens.
- the release control
- Every audit row carries the 12-character hash of the ruleset in force when it was written.
- the audit log
- 62 rules in 17 guideline files, compiled and sealed at build. They cannot change at runtime.
- the guidelines package
- If the model returns an amount that is not a whole number of cents, the amount is thrown away.
- the extraction step
- Approving and releasing money cannot be expressed in the assistant's tools.
- the tool registry
- Above $5,000 a second person is required.
- the approval chain
- An approval can be undone for a fixed window. Then it is done, and it says so.
- the undo window
- Every canonical order is checked to within one cent before it is written.
- the canonical order check
Four things people ask
- We are twelve people.
- You just wrote that three of you approve. That is a policy, and it is enough.
- Our accountant is on Fortnox.
- Kova hands you the file your accountant imports, with a hash on it. QuickBooks Online and Xero connect directly.
- I do not want a model near my money.
- Neither do we. Approving and releasing money is not in the agent's tools, and a figure that is not whole cents is thrown away.
- How much?
- We cover that on the call.
We bring teams on a few at a time.
When it is your turn you book 20 minutes. You leave with your policy live, your ledger connected, and your agent named.
Request access