Lab open · Cycle 01 in progress
We ship software.
A product studio. We build our own software, put it in real hands fast, and let usage decide what comes next.
Built with
- Next.js
- React
- TypeScript
- Postgres
- Supabase
- Vercel
- Cloudflare
- Swift
- Claude
- Stripe
In the lab
Small, sharp tools, products, v1s, experiments — one cycle at a time.
Every product has a version number and a status. Each one lives at its own address.
Manifesto
Software isn't real until someone uses it. Before that, it's a guess. So we keep the distance between idea and user as short as we can. We pick a problem, give it a fixed amount of time, and release what fits. Then we watch, ask, and listen. The next version is written by what we learn, not by what we assumed.
This is a lab. We ship.
How we ship
Shape. Build. Ship. Listen.
Fixed cycles. A clear appetite for every problem. Real users before the next round.
✓ v0.1 the-lab — live
✓ principles.md — published
● fern — building (week 1 of 6)
Next commands: ship fern --version 0.1 --to real-users; listen --cycle 01 --channel everywhere; shape cycle-02 --appetite 6w
- 01
Shape
Pick one problem. Set the appetite.
- 02
Build
Fixed cycle. Scope bends, dates don't.
- 03
Ship
Real release, real users, real version number.
- 04
Listen
Usage decides the next cycle.
Principles
What we hold ourselves to.
- 01
Ship is a habit, not an event.
Small, steady releases instead of big reveals.
- 02
Users write the roadmap.
Every opinion is a hypothesis until someone real uses the thing.
- 03
Fixed time, flexible scope.
We decide what a problem is worth, then make the solution fit.
- 04
Polish what people touch.
Speed in the scaffolding. Care in the experience.
- 05
Version numbers over promises.
Progress shows up as releases, not slides.
- 06
Let go fast.
If it doesn't land, we learn, retire it, and ship the next one.
The log
Everything we release, as it happens.
v0.1The lab opens. theshippinglabs.com goes live.
Shipped · studio
C01Cycle 01 starts — Fern enters the build.
Planned · cycle
v0.1Fern v0.1 in the hands of the first ten teams.
Planned · product
C01Cooldown — we read every message before the next bet.
Planned · cycle
For startups
Need it in users' hands, not in a deck?
We bring the same rhythm to your product: a scoped first release in weeks, then cycles driven by what your users actually do. In English or Spanish.