When the tools you can buy don’t fit how your team works, I build the one that does, once I understand the problem and you have decided it is worth building.
What you are watching: Project Loire, a platform I built for a restaurant’s staff and management, in use. Its dishes, wines, cocktails and procedures. It is for restaurants; yours would be built for your problem. See the Project Loire page
This is real development. I only build what is worth it to your business, and I build it carefully.
What you get first: the Build Decision
Two weeks, and four sheets you keep, whatever you decide. Built for your problem, once I understand it. Here they are, filled in with what I found at a restaurant I worked at.
There is a lot to learn, and not much time to learn it.
An example, from the restaurant work. Your sheets would be about your business.1 of 4
What is worth changing, in order, and what leaving it costs
Keep every dish and wine in one record.Leaving it costs: Guests asked for a dish we had never offered. It had been on the website for months.
Print the menus from that record.Leaving it costs: The wine list, redone by hand every time a vintage changes.
Let the staff learn from it.Leaving it costs: A new team with a lot to learn and not much time to learn it.
An example, from the restaurant work. Your sheets would be about your business.2 of 4
How it would fit together
One record: every dish, wine, cocktail and spirit
What the staff learn from
The printed menus
The training sheets
A feed that can update your website
An example, from the restaurant work. Your sheets would be about your business.3 of 4
The price, or “don’t build this”
A fixed price you can sign.
The build’s price comes out of the Build Decision: one price for the whole build, in writing, before anything is built. I don’t quote a build before I understand it.
Don’t build this.
If what you need can be bought or fixed another way, you hear that instead, and you keep the map.
An example, from the restaurant work. Your sheets would be about your business.4 of 4
What you bring
What is prompting this, and whether there is a date behind it.
The tools, spreadsheets and systems you use today.
An example of where it went wrong.
Who is involved
You, and whoever signs off with you.
Whoever does the work today.
Someone on your team to try each part as it is built.
How every change is built
Six steps, in this order, for every change, big or small.
1
Scope first.
Written down before anything is built.
2
Read first, then the smallest change.
Reuse what works. Extras wait their turn.
3
Every change checked.
On a phone, empty, failing, and beside what it touches.
4
Your data first, and a separate review.
Who sees what, tested. Security reviewed on its own.
5
Nothing goes live without my sign-off.
Every time, not once.
6
A written record.
The same headings, every time.
The record’s headings: What changedWhyWhat it touchesHow it was testedHow to undo itWhat comes next
From the first call to the day it runs
1
The call
20 minutes
You bring
What is prompting this, and whether there is a date behind it.
The tools, spreadsheets and systems you use today.
Who signs off: you alone, or several people.
You get
A straight answer on whether it needs building at all.
2
The Build Decision
Two weeks
You bring
Time with you, and with whoever does the work today.
A look at the tools and records you use now.
You get
A map of how the work runs today.
The changes worth making, ranked, with what each costs you to leave alone.
How the system would hold your information, and how the parts fit.
A fixed price you can sign, or a plain “don’t build this”.
3
The build
A fixed price
You bring
Someone on your team to try each part and tell me what to change.
How I build
Scope first: what it does, who it changes things for and what it leaves out, written down before anything is built.
I read what is already there before I change it, and reuse what works.
The smallest change that does the job. Extras wait their turn.
Every change checked: on a phone, with nothing in it, when something fails, and next to whatever it touches.
Your data first: who can see and change what is set from the start, and tested for every role.
Anything that touches security or your data gets a separate review before it runs.
Nothing goes live without my sign-off.
A written record of every change: what changed, why, how to test it and how to undo it.
4
It runs
Looked after
You bring
Tell me what the team runs into.
You get
Fixes and changes, and someone watching who tells you.
Who it’s for
Teams that keep the same information in several places and retype it every time it changes, and owners who have outgrown the tools they can buy.
How it starts
A 20-minute call first. A build starts with the Build Decision. Running a restaurant that could pilot Project Loire? Say so in your message.