A plugin for Claude
Your team builds its own apps with Claude. Steadyship is the engineer working beside them, always: it asks what they don't know to ask, judges what they can't judge, and brings in real engineering the moment an app starts to matter. Not before.
Open source. Stays on your computer. Keeps working if you remove it.
Claude builds what it is asked to build. These are the three things nobody in the building was there to add.
Before a change is built, it has read your business notes, your other apps and your spreadsheets. So it asks the one or two questions that would be expensive to get wrong, recommends an answer, and builds once you decide.
You say "Make the job board track hours." It asks: against the whole job, or each step? And isn't that already in Hours.csv on the shared drive?
A straight Yes, No or Not yet on whether the team can rely on an app, with the evidence. Security in plain words: who can see this, where what people type ends up, whether a password is sitting in a file.
It never calls an app secure. It says what it checked, and labels what it could not.
A prototype stays a prototype. The day someone relies on it, it gets one master for its data, a backup, a test, a named owner and its decisions written down, each step with one plain line on why. The apps stop drifting apart.
A one-person tool gets no ceremony. The day the workshop runs on it, it gets looked after like software.
Each one is a plain sentence in Claude. No dashboard, no account, nothing to learn. Everything it finds goes into files you keep.
The one or two questions that would be expensive to get wrong, with a recommendation. You decide, it builds, and it writes down why.
Yes, No or Not yet on whether the team can rely on an app, with the evidence. A second reviewer checks the first.
Reads every app and every spreadsheet and shows where a price, a job or a name is in two places and already disagrees.
Can it reach GitHub, read and write the shared drive, open your app? One minute, PASS or FAIL, written down.
Prototype, owned tool, proper app, platform. It says which stage an app is at and moves it one step at a time, with you deciding at each.
A shared glossary with a human owner. Every app reading the same spreadsheets instead of its own copy.
A reviewer from a different AI vendor, so it does not share the builder's blind spots. No terminal needed.
Ordinary files in a private folder the business owns. Remove it tomorrow and everything it wrote is still there.
Three sentences on day one. After that, ask for changes the way you already do.
“Set up Steadyship for Harbour Boatworks”
Answer four questions. About two minutes.
“Check this computer”
Three checks, one minute, recorded.
“Review the job board”
A verdict the owner can act on.
A real reply from the demo business, a boat builder with six apps its staff built with Claude. The short version is what you read. The full picture, every row that differs, goes into a file you keep.
Try it on the demo businessThe three things that matter most
What I'd do first
Update the Quote Builder's two prices, and make it read Price List 2026.csv. It is the one customers see numbers from.
The full picture is in docs/assessment/SUMMARY.md. Say ‘show me everything’ and I'll put it here.
Every app is at one of four stages. Steadyship says which, what would move it on, and does the moving one step at a time with a review at each step. Nobody has to choose a framework, a database or a host. It makes the call, gives the reason, and you can defer.
One file, one person's tool.
Moves on when someone else starts using it.
Shared, backed-up data with one writer. A test. A named owner.
Moves on when two apps touch the same information.
A real framework, shared parts, data checked on the way in.
Moves on when the business depends on it daily.
Several apps on one database, kept in step.
Moves on when they must stay consistent for the business to run.
Always there, never in the way. Exploring? Prototype as you do today; it asks at most once and never blocks. Keeping it? It gets a name, an owner and a first verdict. Relying on it? The stages run, with you deciding at each. Short answers, with more if you ask.
How each step worksA business where a few people who are not developers build their own tools with Claude, and those tools are starting to matter. A job board someone relies on. A quote builder that disagrees with the price list. Two apps that both keep the customer list.
One person does a ten-minute setup. The owner decides what the business relies on. Everyone else keeps building, with an engineer in the conversation.
Windows or Mac, the Claude desktop app or Claude Code in a terminal. One page for each.