What you keepweek two
- Repositoryyours
- Databaseyours
- Credentialsyours
- Runbookwritten
Kill test
still runsDelete us, wait thirty days.
Hong Kong · AI and ownership consultancy
No client logos yet — the terms instead
Own the softwareyou run on.
Bandicoot inventories what you rent, rebuilds the tools you need on your own accounts, and hands them over. Code, data and credentials stay yours.
An illustration of the handover, not a client record.
What we can promise before we meet you
Two weeks · A fixed fee · You own everything
2weeks
to a diagnostic
Bandicoot is an AI and ownership consultancy. We inventory the software you rent, rebuild what you actually need on your own accounts, and hand it over.
Hong Kong first, then Singapore and Australia. The client keeps the code, the database and the accounts — and we say in writing what happens when they stop paying us.
The founder
Bandicoot · Hong Kong
Name and portrait to be added
Material
The standard
Three tests, not adjectives: the kill test, the stranger test and the handover test. A system that fails one is not finished.
Material
The terms
Two weeks, a fixed fee, and a ranked list you keep whether or not you use us. There is no subscription to us.
Tools that
outlive the vendor.
Every service starts with the same two-week diagnostic and ends with something running on your accounts. Start with the one costing you the most hours, not the one that sounds most like AI.
No client logos yet. These are the tests.
- Kill test
- Stranger test
- Handover test
Kill testStranger testHandover test
You cannot stop renting
what you cannot see.
Book a call2weeks
to a diagnostic
Fixed fee, fixed length. The map is yours either way.
9services
in the catalogue
One way in: the diagnostic.
4calculators
live, no signup
Price the pain before you call.
3tests
we hold ourselves to
Kill, stranger, handover.
Facts we can defend before we have met you. No client statistics, percentages or logos are published on this page.
Three things have to be
true before we call it delivered.
The work is judged on what remains when we are gone, not on what we presented. These are the three conditions, in the order the diagnostic tests them.
Read the standardInventory the stack
We count every subscription, seat and renewal, follow where the data lives and who can reach it, and time the work people do between systems. You cannot stop renting what you cannot see, and the bill is usually the smallest part of the cost.
Build it on your accounts
The tool is written into your repository and runs in your database, with your credentials. We do not keep a private runtime that switches the work off when you switch us off. The model writes code and explains it; scripts fetch, transform and validate the numbers.
Hand over, then leave
Documentation a stranger can follow, a runbook for the failures, and a care plan that is optional. We delete our access and wait thirty days. If the report still arrives and the logins still work, the handover was real.
Nine services.
One way in.
Every one starts with the two-week diagnostic and ends with something running on your accounts. The catalogue is a menu of first projects, not a list of things to buy separately.
- 01The stack auditEvery subscription, seat and renewal, with owners and a data map.Audit
- 02Back-office automationInvoices, email, documents and calls read and written into your systems.Automation
- 03Role assistantsOne job, wired to the systems it uses, answered from your own records.Assistant
- 04Knowledge chatYour documents, cited by paragraph, hosted where your rules require.Knowledge
- 05Document checksEvery report and submission checked against your rules before it leaves.Checks
- 06Support automationDrafted replies and correct routing on the ticketing system you own.Support
- 07Voice agentCalls answered, qualified and logged; a conversation that ends in a record.Voice
- 08Market monitorA daily brief with sources, and alerts when a threshold is crossed.Monitor
- 09AI advisoryA standing weekly session and written decisions for teams already building.Advisory
No client quote has
been cleared yet.
The carousel works; the words are missing. When a client gives written permission, the placeholder is replaced and the section stays. Until then, the three ownership tests are the only proof on this page.
PlaceholderClient quote
REPLACE WITH A REAL CLIENT QUOTE
PlaceholderClient quote
REPLACE WITH A REAL CLIENT QUOTE
PlaceholderClient quote
REPLACE WITH A REAL CLIENT QUOTE
9
Services, all reached through one diagnostic.
0
Subscriptions to us. Stop paying and it runs.
From a rented stack
to a system you own.
Get started01
Discovery
Week one. We sit with the people who run the close, the invoice queue and the inbox. We count subscriptions and seats, follow where the records live and who can reach them, and time the work rather than asking how long it takes.
02
Strategy
Week two. The inventory becomes a shortlist: what to replace first, what owning it costs, what it saves, and what stays broken if you leave it. Every figure carries its arithmetic, so you can challenge it line by line.
03
Development
The chosen service is built in your repository and against your systems of record. There is no model in the data path: scripts fetch, transform and validate, and the exception queue is designed for the person who will actually work it.
04
Deployment
It goes live on your accounts, documented for a stranger. We stay long enough to prove the kill test and to train the team, then the care plan is yours to take or leave. Nothing switches off when you leave.
Fixed fee, fixed length.
Never a subscription.
Two ways to buy the work, and one optional way to keep it running. No dollar figure is published here because no price has been quoted for your company yet — the toggle shows the basis, not a number we have invented.
How the two bases differ
One-off is the only way to buy the work: a fixed fee for the diagnostic, a fixed fee for the project, quoted after the diagnostic and never before. Monthly exists only for the optional care plan. Stop paying it and the system keeps running, because it runs on your accounts.
Read what the diagnostic includesThe rule
No model
in the data path.
A wrong number needs a line of code behind it, not a prompt. Scripts fetch, transform and validate every figure. The model writes the code and explains it; it does not compute the number that reaches your board pack.
Get startedSourcesCRM · ERP · accounting
Scriptsfetch · transform · validate
Numbersone definition each
- 01FetchFrom the system that owns the figure.
- 02TransformOne definition per number, written down.
- 03ValidateThe arithmetic is checked before it ships.
The model writes code and explains it. It does not compute the number that reaches your board pack.
Contact
Two weeks · fixed fee
Two weeks to know
what you actually have.
A fixed-fee diagnostic: the stack, the data and the cycle times, with a ranked list of what to fix first and the arithmetic behind every figure. You keep the document whether or not you use us.
- Hong Kong
- Companies of 20–200 people
- No subscription to us
Before you book
Frequentlyaskedquestions.
Five things buyers ask before the diagnostic. If yours is not here, the answer is probably in the funnel notes.
Ask something else01How long does the diagnostic take?
Two weeks, fixed fee. Week one measures the stack, the data and the cycle times. Week two turns that into a ranked list with a cost and a saving against each item.
02What do I keep if I do not proceed?
The map. The stack inventory, the data map, the timed close, the ranked list and the arithmetic behind every figure. It is yours either way, and we say so in writing before we start.
03Do we own the software you build?
Yes. Code in your repository, data in your database, credentials in your accounts. We delete our access and wait thirty days; if everything still runs, it was yours.
04Do you put a model in the data path?
No. Scripts fetch, transform and validate the numbers. The model writes code and explains it, so a wrong figure has a line of code behind it rather than a prompt.
05What does it cost?
The diagnostic is a fixed fee agreed before we start, quoted per company because twenty subscriptions and two hundred are different jobs. The project is quoted after the diagnostic, never before. The care plan is optional and the system runs without it.
Funnel notes
The work,
written down.
Each of the nine problems has a page: the arithmetic, the two tests, and what the diagnostic measures. No dates, because the problem does not go out of date.
All nine funnels01F1 · Invoices
Your invoices are typed twice.
Read, matched and entered once, into the accounting system you already own.
02F5 · Reporting
The Monday report takes all of Monday.
Built overnight from the systems that hold the numbers.
03F8 · Data entry
If the data entry stopped, the business would notice.
Forms and messages that land in your systems without a person retyping them.