Try it before talking to me

Business CRM — claims practice

Seven live cases — kitchen fire, water damage, storm roof damage, vandalism — with their stakeholders, documents, deadlines and financial tracking. Messaging is built in: emails land in the case, not in a separate inbox. Kanban board, assigned tasks, reminders, notifications, action log.

Three profiles offered at login — case manager, lawyer, administrator — to see how permissions differ. Fictional data, **reset every night at 02:00**: nothing to risk.

SaaS core — where a product starts

What you need before writing your product’s first feature: client accounts via login link, a separate back office, subscriptions and invoicing, transactional emails, support tickets, and a client area in three languages. The kind of core that takes months when discovered along the way.

Payments in test mode — nothing is charged.

Question your documents, without sending them out

Drop in a PDF, a Word file, a PowerPoint or plain text, then ask your questions in ordinary language: the tool answers from the document’s actual content, not from what a model believes it knows. It is the concrete answer to the question every director has about AI — the one not asked loudly enough before dropping a contract into an online service.

The demo account is shown on the page, and a button fills it in. Document indexing runs on a machine of mine: nothing is sent to an outside service to be indexed.

Agent cockpit — three ways to steer

Give an instruction in plain language, follow the agent step by step, collect the result. Three built-in modes: **Screen** (parked — chat and tables on the desk), **Remote** (phone commands by voice, results show on the PC), **Drive** (in the car — short spoken answers, no tables while you drive).

Public playground: pre-filled credentials, fictional data. **Automatic restore every night at 02:00** — break whatever you like. Wiring it to your systems is done together, on a bounded scope.