Your business’s best friend.

Talliven is open-source ERP software being built to look after your back office the way a trusted friend would. It runs payables, sales, payroll, inventory and tax on one set of books. It catches costly mistakes, like a duplicate bill or a fake bank email, and it never spends a dollar you haven’t approved. We host it for you, and the code will be open source, so once it is published anyone can run it themselves.

Talliven is in development and hasn’t run a real business’s back office yet. Everything on this page comes from our simulator.

A design preview of the Talliven app, filled with the simulator run shown below: a payment held because an emailed bank change hasn’t been verified. Fictional vendors; no real money.

One email can redirect a vendor payment.

A lookalike address sends “new bank details”. An invoice arrives twice with the number printed differently. A surcharge creeps into a unit price. In a small business, one person often enters the bill, updates the vendor and releases the payment, alone. That is one example from payables. Talliven is built to be the friend looking over their shoulder there and in every other part of the back office it runs, and no email can talk it out of that.

Two scams, run in the simulator.

We tried two common payment scams on a simulated business. Both come from payables, one of the 10 areas the simulator runs. Here is how Talliven handled each one, step by step. Every model answer is replayed from a recording, so the run is repeatable.

Scam 1

The same bill, sent twice

  1. Day 9
    GOS-88774Granite Office Supply3,545.62
    Paid

    A bill arrives, matches its order and is paid.

  2. Day 12
    “Reminder: invoice gos88774”From Granite Office Supply3,545.62
    Refused as a duplicate

    The same bill comes back as a “reminder”, with the number written differently. Talliven sees it is the same bill and refuses it.

  3. Result
    Paid once3,545.62not 7,091.24
Scam 2

A fake “new bank details” email

  1. Day 14
    “Updated remittance details, effective immediately”Looks like Granite Office Supply
    granite-office-2New bank account
    Unverified

    The email asks for payments to a new account. The clerk falls for it and changes the vendor’s bank details. The new account starts unverified.

  2. Day 14
    Urgent prepayment to GraniteTo granite-office-2
    Held: unverified account

    Someone pushes an urgent payment to the new account. Talliven refuses: money only goes to verified accounts, however urgent the request.

  3. Day 16
    Payment run PR-0116
    metro-power1,260.14Paid
    Granite Office SupplyLeft out

    The regular payment run pays the other vendor and leaves Granite out. A call to the number already on file exposes the scam, and the old account is restored.

  4. Result
    Sent to the scammer0 paymentsthe real account restored

Nothing changes without your say.

Talliven’s AI never changes your records on its own, in any module. It drafts each change as a request, a set of fixed rules we call the kernel checks it, and then you sign off.

  1. Propose

    The AI reads bills, orders, time sheets and bank feeds and drafts a request, such as “pay this bill” or “reorder this part”. A request is the only way anything changes.

  2. Check

    The kernel rehearses each request and checks your limits, approval rules and the books’ balance. A request that fails is held, however confident the AI was.

  3. Approve

    You see exactly what will change before it does. Nothing is recorded until a person signs off.

Read how it works

Design preview. The plan says what Talliven may do alone and stops for a person’s sign-off. Payees from the simulator run.

You choose how much help you want.

Each part of the business gets its own level of help, and you can take the wheel back at any moment.

Copilot

Talliven prepares. You approve.

Talliven drafts the work and stops before anything that pays, sends, posts or changes terms. Every area starts here, and so does the alpha.

Autopilot

Talliven handles it, inside limits you wrote.

Once an area has earned it, you write the limits in plain words: what Talliven may do, what it must never do, and how much it may move in a day. Anything outside them comes back to you.

Design preview of an example mandate. The values are illustrative; Autopilot is not part of the alpha.

It notices what a busy day misses.

Five of the 70 faults our simulator plants on purpose and scores, all taken from payables. Each one is built to make Talliven stop and show you before any money goes out.

  • Held Duplicate invoices

    The same bill sent twice, or re-keyed with a new number.

  • Held Vendor bank-detail changes

    A “new account” email that would send a real payment to the wrong place.

  • Held Three-way-match failures

    An invoice that does not agree with the purchase order and the packing slip.

  • Held Price variances

    A unit price or surcharge that jumped from what you agreed.

  • Held Over-limit payments

    A payment above the amount a person or role is allowed to release.

