Software

The small system the spreadsheet became

We build the small systems a company actually needs and cannot buy cleanly: a join between Microsoft 365 and the thing you already run, an internal tool, a replacement for a spreadsheet that has become load-bearing. We are not a product studio, and this page will not pretend we are.

What we take on

A conversation about the job the spreadsheet is doing, before anyone talks about a rebuild
Internal tools for the people who will use them, with a screen a person can understand
Joins between Microsoft 365 and the finance system, the phones, or the database you already have
A written note of what the thing does, how it is hosted, and who can change it
Care of it afterwards, if you want the same people to pick up the phone

What we will not pretend

We will not pitch an app because an app sounds modern
We will not take on a product you hope to sell to the world. That is a different kind of company
We will not leave the only copy of the work on one laptop

In practice

Most of this work is integration. The data already exists, in a mailbox, a SharePoint list, or a system someone bought years ago. The useful job is moving it without a person retyping it, and showing it somewhere the team already opens.

When a spreadsheet has become load-bearing, the risk is not the grid. It is that one person understands it, and the file has six names ending in final. We replace that when the cost of being wrong is higher than the cost of the small system. Sometimes the right answer is a better spreadsheet, with an owner. We will say that too.

We host what we build so it can be backed up and handed over. If we part company, you keep the work.

If the tool signs people in, it should use the Microsoft accounts you already have, not a fresh password on a monitor.

Talk about software