Workflows
The line runs idea, spec, build, and release. A gate inspects the work before it moves. You pass it, or a fresh session does.
Build a startup
in a weekend.
Shipforward is a factory for the idea. Workflows move it down the line, agents do the jobs, and the session that wrote the work can’t pass the gate.
A weekend is enough for a link a customer can open. Start any day. After the gates, the line can keep running overnight.
The factory behind the idea.
You stay with the product. The line already knows the rest.
Agents
Research, backend, frontend, database, security, performance, and review. The gatekeeper didn’t write the code, so it can pass the work the author can’t.
Skills
Sign-in, Stripe billing, who can read a row, screens, tests, and the launch page. They’re in the package on day one.
The idea moves down the line.
A new product takes the full line. A bug takes a shorter one. A prototype, a mockup, and a speed check can join when you want them.
-
Intake
The idea comes in. Open Claude Code in the package and describe the product. Setup runs once, and the rest of the line builds on that.
-
The brief
The idea is written into a file the build has to follow. Research can look at who it’s for before any code.
-
Idea gate
Worth building, and the problem is clear? You pass it, or you set the gate to auto and a fresh session does. The session that wrote the idea can’t pass.
-
The spec
What the app does, who can see what, and how someone pays. Written down so assembly isn’t guessing.
-
Spec gate
Right product, specified well enough to build? A different session from the one that wrote it.
-
Assembly
Accounts, checkout, and the feature. For the lead desk, that’s the morning list, the draft, and who replied. Tests come with the code. Security can read the change before it ships.
-
Launch
The page people land on, the search text, and the legal pages.
-
Ship
A pull request carrying the idea through to the code.
-
Release gate
Safe to merge? It waits for you, unless you set that gate to auto. Even then, a different session has to pass it.
The same package works with Codex, Cursor, Gemini CLI, and OpenCode. The stop before a bad edit is wired for Claude Code. Git hooks and CI hold the rules for every tool.
The crew on the line.
Each station has an agent already in the package. The gatekeeper is the one that didn’t write the code.
Research
The problem, the customer, and what else is out there, before anyone writes the app.
Backend
The rules of the product: accounts, payments, and what happens when something fails.
Frontend
The screens a customer actually uses, including empty, loading, and error.
Database
Where the data lives, and the rule that one customer can’t read another’s row.
Security
Sign-in, secrets, webhooks, and who is allowed to see what.
Performance
Speed, page weight, and the slow spots a review should catch.
Review
Reads the change against the spec before anyone calls it done.
Verifier
A fresh session runs the app. It didn’t write the code it’s checking.
Debugger
When something breaks, it finds the cause and brings the fix back onto the line.
Simplifier
Cleans the code so the next change is easier to make.
Gatekeeper
Passes idea, spec, or release when a gate is on auto. It never graded its own work.
What they already know.
Skills are the standards. Guards stop a bad edit before it lands. Git hooks and CI hold the same rules on every commit.
Sign-in
Accounts, sessions, a password reset, and the screen before anyone is signed in.
Stripe
Checkout, the customer portal, and what happens when a subscription lapses.
Every row
Migrations and row-level security, so one customer’s leads stay theirs.
Screens
Empty, loading, and error states, plus keyboard access and contrast.
Tests
A check has to pass before the work is called done. Bug fixes start from a failing test.
Secrets
A password is blocked before it can be written into the project. On Claude Code that stop happens before the edit.
Launch pages
The landing page, the search text, and the legal pages.
The trail
Each step commits what it decided. The next step reads that, so the thread can’t drift.
After the link, it keeps watch.
A night shift scans the live product and files what it finds. It doesn’t merge a fix. The loop can pick up the next idea overnight, including from those notes.
Security
Looks over the repo for auth gaps, data leaks, and secrets.
Speed
Measures the live site against your budgets, once you give it the address.
Dependencies
Known vulnerabilities, outdated packages, and code nothing uses.
Errors
Groups production crashes by cause, once an error feed is connected.
Buy it once. Use it on the next idea.
Beta is $49 once. You still pay Anthropic for Claude, or the provider of whichever model you run. The files stay yours.
Solo
Once, for beta. You, and every product you start.
- Workflows, agents, and skills
- Gates at idea, spec, and release
- An overnight loop
- Night shift scans after a merge
- Every product you start
- Updates while it’s 1.x
Team
$499 once
One company, including the people you hire.
- Everything in Solo
- Every project the company starts
- Email if the first start stalls
Questions
Do I need to know how to code?
No. Describe the product. A lead desk that finds firms and drafts the first email is enough. Open Claude Code in the package and start. You can pass each gate yourself, or leave it on auto.
How is this different from chatting with Claude?
A chat writes code in the thread. Shipforward runs a factory. The idea goes into a file, the line runs idea, spec, and release, and the agent that wrote the work can’t pass those gates. Skills for sign-in, billing, and who can read a row are already in the package. After the gates, the line can keep running overnight.
Can it publish the app, or save a password, without me?
A password is blocked before it can be written into the project.
The app doesn’t go live on its own. Release is a gate. You pass it, or you set it to auto and a different session passes it. That session didn’t write the code. After a merge, a night shift looks for security problems and writes them down. It doesn’t merge a fix.
What does it cost?
Solo is $49 once for beta, down from $149. Team is $499 once, with email if the first start stalls. You still pay Anthropic for a Claude subscription, or the provider of whichever model you run.
I already have a project. Will this overwrite it?
No. If a file is already there, the new copy is saved beside it.
Bring the idea.
Open Claude Code in the package and describe the product.
Get Shipforward · $49One payment. The files stay yours.