On-site setup
La Mise au Carré
Getting operations in order.
Give us what you have, we hand back Tsuno up and running, on site, and we leave once it runs in front of us. Delivered by restaurant operators who use their own system.
The trigger
You don’t call about software. You call because you’ve had enough.
The real criterion isn’t the size of your group. It’s the pain. You have said at least one of these:
- “If I’m not there, nothing works.”
- “I repeat the same thing to every new hire.”
- “I can’t take a vacation.”
For a group of 3 to 5 restaurants, or a single site. We only show you Tsuno once we’ve heard your problem.
The Kajirō story
It happened to us.
We sell what we use.
Kajirō is our own restaurant group. We closed a restaurant there for lack of written processes.
Our first training handbook? Duplicates, unfinished pages, and nobody to read it. So we changed the order: checklists first. That is the method we still use at home, and the one we come and set up at yours.
Delivered pre-filled
We start from what you already have.
Documents, photos, spreadsheets, procedures: we pull out the content, a person validates every sensitive match, then everything is imported and reviewed on the floor. AI proposes, a person decides.
The chain
Six links. Each one sets up the next.
We don’t start with a handbook nobody opens. We start with checklists, and the chain ends where it shows up in the books.
-
Checklists
The whole day, from opening to closing, by station.
We write the typical day, then adapt it: fish delivery day, Friday, Saturday. For each task, the station, the duration, the time the result must be ready. The checklist then shows what knowledge is needed.
-
Task timing
We time tasks, not people.
Task durations and deadlines give you how many people you need and when they arrive. No more staffing “just to be safe.”
Teaching example
A 45-minute block must be ready at 10 am: the person arrives at 9:15. Two blocks ready at 10 am, one taking 1:15, the other 2 hours, with a 9 am start: you need two people, or an earlier start.
-
Skills
Mapping what gets passed on, in detail.
“You cut the fish” means nothing: whole fish to fillet, fillet to saku, saku to slices. Not everyone can do all three. A skill is a dated fact, never a rating of the person.
Rather than blaming the employee, we turn it into process, training and skills.
-
The schedule
Built from tasks and times, not gut feeling.
It goes into the kiosk, a shared tablet in the kitchen or dining room that the team opens every morning. The kiosk only shows published shifts: what you see is what was decided.
-
Labor cost
The link that shows up in the books.
Staffing built from tasks can be compared with what you actually pay. Cutting staffing without hurting service is impossible without a way to measure.
No figure promised: we only publish one with its written measurement protocol.
-
On-site setup
We train in front of you and stay until it runs.
The job doesn’t end with a report. It ends with a system your team opens every morning, running in front of us.
The eye
We industrialize data collection. Not judgment.
The value is an operator’s eye: the sub-skill nobody named, the staffing kept just to be safe. That’s why we come. Tsuno connects the facts. People decide.
What Tsuno refusesThe workload
On site, for as long as it takes.
No duration announced up front: it depends on what you already have, the size of the group and your team’s availability. We set the calendar together, after seeing your material.
-
Pre-fill and collection
Your documents extracted and validated, then checklists, task timing and skills observed during real service.
-
The build
Schedule, labor cost, the tool configured and opened every morning by the team.
-
Making it stick
We stay until it runs in front of us, then a 30-day review.
Honest caveat: at a client’s, it isn’t the task that takes time. It’s the client.
What we refuse
We say no before, not after.
The worst case isn’t the unhappy client. It’s the disorganized client who soaks up all the time and never provides the material.
-
No point person, no engagement
Someone has to own the project on your side. Without them, we install into thin air.
-
No half day, no engagement
Discovery with the owner is not a formality: it’s where we see whether the problem is the right one.
-
No pre-sale site visits
We sell the end of depending on physical presence. Field work starts after signing.
-
No custom Tsuno
No client-specific development, no fork. A need becomes a setting, a generic module or an add-on.
On the product side, Tsuno ranks no one, automates no sanction and never guesses motivation or mood. Every product refusal
Frequently asked questions
Is La Mise au Carré right for us?
It is built for a group of 3 to 5 restaurants, though a single site works too. You are still hands-on in operations, your site managers carry the day to day, and you can free up the budget. Above all, the problem is wearing you out: without stated pain, the tool looks like overkill.
Why don’t you visit before the sale?
It isn’t a scheduling issue. We sell the end of depending on physical presence: if we had to travel to convince you, we would prove the opposite. Qualification and demo happen by video call, in an isolated demo environment, then e-signature. Field work starts after.
How long does the engagement last?
No duration is announced up front. Starting from your documents lightens collection, and the trial with three non-sensitive operational documents (recipe, procedure, checklist, anonymized schedule) lets you check that before any commitment. We set the calendar together.
What do you bring on site?
What is needed: travel, lodging, and equipment depending on what you already own, for example shared tablets for the kiosk, where the team checks off and flags.
What does Tsuno refuse on the product side?
No employee ranking or overall score of a person, no resignation prediction or firing recommendation, no automatic sanctions, no inference of motivation, honesty, loyalty or mood. When data is missing, Tsuno says so instead of making it up. The details are on the Trust page.
How are deliverables approved?
Approval terms are set in the commercial proposal.
We look at your problem, not a demo.
Send three documents you already have. We build an isolated environment, walk you through it in a meeting, then delete it on the agreed date.
Non-sensitive operational documents only: no personal data, no HR documents, anonymized schedules.