Sometimes somebody just has to build it.
Training gets a team to the point of knowing what is possible. Sometimes the honest next step is that a thing needs building, and nobody in the building has a spare week to build it.
That is this: the report, the check, the automation, built on the tools you already pay for and handed over working. It runs on your accounts and you own it outright.
Quoted per piece of work after a call, alongside a private engagement that starts at $5,000. There is no platform here and no licence to keep paying for: it runs in your accounts and it is yours.
I am not a software company. I am an operator who builds, which is why the first answer is usually that you already own something that does the job.
If you would rather see than read: the live demo is a week of a six-store group with the analysis running on it. Invented company, generated numbers, real arithmetic.
When building is the right answer
The task repeats and nobody owns it. Somebody rebuilds the same report every Monday. It is not hard, it is just never anyone’s actual job, so it eats the same two hours forever.
The data is already there and nobody can reach it. The POS holds two years of covers and the answer to next week’s schedule is inside it, but getting it out requires a step nobody has time to work out.
It has to survive a Friday. A thing a manager has to think about during a rush will not get used. Building it properly once is what makes it invisible enough to become habit.
Built on what you already pay for, handed over working, owned by you.
When it is not
Most of the time, honestly. Two-thirds of what operators ask me to build turns out to be something their existing software already does, or something one person on their team could do in an afternoon once somebody showed them how.
If that is your situation I will say so on the call, because selling you a build you did not need is the fastest way to make sure you never call again. The workshop is often the cheaper and better answer, and so is an hour on the phone at $500 before anybody commits to anything larger.
It is also not the answer when nobody has agreed what the thing is for. A build with no named owner and no number it is supposed to move becomes shelfware, and it is a more expensive kind of shelfware than a subscription.
How big these get
Most are small: one report, one check, one thing that stops being done by hand. Those are days.
Some are not. A place your team actually works out of - training and onboarding, documents, announcements people have to read, reporting that lines every store up the same way - is weeks, occasionally a few months. That is work I take, and I run it in stages so there is something usable at the end of each one.
What I am not is a software company selling you a product with your logo on it. Everything is built around how you already run, which is the part a software company cannot do and an operator can.
What handover means
It runs in your accounts, not mine. You get whatever it is written in, a one-page printout for whoever operates it, and a named person on your side who owns it.
No licence, no seat fee, no platform. If we never speak again it keeps running, and you are never paying me for permission to use it.
What I will not tell you is that it never needs attention. Anything that reads from another system eventually meets a vendor who changes something, a password that expires, or a report that moves. You will know what it costs to run before we start, and keeping it healthy afterwards is a set price you can take or leave.
The three tools on the site are the honest sample of this: built for real stores, and one of them runs in the page so you can see what it actually does rather than read about it.
More on working with a group
- Private AI training for restaurant groups
A day with your own team, on your own numbers.
- What a private engagement costs
From $5,000, and exactly what moves the number.
- Rolling out across multiple locations
When every GM has invented their own version.
- Bring someone in, or use the person you have?
Including when the answer is your own spreadsheet guy.
- Public workshops
The cheaper way in, if you have one or two to train.
Questions people actually ask
- What does 'implementation' actually mean here?
- Somebody builds the thing and hands it over working. The report that gets assembled every Monday, the variance check nobody has time to run, the prep list that lives in one chef's head. Not a platform, not a subscription: a thing that does a job you currently do by hand.
- How much does it cost?
- It is scoped and quoted per piece of work, after a call, because a one-page report and a rollout across fourteen stores are not comparable. A private engagement starts at $5,000 and building is quoted alongside it. You get the number in writing before anything starts.
- Do I need training as well?
- Usually the other way round. Most groups should do the session first and then find out how little needs building, because a team that understands the tools tends to build the easy two-thirds themselves.
- Who owns what you build?
- You do, outright. It runs in your accounts, in your tools, and you get everything it is written in. There is no licence and no seat fee, so you are never paying me for permission to use your own system. What you do pay for directly is whatever it runs on - the accounts are in your name, usually a few dollars a month to a hundred or so, and I tell you the number before we start.
- Does it keep working without you?
- Day to day, yes - nothing phones home to me. But anything that reads from another system can need attention eventually: a vendor changes how their system works, a password expires, somebody changes a report it reads. That is true of every integration anyone sells you. When it happens you can call me, call anyone, or fix it yourself, because you own the thing. I offer upkeep for a set price and plenty of clients never take it.
- Do we have to buy new software?
- Almost never, and I will tell you when the honest answer is yes. Most operators already pay for more than they use. If you own something that does the job, hearing that from me is worth more than being sold a second one.
- What if we already have someone technical?
- Then use them. Genuinely. If you have a person who is good with spreadsheets and has the time, the best value I can offer is a few hours briefing them rather than a build. I would rather do the small job well than the big one unnecessarily.
- How long does it take?
- A single report or check is usually days. A system several people use every shift - onboarding, documents, reporting across stores - runs weeks, and some run a few months. I take that work. It is built in stages with something usable at the end of each one, so you are never months in with nothing to look at.
Still deciding?
Take the free check first. Eight questions, no email, and you get the two things I’d fix in your building before I ask you for anything.