stacketr · How it works
Install it.
Describe your business.
It runs.
Three steps, and the system takes the shape of your business. Here's what each one looks like.
01 — Setup
Two commands, one question.
There's no signup and no account. The installer puts one file on your machine and checks it against the published checksum. Then it asks for your business's name — and that's the entire setup.
02 — Your business, described
One document says
what your business is.
What you sell, your prices, your locations, your rules — and crucially, what needs your approval and what doesn't. It lives in one readable document inside the folder. Change a price, add a location, tighten a rule: edit the document and the system follows. There is no developer in that loop and no migration project when the business changes. The document is version controlled — every edit is a version you can inspect, diff, and roll back.
03 — Everything is recorded
Ask it anything.
Get an answer, not an export.
Every sale, every stock movement, every approval, every change — one record, in order, forever. "What did we sell last Tuesday?" "Who approved this refund?" "When did this price change?" You ask, it answers. And because there's one set of books, the register, the stockroom, and the accountant never disagree.
04 — Routine and judgment
The routine happens.
The calls wait for you.
Nightly counts, daily totals, restock drafts, follow-ups. These just happen — on schedule, written down, no supervision needed.
Refunds, price changes, spending, anything a customer will see. Each one lands on your phone as a yes/no — approve or refuse in one tap, from anywhere.
05 — Backup and recovery
The backup plan is
copying a folder.
The whole business is one folder, so protecting it is not an IT project. Keep a copy on a drive you own — or let the system mirror itself to one continuously. Attach that copy to any machine and the business is back, exactly as it was. New computer? Move the folder. That's the entire procedure.
06 — Modular
Add a skill.
The system grows.
Capabilities ship as signed, versioned modules. Install one and its types, screens, and permissions join the system — the console, the app, and every agent see them at once. Remove one and it leaves cleanly. The system and its modules version together, so the whole thing is always one coherent, checkable unit.