Your own database. Every sign-off, on record.

Your business gets a database of its own, with its own keys, and your team signs in with a one-time code. Anything that moves money waits for your yes.
A closed matte-white box with a seam of lavender light under its lid, three loose tiles beside it
Debtor remindersApproved, 09:14

Supplier payments

Waiting for you

Morning, Name. I've matched 12 supplier invoices to their orders. Ready to pay nine suppliers on Friday, $12,350 in all. Pay them, or change first?

Example thread, sample data

Who holds the keys?
You do.

The accounts your system runs on sit in your business's name from the first day, and so do the code and the data. Another developer can pick it up.

The database itself decides who sees what.

Five plain facts keep your records with the people who should see them. We describe what we do; we do not claim certificates we do not hold.

  1. Its own database

    Each business we build for gets a database of its own, with its own keys.

  2. Who sees what

    Access narrows to each person and each job, so everyone sees their part.

  3. A one-time code

    Your team signs in with a one-time code instead of a password.

  4. A PIN on the floor

    A device the whole floor shares signs in with a PIN rather than a personal code.

  5. The day someone leaves

    When someone leaves the business, their access is removed on the day they go.

Your business

Viewing as the workshop floor

View as

Sign-inPIN on a shared device
  • Money

    Not in view

  • Payroll

    Not in view

  • In view

    Stock

    Stock and orders

    4 below reorder

  • In view

    Jobs

    Jobs and bookings

    38 open

  • Customers

    Not in view

  • Approvals

    Not in view

Held in the databaseWho sees what, a PIN on the floor2 of 6 in view
Illustrative screen. Not client data.

Each agent reaches only what its job needs.

Each agent gets one job and a written rule for when it stops and asks. Anything that moves money, reaches a client or is published waits for a person, and the yes is recorded.

Stock watch

Waiting for youRuns on Grok Bot
Can reachStock and ordersSuppliersNothing else

Today, 09:00

Morning, Name. I've drafted a purchase order for the four lines running low. Ready to send it to your usual supplier, $690 in all. Send it, or change first?

Sign-off record
  • Purchase order, four linesWaiting for you
  • Payroll prep, week 41Approved, Mon 16:40
  • Quote, Thursday's site visitApproved, Mon 11:12
Example thread, sample dataPress “Send it” to give your yes
  1. Only what the job needs

    Each agent can reach what its one job needs, and nothing else in your business.

  2. It stops and asks

    A written rule says when it stops, and it waits for your answer: silence is never a yes.

  3. Every yes on record

    Each approval is recorded in the Foundation, in one place with your reports and dashboards.

Agents say they are AI, in the first message.

Every agent says it is an AI agent in its first message to anyone new, before anyone could think they are talking to a person. Not only when asked.

Example thread, sample data. An example chat. The customer asks: Hi, is my order ready to collect? The agent replies: Hi, I'm [agent name], the AI agent who looks after customer replies for [Business name]. I can check an order for you, or put you through to the team. Signed [agent name], for [Business name]. Two buttons follow: Check my order, and Talk to the team.
  1. AI, in the first message

    Its first message to anyone new says it is an AI agent and names its job and your business.

  2. Signed as your business

    Messages are signed agent name, for Business name, so customers know whose agent it is.

  3. A person is always reachable

    Every agent that talks to your customers offers a way to reach your team.

  4. Never a pretend person

    It never claims to be human, signs as a staff member or uses a human photo.

What passes through, and what stays in your name.

We set the agents up on Grok Bot and OpenAI dots, inside the system we build for you. The agent runs on the platform; your Foundation and its data sit in your name.

Your Foundation

Your records and sign-offs

Only what its job needs

The agent

One job, set up by NORION

The work passes through

Grok Bot or OpenAI dots

Chosen per job

The agent reaches only what its job needs in your Foundation, and the work it does passes through Grok Bot or OpenAI dots, the platform chosen for that job.

What passes through

The work an agent does passes through its platform, so each agent gets only what its job needs.

Independent of both

NORION is an independent company that sets up agents on both platforms, and neither company endorses NORION.

Bring us the job nobody has time for.

A call, thirty minutes, no deck. Then a written note on what we would build first, and a quoted scope, or an honest reason not to bother.