The portals, the remits, the weekly filing.
Every Monday at 7:00 am your agent files the week's remits to your shared folder and leaves one line: what arrived, and what waits on a person. Anything a portal will not let a bot do comes to a person. A payments summary is available if your team wants one. For billing companies first.
Billing agent, Monday 7:00 am22 remit files filed. 1 waiting on a person to sign in to a portal.
- Each file named with date, amount and portal.
- A person approves or sends messages to payers and clients.
Example layout on example data.
One agent, one job, in your kind of business.
A billing assistant that logs into your payer portals, files the remits and tells you what needs a person.
- Monday, 7:00 am: last week’s remits filed and a one line note in your team thread.
- Each remit renamed and filed to your folder.
- When a portal needs a person, it asks one, with the screen shared.
In use as a pilot at one medical billing company since August. De-identified billing operations only until a BAA is signed.
A month-end assistant that knows which clients still owe you documents, checks what came back, and drafts every reminder for you to send.
- One checklist per client, kept up to date.
- Reminders drafted in your voice. You read and send.
- For a fractional CFO with several clients: one view of who is late across all of them.
New angle. No customer yet. We would set up the first checklist with you on the call.
An operations assistant that produces the reports your vendors keep asking for, from your own ERP, on the day they are due.
- Monthly vendor reports regenerated line for line in the format your vendors expect.
- Bills matched to purchase orders.
- Bills that do not match are held for you.
Running at a lab supply distributor, our reference customer. Aggregate counts only, no names.
An office assistant for the reports and follow-ups that eat the owner’s evening: job status for the prime contractor, subcontractor invoices checked, overdue payments chased.
- Starts with a few questions about what takes your week.
- Each plan is built from your own words.
- Each plan is drafted for you to approve or hold.
No construction customer yet. Shown on example data, and we say so on the call.
One option we are testing: a paid pilot.
This is one variant for the team to react to.
Once, to set up one agent on one job in your real systems. Plus USD 990 a month, with a 60 day minimum.
A month per agent, month to month, with 1,500 actions included. You see actions done, never a usage meter.
- A named person on our side.
- A short weekly note (planned).
- Approval cards for the steps that matter.
Why not just use Claude yourself?
Claude is very good. Using it on its own, or through a desktop tool such as Cowork, is a fine way to get one person more done. Running a business function on it is a different job.
| Where it gets hard | Claude or Cowork on your own | Luminorix |
|---|---|---|
| Across the organisation | A good fit for one person's own work. Sharing it across a team is left to you. | Set up and run for a team, so a new person uses what is already working. |
| Your data | It sits in the account that set it up. Where it goes is yours to manage. | A workspace for each customer, a record of actions, and a plain list of what we do not have yet. |
| What it costs | Model usage adds up with every task, and someone has to watch it. | Model usage is our job to manage. You see the work done, not a usage meter. |
| When nobody is at the desk | Usually runs when a person starts it. | It runs on a schedule and on events, and writes to you in Teams, Telegram or email. |
| Who sets it up and runs it | You do. | We do. A named person on our side answers when something looks wrong. |
Built on Claude, operated by us, embedded in your business. It works when nobody is at the desk, lives in your channels, has a name, a role and a memory, has control built in, and is done for you.
A person on your team approves or sends.
AI agents draft the next step. For the steps that matter, you get a card with the reason and you approve or hold. Every action is on the record, and where an action can be reversed you can undo it. A spoken yes never approves; you tap.
- On its own: read, draft, prepare.
- Comes to you as a card: sending, posting, paying, changing a price.
- Our hard stop list: moving money, writing to someone new, deleting.
Send 2 reminders. Hold 1 for you.
You read each draft first. Where an action can be reversed, you can undo it.
Example card on example data. Nothing here is connected to a real system.
See it on your own business.
The proposal above is one option we are testing. Exact terms come after we know the job.
- A short call with a founder.
- We ask what takes your week before we show anything.
- A person on your team approves or sends. Every action is on the record.