A plugin for Claude

An engineer in the conversation.

Your team builds its own apps with Claude. Steadyship is the engineer sitting beside them. It asks the questions nobody thought to ask, tells you honestly whether an app is good enough to rely on, and only starts adding proper engineering once something actually matters.

Get started See what it does

Open source, and it all stays on your computer. If you remove it, everything it wrote is still there.

What an engineer brings

Claude builds whatever it is asked to build. What is usually missing is someone who has seen a few of these go wrong.

Asks what you don't know to ask

By the time you ask for a change it has already read your business notes, your other apps and your spreadsheets. If there is a question that would be expensive to get wrong, it asks it, suggests an answer, and builds once you decide. Usually that is one question. It is never a questionnaire.

You say "Make the job board track hours." It asks whether hours go against the whole job or each step, and points out that Hours.csv on the shared drive already has some of them.

Judges what you can't judge

Ask whether the team can rely on an app and the first line is Yes, No or Not yet, followed by the evidence. It also covers the security questions most people don't think to ask: who can see this, where what people type ends up, whether a password is sitting in a file.

It won't tell you an app is secure. It tells you what it checked, and is clear about what it couldn't.

Brings engineering when it's needed, not before

While an app is one person's experiment, it is left alone. Once other people start relying on it, Steadyship gives it the things software needs to be relied on: its data in one shared, backed-up place, a test, a named owner, and a record of why decisions were made. Each addition comes with a sentence on why it is worth having.

So a one-person tool stays quick and simple, and the app the workshop runs on gets looked after properly.

What it does

You type a sentence in Claude. There is no dashboard or account to set up, and whatever it finds is written into files you keep.

Asks before it builds

If a change would be expensive to get wrong, it asks about it first and suggests an answer. Once you decide, it builds, and records why.

Gives a straight verdict

Yes, No or Not yet on whether the team can rely on an app, with the evidence. A second, independent reviewer checks the first one's work.

Finds the same thing kept twice

It reads every app and every spreadsheet, and shows you where the same price, job or customer is kept in two places and already disagrees.

Checks the ground first

Before anything is built, it checks that it can reach GitHub, read and write the shared drive, and open one of your apps. It takes a minute, and the result is recorded.

A path forward, not a rebuild

Every app is at one of four stages, from prototype to platform. It tells you which, and moves an app one step at a time, with you deciding at each step.

Apps that stay in step

A shared glossary that someone in the business owns, and every app reading the same spreadsheets instead of keeping its own copy.

A second opinion from another vendor

If you want the strongest check, the review can go to a model from a different company, which won't share the blind spots of the one that built it.

Everything stays yours

Ordinary files in a private folder the business owns. If you remove Steadyship tomorrow, everything it wrote is still there and still useful.

All of it, in more detail·Tell us which one you'd want first

How it works

Three sentences on the first day. After that you ask for changes the way you already do.

1
“Set up Steadyship for Harbour Boatworks”
Four questions, about two minutes.
2
“Check this computer”
Three checks in about a minute, all recorded.
3
“Review the job board”
A verdict the owner can act on.

See it answer

This is a real reply, from the demo business that ships with Steadyship: a boat builder with six apps its staff built with Claude. You read the short version. The full picture, with every row that differs, goes into a file you keep.

Try it on the demo business

What apps do we have and where is the same information kept twice?

The three things that matter most

The Quote Builder is using old prices. Price List 2026.csv has Bimini top $3,450 and Trailer $6,250. The app has $3,200 and $5,800, so a quote with both is $700 low before GST.
The job list is typed into several places, and they disagree. Jobs.csv has 8 jobs. Job Board has 8, Delivery Checklist 4 and Shop Timer 3. J-1039 is “Sea trial” in Jobs.csv but “Paint” on the board.
If a laptop died, most of the work would be lost. Five apps keep what people enter only in that browser on that computer.

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.

From prototype to something the business runs on

Every app is at one of four stages. Steadyship tells you which, what would move it on, and does the moving one step at a time with a review at each step. Nobody in the business has to pick a framework, a database or a host. When it thinks the time has come, it says so and explains why, and you can always say "not yet".

Stage 1
Prototype
One file, one person's tool.
Moves on when someone else starts using it.
Stage 2
Owned tool
Shared, backed-up data, a test and a named owner.
Moves on when two apps touch the same information.
Stage 3
Proper app
A real framework, shared parts, data checked on the way in.
Moves on when the business depends on it daily.
Stage 4
Platform
Several apps on one database, kept in step.
Moves on when they must stay consistent for the business to run.

It stays out of the way. While you are experimenting it leaves you alone, apart from the occasional question. When you decide to keep something, it gets a name, an owner and a first verdict. Only when people start relying on it does the real work begin, and even then its answers fit on one screen, with more if you ask.

How each step works

Who it's for

Businesses where a few people who are not developers build their own tools with Claude, and those tools are starting to matter: a job board the workshop relies on, a quote builder that disagrees with the price list, two apps that both keep the customer list.

We are building it alongside a New Zealand boat builder whose staff did exactly that. One person does a ten-minute setup, the owner decides what the business relies on, and everyone else keeps building.

What it is not

It doesn't host your apps and it isn't a database.
It doesn't replace Claude. It sits in the same chat.
It isn't a certificate that an app is secure. It tells you what it checked and what it couldn't.
It doesn't nag. It stays quiet until something matters.

Ten minutes to a first verdict.

There is a page for each setup: Windows or Mac, the Claude desktop app or Claude Code.

Get started Tell us what you'd want first