A portal for your clients, from a spec

Many small businesses end up with the same need: a place where their clients sign in and see their own things. An appointment, a job in progress, a document to sign, an invoice, a message. A website cannot do that, and a custom app is too much.

A Geenius MVP web app is a site with a spec.

Kits, not code#

A web app is made of kits. Members gives sign-in by e-mail code or magic link, with sessions per device, rate limits and lockout. Records gives your own entities. Booking, jobs, memberships, tickets, reviews and rewards are service-business kits; portal, matters, appointments, documents, invoices and messages are the client-portal kits. Twenty-eight kits are built, and four shop kits are not.

A starting point#

There are twenty-two web-app starting points: a member portal, a salon, a studio, a repair shop, a trades business, a clinic portal, a tax advisor, an agency and more. You start from one and patch the spec. Your AI can do that, and every problem it makes comes back with a JSON path, so it can fix itself.

Members are not accounts of ours#

The members of a web app are the app's own people, your clients and customers. They are not Geenius OS accounts. They sign in with an e-mail code, and you can export everything kept about a member or erase them with their records.

Cautions#

Two cautions are repeated on the starting points that need them. The deployment runs in the United States, so for law, health and tax starting points use fictional data only until an EU region exists. And legal texts are templates, not legal advice. Some portal kits also read Geenius OS tools (Contacts, Matters, Bookings, Invoices, Files) which the standalone app does not reach yet.

Try it with fictional data#

A client portal can be loaded with fictional demo data, and cleared again with one action, so you can see it work before a real client does.

See web apps and kits.