A final ShipOrSkip decision
We decided to skip it.
ShipOrSkip is closing. The workflow was useful, but the hosted business was not sustainable. The useful part now lives on as an open-source agent skill.
Get the ShipOrSkip skillWhy close it?
A good report. A terrible business model.
Put plainly: the unit economics were terrible.
Every useful report required a long chain of paid AI and web-research calls: validation, five separate research tracks, synthesis, and scoring. That made the result valuable—and made every run expensive.
Charging enough to cover the real cost would make the product hard to justify. Pricing it accessibly made it unsustainable. Closing the hosted app is the honest decision.
The useful part lives on
ShipOrSkip is now an agent skill.
I kept the core workflow and removed the hosted machinery that made it unsustainable. The result is smaller, open source, and intentionally more limited.
What it keeps
- Market, competitor, customer, technical, and risk research
- A Ship, Conditional Ship, or Skip verdict with feasibility scoring
- Strategy, roadmap, research artifacts, and optional build planning
The tradeoffs
- You need a compatible agent such as Codex or Claude Code
- Fresh research depends on the tools available to that agent
- Reports live in your workspace instead of a hosted dashboard
github.com/andriikravets
ship-or-skip-skill
Thank you for giving your ideas a harder look.
Sometimes the right decision is to skip—and keep the useful part.