Built by operators

We built this in a
kitchen and on a
job site.

One operations platform, two industries. Both versions were built next to the people who use them — line cooks and installers, not a product committee.

Built alongside a seven-location pizza brand and a $10M window-coverings company — operators running real businesses, every day.

One company, two industries

Same engine.
Two very different days.

A restaurant runs on food cost, labor, and what happened on the closing shift. A contractor runs on the job — the quote, the signature, the install, the invoice. We didn't force one product to pretend it understands both.

Why this exists

Most software is written by people who've never worked a Friday night.

The people who run MarginGains run the businesses it's built for — restaurants on one side, home services on the other. Both sets of problems. Both sets of 9 p.m. paperwork. Every module exists because somebody here needed it on a Tuesday and couldn't buy it.

Which is why we only ask two questions of anything we build: does it put margin back in your business, or does it give you time back? Anything that does neither doesn't ship.

To the penny
Recipe and quote math checked against real vendor invoices, not estimates. The number your team sees is the number the vendor bills.
$1,200 a month
What our A.I. receptionist replaced at one of our own companies — an answering service that still managed to miss calls.
Nine lessons
Training videos we produced from a customer's own kitchen footage — edited, scored, and quizzed. We make the videos, too.
Underneath both

One platform, shared.

Whichever industry you're in, the same spine runs underneath — and every A.I. feature has a plain, deterministic fallback, so nothing ever shows your team an error screen.

01
The morning brief
Three things that need attention today, written from your own numbers — not a dashboard you have to interpret.
02
The A.I. receptionist
Answers 24/7, books and reschedules, trained on your services and prices. Nights, weekends, overflow.
03
Training that ships
Your team films it, we produce it, it publishes to your library with a knowledge check on every lesson.
04
Support, two lanes
Your customers to you, and you to us. Every question becomes a ticket with an owner and an answer.
The demo you don't have to book

Don't take our word for it.
Call it right now.

Two phone numbers. Two completely different businesses. The same A.I. receptionist underneath, trained on each one. Pick up your phone and interview it.

The restaurant
Ask about hours, try to place an order, or ask whether something has nuts in it. It answers like a restaurant, because that's what it was trained on.
The home services shop
Try to book an estimate, or ask what it costs to come out. Same product — a completely different brain.

Both are demo businesses we invented, not customers — we'd never put a client's menu or pricing behind a public number. The chat bubble in the corner is our own product too, pointed at our own business.

Pricing

Priced per location.
Never per person.

Unlimited users on every plan — add a dispatcher, a second manager, the whole closing crew, and the bill doesn't move. Month-to-month, no contracts, no setup fees.

Next step

Thirty minutes, the real product, no slides.

We'll open the actual app and run your workflow — your menu, or your job. If it doesn't fit, we'll tell you.