Wayist — Mini apps
MINI APPS

Ask for the tool. It exists by the afternoon.

Describe the internal tool you need in a conversation and an agent builds it over your own bases, then publishes it privately to the workspace. No repository, no deploy, no ticket.

Get started free See pricing
Gaia· #ops stream
We need a board for supplier claims. Status, amount, who owns it, and flag anything older than 14 days.
BUILT FROM SUPPLIER CLAIMS · 3 VIEWS
Supplier claimsboard · aged flag at 14 days · 2 editors
OpenPublish to workspace
Add a column for the contract reference.

Describe it instead of specifying it

The brief is a sentence in a stream. The agent reads your bases, picks the fields it needs, builds the views and shows you the result — then changes it when you reply.

Built over live records, so the app and the data cannot drift apart
Iterate by replying: the next message changes the app
Published privately to the workspace in one click
Anyone can build one, not just the person who can code

Small tools kept like documents

Mini apps sit in folders with an owner, a modified date and a history. They are not shadow IT — they live inside the same permissions as everything else, and an app cannot reach past what its user already can.

Folders, ownership, rename, move and a bin
Bounded by the same authority matrix as its user and its agent
Install from the skill market when someone has already built it
Mini appsMy mini apps · 9
Supplier claims
built by Gaia · used daily
Visit planner
built by Owen · used weekly
Burn tracker
built by Kate · used monthly
+ Describe a new one
Skill market · 40+ installable skills and apps

How mini apps behave

Built by conversation

No repository, no build step, no ticket in someone else's backlog.

Live over bases

The app reads and writes the same rows your team works in.

Folders and ownership

Organised like files, with a history and someone responsible.

Skill market

Install what has already been built instead of describing it again.

Same permissions

A mini app cannot see past what its user and its agent already can.

Published privately

Shared inside the workspace, not on the internet.

Gaiathinking · 11sStop
Owen: add a contract reference and group by supplier
✓ Read the Supplier claims app
✓ Found contract ref on 📇 suppliers base
✓ Added the column and the grouping
◌ Rebuilding the board view
Published to the workspace once a person approves it.

The agent keeps building after the first version

A mini app is never finished in one message. Ask for a change and the agent reads the app, the base behind it and what people actually use, then rebuilds and shows you the difference.

Change it by replying, not by reopening a brief
The agent explains what it changed and why
Versions kept, so you can go back to the one that worked
IN THE BOX
Build by describing
Build from a base
Iterate in conversation
Folders and colours
Rename, move and delete
Owner and modified date
Publish to the workspace
Install from the skill market
Agent-built apps
Per-app permissions
Runs on live records
No deploy step

Common questions

Do I need a developer?

No. The brief is a sentence. A developer can extend it later through the API, but nothing about building one requires code.

Can an agent build one on its own?

Yes, within its authority, and the result arrives as a draft for a person to publish.

What happens if the base changes?

The app follows it — it reads the base rather than a copy, so a new column is available immediately and a removed one is flagged.

WORKS WITH
Omnichannel inbox Team collaboration Video calls & recordings Bases Agents & authority Team mail and calendars Data warehouse Analytics Docs, decks & drive

Describe the tool your team keeps asking for

One sentence in a stream, one agent, and the thing exists before the afternoon is over.

Get started free Compare plans