Small Business OS
Small Business OS connects your inbox, POS, CRM, accounting and spreadsheets, one workflow at a time. Orders land clean, invoices go out, and the week's numbers reach you on Monday morning. The first workflow goes live in five working days.
Proposed actionCreate the order in the POS, move delivery to the 11:15 slot, and send the client a confirmation.
Proposed actionAdd the $45 delivery fee from the signed quote and send the invoice.
Proposed actionSend the approved follow-up to all three, and remind Dana on Friday if there's still no reply.
Most owners can name the leak in one sentence. It's the same few places in almost every business that takes orders.
Each module is built on the tools you already use, such as Gmail or Outlook, Square, Toast or Shopify, QuickBooks or Xero, and your CRM. Anything customer-facing or financial waits for a person to approve it.
The order desk
Orders from email, phone, web forms and your POS become one clean record with the details checked. Conflicts, such as a double-booked delivery slot, are flagged before anyone confirms.
A person approvesNew orders that don't match the menu, price list or calendar.
Missed calls, quotes and payments
Missed calls get a text back and a booking link. Stale quotes get a follow-up. Unpaid invoices get reminders. Every touch is logged in the CRM, so nothing depends on someone remembering.
A person approvesThe templates, the timing, and anything outside the usual script.
Billing
Invoices are drafted from completed work and checked against the signed quote. Missing fees and mismatches are flagged before the invoice goes out.
A person approvesEvery invoice with a mismatch, and any credit or write-off.
The owner's view
One weekly view of orders, cash collected, open quotes and the leaks still open, in your inbox at 7 a.m. every Monday.
A person approvesWhich numbers matter. We set them with you in the first week.
Every module starts as one bounded workflow, delivered in five working days. The clock starts once access and the acceptance tests are agreed.
Walk through the workflow, its owner and its exceptions. Write the acceptance tests together.
Set up access to up to two systems, with the permissions you approve.
Build the smallest complete version that does the whole job.
Run it on your past cases, including the messy ones, and test the manual fallback.
Demo against the tests, train the team and hand over the runbook.
About two hours of your time across the week. Everything else is on us.
Before we build, we write the acceptance tests with you. If the workflow doesn't pass them, we keep working at no charge until it does.
Each step is useful on its own, and every fee is credited to the next one. Prices are on the pricing page.
A 20-minute call, then a one-page leak map within 48 hours. If nothing is worth fixing, we say so.
One workflow, up to two systems, fixed price, tested against your acceptance tests.
Three or four modules plus the dashboard, built over six to eight weeks.
Monitoring, tuning and one small change each cycle, billed every four weeks.
That's why we build inside the tools your team already uses: the inbox, the POS, the spreadsheet. Training is part of the sprint, and the handoff includes a written runbook.
Most is. Cleaning the records that one workflow depends on is part of the sprint. A full data cleanup is a separate, quoted project.
Plan on about two hours across five working days: a kickoff, a review of the tests, and the Friday handoff.
It can't send anything you haven't approved. Customer-facing messages use templates you sign off on, and anything outside them goes to a person first.
No. Accounts are in your name, the workflows are documented, and nothing runs on a platform we own. Ops Care is optional and month to month.
That's what the free leak check answers. We size the leak in hours or dollars before you spend anything, and we'll tell you if it isn't worth fixing.
Twenty minutes on a call, then a one-page map of where orders and money slip. It's free, and it's yours to keep either way.