For teams that outgrew one-price-per-head

Maennche Studio

Your office runs Studio.
The floor runs your app.

Same operating system. Full Studio seats for the people who run the business. A branded Custom Portal, on the same records, for everyone else.

Book a demo →Walk through a floor job

★ Not a second product

Scroll

Is this your company?

This page is for operators who already have an office and a floor — not for a one-person shop starting free.

This is not for you if

✗You are a one-person shop. Start at maennche.com — Free, then a Business Seat.

✗You want a standalone time-clock or shift app. That is not Studio.

✗You want a one-off custom codebase you will own. This is still Studio, with a branded surface.

This is for you if

✓The office lives in deals, customers, inventory, and orders.

✓The floor lives in picking, packing, receiving, production, or a line of jobs that should not open the whole OS.

✓You would rather have one system with two kinds of access than a stack of apps glued together with email.

Two seats. One system.

The office gets Studio. The floor gets your app.

Permissions already distinguish Studio vs portal. The branded app is that distinction made visible.

Studio seat

Business Seat, $50/mo. Personal AI assistant, AI employees, CRM, proposals, phone and SMS, websites, full admin. For owners, office, sales, marketing, and ops leads — the people who run the business.

Floor app

Not a full Studio seat. Your brand, your domain, only the screens that job needs. Same customers, orders, inventory, and tickets. Native iOS and Android. No second database.

A day on the floor

What the floor person actually does

Not the whole CRM. The next job, on the same record the office already has open.

1
1
See my work
Today's orders, jobs, or tickets — not every customer in the company.
2
2
Do the next action
Pick, receive, update status, attach a photo. One screen, one job.
3
3
It hits the office instantly
Same record the office already had open. No export, no email, no second system.
4
4
Ask if stuck
Help desk from the same system, not a side channel.

Join the businesses already using Studio Custom Portals

Same operating system. Office on Studio. Floor on your app. Built so the whole team can work the records — without putting every head on a full Studio seat.

Book a demo

What is already true

One OS. Two surfaces.

Custom Portals

Your brand on the floor

The floor sees your name, not ours.

iOS + Android

Native apps

The floor lives on a phone. Studio is on the stores.

Set of records

Customers, orders, inventory, tickets — not a second database

Do not buy full Studio seats for the warehouse

Business Seats are $50/mo. Floor access is not a full Studio seat. There is no public catalog price for the floor — we scope it on the demo. This example is the math that makes mixed seating the point.

Setup	Everyone on Studio seats	Mixed seating
10 office people	10 × $50 = $500	$500 for the operating environment
40 floor people	40 × $50 = $2,000 they will never use	Not full Studio seats — scoped on the demo
What you buy	A second product, or 50 full seats	One OS. Two kinds of access.
	$2,500/mo	Office on $50 seats; floor is not a Business Seat

Why not the alternative

Not a custom codebase.

A custom shop leaves you owning software. Studio Custom Portals stay on the OS.

</>

Custom app shop

You own a codebase. You are responsible to maintain security & maintenance updates. AI is a chatbot you glue on.

Studio Custom Portals

One OS. Office gets the whole environment. Floor gets a branded job surface. One permission model. AI on the records — not a second brain.

On the floor app

What ships

Your name on the app. Only the screens that role needs. Same records as the office.

Your brand and domain

The floor does not see "Maennche" as the product. They see your name.

Scoped screens

Team-scoped menus. The warehouse does not get the whole CRM.

Same records

Customers, orders, inventory, tickets — the office already has them.

iOS and Android

Browser works. Native apps exist if the floor lives on a phone.

Help desk, same system

Stuck? Ticket from here. Not a side channel.

AI stays on the office side

AI employees work the records. Floor portal users do not get a $50 AI Team seat by walking in.

How it happens

Office first. Floor jobs mapped. Portal access.

We do not start a greenfield app. We map the floor onto objects you already run.

1
1
Office is on Studio
Or we start there. That is the operating environment.
2
2
Map the floor jobs
Screens on the same objects — not a separate product.
3
3
Portal access, not a Business Seat
Floor people get the job surface. They do not get a $50 seat they will not use.
4
4
Brand, domain, mobile
Iterate in Studio. Not a deploy of a separate repo for every customer.

FAQ

Straight answers

Put the office on Studio. Put the floor on your app.

Same records. Two kinds of access. Book a walkthrough with a real floor job, not a slide deck.