bandicoot

Two weeks. A fixed fee. A map you keep.

Own the software
you run on.

Bandicoot inventories what you rent, rebuilds the tools you actually need on your own accounts, and hands them over. Code, data and credentials stay yours.

Hong KongCompanies of 20 to 200 people

What we are held to

No client logos yet. These are the tests instead.

  • The kill test
  • The stranger test
  • The handover test
  • No subscription to us
  • Fixed fee, fixed length
  • Your repository
  • Your database
  • Your accounts
  • Hong Kong

About us

We measure a system by whether it still runs without us.

Bandicoot is an AI and ownership consultancy in Hong Kong. The premise is plain: a company should fully own all the software it generates together, including what its agents generate. Data ownership is a consequence; the software is the thing that gets kept.

We work with companies of 20 to 200 people whose numbers take weeks to assemble: ecommerce operators, licensed professional firms, distributors and agencies with a finance lead. The question is usually the same one — what are we actually paying for, and what would it take to own it instead?

Read how the work is done

2weeks

The diagnostic

Fixed fee, agreed before we start. The map is yours either way.

0subscriptions

To us

Code in your repository, data in your database, runs on your accounts.

Key features

Four things we build, and what each one replaces.

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.

View all nine services

01 · Audit

The stack audit

You cannot stop renting what you cannot see. We inventory every subscription, seat and renewal, follow where the data lives, and time the work people do between systems.

  • Owners and renewal dates
  • A data map
  • A ranked list with the arithmetic

02 · Back office

Back-office automation

Invoices, email, documents and calls are read and matched, then written into the accounting, CRM and ticketing systems you already own. One exception queue is left for a person.

  • Invoices read and matched
  • One exception queue
  • No re-keying between systems

03 · Knowledge

Knowledge chat

Finance handbooks, procedures and contracts answered in plain language with the paragraph cited, from your documents rather than the open web.

  • Answers cite the source
  • Permissions follow roles
  • Hosted where your rules require

04 · Checks

Document checks

Reports, invoices and submissions are checked against your rules before they leave, every one rather than a sample, with failures queued for a person and the reason attached.

  • Your rules, written down
  • Every document checked
  • Failures queued with a reason

The handover

Delete us and wait thirty days.

That is the kill test, and it is the whole claim. A walkthrough of a real handover belongs here, filmed rather than staged. Until there is one to publish, the button opens the standard in writing.

Kill test · Stranger test · Handover test

The walkthrough · recording pending

The handover

No recording is published yet.

We film a handover when there is a real one to film, not a stock demo. Until then, this is the standard the recording would have to show:

Benefits

What stays with you when the project ends.

The work is judged on three tests — kill, stranger, handover — rather than on a feeling about the last workshop. These are the five things those tests protect.

You keep the code

The repository is yours from week one, with the commit history and a README that explains it. We do not keep a private copy that only we can run.

You keep the running system

It runs on your accounts, in your database, with your credentials. Delete our access and wait thirty days: the work still gets done without us.

No model in the data path

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.

Fixed fee, fixed length

The diagnostic is two weeks and the project is quoted after it, never before. There is no open-ended day count and no subscription to us.

Hong Kong, next to the buyer

Same timezone, same regulator, same language, and someone on site when the work needs it. Singapore and Australia as the work travels.

How the three tests are applied

Three steps

From a rented stack to a system you own.

