The first time
00.00sIt doesn't know your process yet.
The simplest way to build, manage and share business apps in and for your agent sessions.
WHICH ONE ARE YOU?
I USE SOFTWARE My work is spread across other people's software. New clients, purchase requests, invoice approvals — the process lives in four apps and one person's head. That's me I OFFER SOFTWARE My customers are already pointing agents at my product. Each of them wiring it up alone, with a key that can do everything, and your support queue absorbing the difference. That's me
01 · YOUR STACK
Which of these does the work happen in?
Pick at least two. Most companies run on more than they think.
01 · YOUR SURFACE
What does your product already expose?
Pick whichever you have. Whatever is there is what an agent will find.
02 · WHAT YOUR ASSISTANT GETS HANDED
0
Illustrative counts, from the systems you picked.
03 · THE ONE THAT COSTS YOU MOST
If it only learned one of these, which?
The one you get asked about every week.
03 · WHAT THEY ASK FOR MOST
What do your customers automate first?
The thing your support queue already answers.
04 · THE RACE
Same request. Watch the gap.
Both get the same job, across the systems you picked.
Every time after
00.00sOne call. Your steps. In order.
Illustrative pacing, not a benchmark. The systems and the order are yours.
05 · THE RULE
Who may run it?
This is the part an API key cannot answer.
05 · THE RULE
Who may install it?
This is the part an API key cannot answer.
06 · WHAT YOU TOLD US
That is one afternoon's work.
Your answers stay in this browser — none of them are sent anywhere. We count which door people pick and how far they get, nothing more. How that works.
07 · EVERY CALL, WRITTEN DOWN
You can see what it did.
Who ran it, against which account, and how it ended.
ACTIVITY live
08 · HANDING IT ON
Who else should get this?
Publishing sends the shape, never a key.
08 · HANDING IT ON
Who may install it?
Publishing sends the shape, never a key.
09 · THAT IS THE WHOLE THING
Built once. Handed to anyone.
Your answers stayed in this browser — every one of them. The 90% is the decisions, and you just made all of them.
Inline speaks to all tools, so your agents use apps.
Your assistant doesn't need more tools.
It needs the right one. Connect the systems you already run on and it is handed every action in all of them, with no idea which four you meant.
ACTIONS YOUR ASSISTANT IS HANDED
970
WHAT IT ACTUALLY NEEDS
new_client_onboarding(client)
AND THIS IS THE PART NOBODY BELIEVES
The app opens inside the conversation.
Not a link out to a dashboard. A real screen — the fields that matter, one button — right there in the chat, built from the process you taught it.
Gmail Notion Drive Asana one app
CONNECTED TO INLINE
Set up Northwind as a new client — standard plan, Maya owns it.
You have an app for that. Here it is — check the details and run it.
new_client_onboarding running
CLIENT Northwind Ltd
OWNER maya@yourcompany.com
PLAN Standard — monthly
SET THEM UP
- 01 Drive created the client folder
- 02 Notion added their page to the CRM
- 03 Gmail sent the welcome email
- 04 Asana started the onboarding checklist
Northwind is set up. Folder, CRM page, welcome email and checklist — all four, in that order.
The tool works in any MCP client. The screen appears wherever the host supports MCP Apps — everywhere else the same tool runs and asks for what it needs in words.
DISTRIBUTION
Built once. Handed to anyone.
Publish a process and another team — or another company — installs it. What travels is the shape: the steps, their order, and the point where a human has to look. Not a single credential.
new-client-setupv3
- Stripe your account
- Asana your account
- Gmail your account
new-client-setupv3
- Stripe their account
- Asana their account
- Gmail their account
No key changes hands. They connect their own accounts, the same way you connected yours. If they stop using it, they disconnect their own sources — there is nothing of yours to take back.
Start with one process.
The one everybody asks you about. It takes an afternoon.