Mini-apps · built with Claude
The screen your process is missing. Described in a sentence, run with your own permissions.
A customer card with exactly your fields, a form for after a visit, a planner that knows who is free. Describe it, and Claude writes it as a Mini-app: one small page that lives inside the CRM and can do nothing the person using it could not.
What people build
One screen, one purpose, shaped like your process.
Not a feature request that waits for a release. A page your team uses this week, inside the contact or the opportunity it is about.
A customer card
Exactly the fields your team fills in, in the order they think about them, inside the contact.
A visit report
One form after a visit: logs the activity, sets three fields and books the follow-up with the right person.
A small planner
Who is free on Thursday, who already has the most on their plate, and one tap to assign it.
A client file with health data
A gym’s client file: measurements over time and medical notes, kept in the protected store, with the client’s signed consent.
From a sentence to a page
How a Mini-app gets made.
aicroo documents itself for Claude: the guide it hands over already knows your fields, your departments and what you are allowed to publish.
Describe it
Ask for it in the app’s Create with AI panel, or hand Claude the guide aicroo writes for your company, with your fields, your departments and what you may publish.
It is checked
The page is checked against the rules the moment it arrives. One that reaches outside, asks for access it does not use, or turns data into code is refused, with the reason.
Preview it
Run it on your real data with your own permissions. Writes are simulated unless you switch live writes on.
Publish it
The fields it needs are listed for you to confirm, and created in the CRM. Every version is kept, so you can restore an earlier one or unpublish.
Use it
As its own screen, or as a section inside a contact or an opportunity with that record already open. On the web, and in the phone, tablet and Mac apps.
What a page can do
Enough to run a real process, with control built into every capability.
Read and update the CRM
Contacts, opportunities, activities and their custom fields, with server-side search and paging.
Under control
Only what the page declared it needs, and only what the person looking at it may do.
Log the work
Create activities with their alerts, and add notes to an opportunity.
Under control
The same records the CRM screens create, with the same checks.
Assign it to the right person
The team with their faces, department, availability on the day and current load, so a page can propose who takes it under your rule, and the person can override it.
Under control
Assigning is its own permission. The assignee must be an active employee, and is told.
Hold sensitive data
Health data goes in the protected store, encrypted and logged, and consent can be requested from inside the page.
Under control
Mini-apps are the only place those values are ever shown.
Why it is safe to run
A page written by a model, with the powers of the person looking at it.
The rules are enforced by the product, not suggested to the author. That is what makes it reasonable to let a model write the code.
Watched by
Compliance
It runs as the viewer
Every call runs with the permissions of the person looking at the page, and the database decides. A page cannot do anything that person could not do by calling the API themselves.
It cannot reach the outside
The page runs in a sandboxed frame with no network at all. It cannot call anywhere, load a script, style or font from anywhere, or navigate away. Its only channel is the bridge to aicroo.
It asks for exactly what it uses
A page declares the access it needs, no more and no less. A call outside what it declared is refused, and so is a declaration it never uses.
Publishing cannot escalate
Only someone who already holds every permission a page asks for can publish it. When a version adds write access, the other publishers are told by e-mail, Teams or Slack.
Your data stays yours
Fields a page creates belong to the CRM.
A field a Mini-app declares is an ordinary CRM field: it shows up in the CRM’s screens, filters, saved views, imports and reports like one made by hand. Archive the page and the data stays where it was. Nothing captured through a page is trapped in it.
Watched, not filed
Ventas notices when a page drifts.
Pages never run unattended, so what goes wrong is drift: a permission lost, a field changed, work assigned to someone who is not there.
Watched by
Sales
- A published page whose publisher has since lost a permission it relies on.
- A page that declares a field someone has since archived or changed in the CRM.
- Open work assigned to someone who has left.
- An activity in the coming week assigned to someone who is absent that day.
By design
Built to do one job well.
- One screen, one job: each Mini-app does a single thing well, and when a process needs a whole workflow, the product already has one.
- Text, number, date, yes/no and option-list fields — what a form needs — each one a CRM field you can filter, report on and import.
- On Windows and Linux, Mini-apps open in the web app, one click away.
Building from Claude Code?
A kit gives Claude the contract, a local harness with synthetic data under different roles, the same checker the app runs, and worked examples. Drafts go up with an API key.
Bring the screen you wish you had.
Tell us the form your team keeps in a spreadsheet. We will describe it to Claude on the call and open it inside a contact.