The diagnostic is two weeks, in two halves, and then one project. Each step ends with a document or a system in your hands, not a slide.

  1. 01Week one

    Measure

    Week one. We count what you rent and time what it costs you to use it, with the people who run the work rather than the people who bought the software.

    • Every subscription, seat and renewal, with its owner
    • A data map: each source, where it lands, what reaching it costs
    • The close and the planning cycle, timed rather than estimated
    • The exceptions a person handles by hand, watched as they happen
  2. 02Week two

    Rank

    Week two. The inventory becomes a shortlist, and every line on it carries a cost to own and a saving you can check. Then we argue it through with you.

    • What to replace first, and what owning it costs
    • The saving written as arithmetic, not as a percentage
    • What stays broken if you leave it alone
    • A ranked list you can act on with or without us
  3. 03After the ranking

    Build and hand over

    One service, fixed scope, delivered on your accounts. We document it, train the team that will own it, and then we leave.

    • Code in your repository, not our workspace
    • Data in your database, credentials in your accounts
    • A runbook a stranger can follow in a day
    • The kill test: delete us, wait thirty days, everything still runs

Start with the two weeks. The map is yours either way.

Book the two-week diagnostic

Pricing

Three ways to buy. Only one recurs.

The diagnostic is the only ask: two weeks, a fixed fee, and the map is yours. A project is quoted afterwards, never before. The care plan is optional and the system runs without it.

Billing period

The diagnostic and the project are one-off fixed fees; only the care plan changes basis.

Project

One service from the nine, delivered and handed over.

Fixed feeSame price

Fixed scope, quoted after the diagnostic.Fixed scope, one invoice. No annual rate applies.

  • One service, fixed scope and fixed fee
  • Quoted after the diagnostic, never before
  • Code in your repository and a documented handover
  • The team trained to change it without us
  • Care plan optional, never required
Read the nine services

Care plan

For the firm that would rather keep us on call.

MonthlyAnnual

Quoted per company. Stop any time.Quoted per company, one invoice for twelve months.

  • We keep it running and answer the page
  • A fixed number of changes each month
  • The same repository, still yours
  • Stop it and the system keeps working
  • No lock-in and no subscription to a platform
Ask about the care plan

Fees are quoted per company, because twenty subscriptions and two hundred are different jobs. No subscription to us, and no annual discount to argue about.

Testimonials

What clients say, once they have said it.

No client has cleared a quote for publication yet, so these three cards are placeholders. They will be replaced with real words and a real name, or removed.

Placeholder

REPLACE WITH A REAL CLIENT QUOTE

Client nameRegion
Placeholder

REPLACE WITH A REAL CLIENT QUOTE

Client nameRegion
Placeholder

REPLACE WITH A REAL CLIENT QUOTE

Client nameRegion

FAQ

Questions the buyer actually asks.

If the answer is not here, ask it directly: hello@bandicoot.ai. We would rather answer it once on this page than twice on a call.

What does the two-week diagnostic produce?

A stack inventory with owners and renewal dates, a data map showing every source and what it costs to reach, the close and the planning cycle timed rather than estimated, and a ranked list of replacements with a cost and a saving against each one. The arithmetic behind every figure is included so you can challenge it.

What does it cost, and how long does it take?

Two weeks, fixed fee, agreed before we start. It is quoted per company because twenty subscriptions and two hundred are different jobs. Any project afterwards is quoted separately and only after the diagnostic, never before.

Do we own what you build?

Yes, and that is the point. Code goes into your repository, data into your database, and the running system onto your accounts. You keep the credentials and the documentation, so cancelling us does not switch anything off.

What is the kill test?

After handover we delete our access and wait thirty days. If the work still gets done, the report still arrives and the logins still work, the system was yours. If any of that stops, the project was not finished.

What is the stranger test?

A developer who has never met us opens the repository, reads the README and ships one change in a day, without asking us anything. That is the standard the documentation has to meet before we call a handover done.

Do you put AI in the path of our numbers?

No. Scripts fetch, transform and validate the figures, and the model writes code and explains it. We do not let a model compute the numbers that go into a report, because a wrong figure needs a line of code to point at.

Do you work outside Hong Kong?

Hong Kong first, then Singapore and Australia. The work is done on your systems and handed over in writing, so distance matters less than access and a shared working day, but we start where we can be in the room.

The one ask

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. You keep the document whether or not you use us.

Or work out what it costs first: four free calculators.