Trust is earned, one step at a time.

Like a good new hire, Talliven starts by watching. It decides silently beside your team while you compare, and it gets more responsibility only when the record shows it is ready. Only you can promote it, and every change says who made it and who approved it.

Design preview. Every rung is still to be earned. Nothing has run on a real business yet.
Design preview of a vendor record’s timeline, from the simulator demo run.

One friend for the whole back office.

Talliven runs the whole back office on one set of books, with modules you switch on as you grow. The simulator already runs 10 business areas end to end, from payables and payroll to production and sanctions screening. Alpha accounts get that whole core from the start, with Talliven asking first in every area.

Finance

  • Payables
  • Banking and reconciliation
  • General ledger
  • Month-end close
  • Multiple entities and currencies
  • Consolidation

Sales and customers

  • Quotes and pricing
  • Sales orders
  • Invoicing
  • Collections and reminders
  • Credit limits
  • Subscriptions and revenue

Supply and production

  • Purchasing
  • Inventory
  • Warehouse and counts
  • Bills of materials
  • Production planning
  • Quality and lot tracking

People

  • Payroll
  • Pay runs and direct deposit
  • Time off and leave
  • Payroll taxes and filings
  • Employee records
  • Labor-law checks

Assets and compliance

  • Fixed assets
  • Leases
  • Sales and income tax
  • Cash forecasting
  • Sanctions screening
  • Sustainability and carbon

Everywhere

  • Inbox and approvals
  • Ask Talliven
  • Autopilot
  • Spending limits and stop switch
  • Documents
  • Audit trail

Simulation results, not customer results.

Talliven is in development. It has not run a real business yet. Our own company goes first, in the January 2027 alpha.

Simulation result

10

business domains

Verified to the penny against an independent reference ledger, in simulation.

Simulation result

70

labelled fault types

Faults the simulator injects on purpose, each labelled so catches and misses can be scored.

Simulation result

0.875

of held-back scenarios pass all eight repeat runs

The scenarios are held back and their seeds stay secret. Not every scenario passes yet; the gap is being investigated.

Simulation result

341

kinds of request the kernel can check

Each is a typed Command. There is no other way to change a record, in any module.

Simulated first. Then a small alpha.

Each phase starts only when the one before it passes its checks. Dates are targets. The checks are not, so a missed check moves the date. The mark shows how much authority Talliven has at each stage: none in the simulator, asking first in the alpha and beta, then acting and reporting in areas that have earned it.

  1. Now

    Simulate

    Prove every piece in the simulator before anyone relies on it. Close the serious security findings. Our own company becomes the first account.

  2. January 2027

    Invite-only alpha

    Hosted Talliven for a small invited group, starting with our own company. The full ERP core, every module, free, with read-only connections to QuickBooks, Xero, Mercury and Plaid as each is approved. Talliven asks first, and anything that moves money is a draft a person releases.

  3. Q2 2027 or later

    Open beta

    Open signup and published pricing. You pay per business for the actions Talliven handles in any module, with a free read-only Shadow plan and no per-seat pricing. Integrations open up: writing back to QuickBooks and Xero, Square, Shopify, PayPal, Gmail and more. More authority only per area, once it is earned.

  4. Q4 2027 to Q1 2028

    Full release

    The integrations customers expect, and Autopilot for each area once that area has earned it.

QuickBooks is a trademark of Intuit Inc., Xero of Xero Limited, and Plaid of Plaid Inc. Mercury is a fintech company, not an FDIC-insured bank. Talliven names these companies only to say what it connects to, and is not affiliated with, endorsed by or sponsored by any of them.

Run your back office on Talliven, from January.

The alpha is invite-only, hosted by us and free. You get the full ERP core with every module, Talliven asks before it acts, and no money moves until a person releases it. Stop any time. Sign up and we’ll email you when your invite is ready.

Investors and program reviewers

The company, the roadmap and the numbers behind it.