Product · Build by chat
Ask for the module you’re missing. Alori builds it.
Renewals, onboarding, inspections, commissions: say what you need, the way you’d tell a colleague. Alori builds it into your app, on the customers and data you already have. No developer, no new subscription.
Add a Renewals module: each client’s contract, its renewal date and amount. Remind me 30 days before.
- Added Renewals to the menu
- Linked each renewal to its client
- Reminder 30 days before
- Preview ready
| Client | Renews | Amount |
|---|---|---|
| Northwind Studio | Nov 28 | $4,800 |
| Hart Accounting | Dec 15 | $2,400 |
| Pine & Co. | Jan 9 | $9,600 |
| Lumen Labs | Feb 2 | $1,200 |
Ask, try, publish.
Every change works the same way, from one new field to a whole new module.
- 01
Ask in plain words
Type what you need in the chat, in English or French. No forms to fill, no settings to learn.
- 02
Try it in the preview
The new module shows up in your preview with your real customers. Click around, then ask for changes until it’s right.
- 03
Publish when it’s right
Your team keeps the screens they know until you click Publish. Changed your mind? Go back to an earlier version from History.
What owners ask for.
“Add a Renewals module, with a reminder 30 days before each one.”
“Track each new client’s onboarding with a checklist the team ticks off.”
“Show what each salesperson sold this month, and their commission.”
“A warranty claim form on my website that lands in a list for the office.”
“Quotes over $5,000 need my approval before they go out.”
“Add the renewal date to each client.”
Built into your app, not bolted on.
- 01
Same customers, same data
A new module uses the customers, deals and invoices you already have. Nothing to sync, nothing to import twice.
- 02
Your AI team uses it too
Ask Alori and your bots read and fill the new lists: “Add a renewal for Northwind, $4,800, next March.”
- 03
Nothing breaks for your team
Changes wait in the preview until you publish, and every published version can be brought back.
- 04
You pay per change
One credit is one change. Bigger changes use more, and a change that fails or changes nothing is refunded.
Questions
Another question? Ask it when you start.
No. You describe what you want in plain words. Alori writes the code, checks that it works and shows you the result in the preview.
A new field, a rule, a page, or a whole module with its list, its record page and its reminders. You can also add a separate project with its own address, like a client portal, on the same data.
Each change uses credits: one for a small change, more for a big one. A change that fails or changes nothing is refunded. Paid plans include credits every month, and you can add more anytime.
Ask for a fix in the same chat, or go back to an earlier version from History. Your team only sees a change once you publish it.
Yes. Going back to an earlier version changes the screens, not your data: your customers, deals and invoices stay as they are.
Yes. An Alori partner can build your modules and look after your app for you.