amazity Get early access

Build your business. Amazity does the rest.

Tell it how your company works. It becomes the tooling around your product, keeps it running with agents that stay inside your rules, and asks you before anything that matters.

Get early access See how it works

The rest is most of it.

Onboarding. Billing. Renewals. The support queue. The follow-up you meant to send. The spreadsheet that became a system. None of it is your product. All of it eats your week.

How it works

Four things, in order.

1

Say it in your words.

Describe your company like you'd brief a new hire. Customers, plans, tickets, renewals, and how they hang together. That is your ontology, and Amazity builds on it rather than bending you to a template. Your entities, your relations, your rules. No field called "custom 1".

"We sell seats on annual plans. A customer signs up, someone runs onboarding, tickets come in, and every plan has a renewal date. Maya approves any discount over 20%."

becomes your ontology

customer has many plans · has many tickets plan has one renewal · discount over 20% needs Maya
2

Change it by asking.

Ask for what's different this month. See exactly what will change, line by line. Nothing moves until you publish. Every publish is a release, and the one before it is kept.

Add a health check before a renewal goes out. If they haven't logged in for 30 days, route it to me first.
Workflow · renewal · draft
+steps.health_check · wait until last_login < 30 days, else route to Maya
~steps.send_renewal.after job_created → health_check
+customer.last_login · date
draft 8c1f2a9e · valid Publish · release 14
3

Let it run.

Give an agent a job across your tooling: chase the overdue, prep the renewals, keep the records straight. It works inside the rules you set. Anything above its limit comes to you as a question, not a surprise.

Chase everything overdue and tell me what's stuck.
Bookkeeper
records.query · invoices · overdue · 3 email.send · reminder · Halden & Co email.send · reminder · Orme Builders invoices.write_off · needs you
Two reminders sent. Bramley sent an insolvency notice on 3 Sep, so I'd write INV-2198 off. That's above my limit. Your call.

Bookkeeper wants to run invoices.write_off

Above your auto-approve limit of £500.

invoice: INV-2198
amount:  £1,240.00
reason:  client insolvent

4

Everything is written down.

Every record change, every agent step, every release: who, what, when, and which version of your rules was in force. Not a log you export. The way the thing is built.

Ledger · this morning

Your data

It's already there. In six places.

The customer list in a spreadsheet. Invoices in the billing tool. Conversations in an inbox. An export nobody opens. Amazity brings them into your ontology, so the same customer is one customer, and what it finds gets acted on.

Where it lives
Your ontology
Auditor
records.match · customers · 2 duplicates records.merge · "Halden and Co Ltd" → Halden & Co billing.read · INV-2231 · paid 9 Sep records.update · invoice · overdue → paid workflow.cancel · reminder · Halden & Co
Halden & Co were two customers across the sheet and billing. Merged them. They paid INV-2231 on the 9th, so I marked it paid and pulled the reminder before it went out.

Agents

Hired, not installed.

Each agent gets a name, a mark and a remit across your apps. They share your ontology, your rules and your context. No separate world of bots to keep track of.

Why trust it

Trust isn't a promise. It's the build.

  1. 01

    Only what the moment allows.

    Every kind of record needs an access rule before it can exist. There is no default where everyone sees everything, and the server decides, not the screen.

  2. 02

    It asks first.

    Agents propose exact steps. Above your limits, they wait for you. Nothing runs off the books, and nothing runs on a version of your rules you haven't published.

  3. 03

    Forward only.

    A publish is a new release. The one before it is kept, whole. What was true last month can be shown, not reconstructed.

  4. 04

    One ontology, everywhere.

    Apps, agents, imports and reports all speak the same entities. There is no second model of your business hiding in a bot, a sync job or a spreadsheet.

You build. It does the rest.

Get early access

Early access, by invitation.