Custom software for small businesses.

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.

Tell me what you’re working onThe first call is 20 minutes.

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.

  1. How the work runs today
  2. What is worth changing, in order, and what leaving it costs
  3. How it would fit together
  4. The price, or “don’t build this”

How the work runs today

A vintage changes.
The wine list is redone by hand, every time.
A dish comes off the menu.
It stays on the website for months.
The restaurant opens.
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

  1. 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.
  2. Print the menus from that record.Leaving it costs: The wine list, redone by hand every time a vintage changes.
  3. 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

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.

Tell me what you’re working on

Goes well with

Every service