Write it down
Decisions, trade-offs and the reasons behind them go in the log, not in someone’s head. Anyone can pick up where anyone left off.
The studio
Six people. One crew.
No account managers, no subcontractors, no bench. The people you meet on the first call are the people who design, write and deploy your software, and who answer the pager after launch.
Our story
Started small. Stayed small on purpose.
Jordan Hale started Shipped in 2019 after a decade of watching good ideas sink between agencies. One team designed it, another built it, a third was meant to run it, and nobody owned the result. The first client was a local bakery that needed wholesale ordering by Friday. It shipped on Thursday.
We grew one hire at a time, and only when the work asked for it. Today there are six of us: designers who write code, engineers who talk to customers, and one person who keeps every project on its weekly rhythm.
We still take on a handful of projects a year. That keeps the crew close to every release, and it means the person who built a feature is the one who fixes it if it breaks.
- Founded
- 2019
- Products shipped
- 40+
- People, all senior
- 6
- Release a week, every week
- 1
Who you will work with
The crew.
Every project gets a named lead and the whole studio behind them. Here is who is on board.
Jordan Hale
Founder and lead engineer
Has shipped Rails apps since the 2.x days and still reviews every pull request before it goes out.
Good at
- Architecture
- Ruby on Rails
- Kamal
Mara Okafor
Product designer
Turns a messy brief into a clickable prototype by Wednesday, then cuts half of it by Thursday.
Good at
- Interface design
- Prototyping
- Design systems
Tomas Reyes
Full-stack engineer
Writes the test first, the feature second and the commit message like someone will read it.
Good at
- React
- Inertia
- Testing
Elin Sorensen
Infrastructure engineer
Restores a backup every month just to prove it works, and keeps the logs of every attempt.
Good at
- Linux
- Backups
- Monitoring
Ravi Menon
Product engineer
Owns the unglamorous parts that make money: sign-up, billing, receipts and the emails around them.
Good at
- Payments
- Email delivery
- Accessibility
Hannah Lowe
Project lead
Keeps the weekly plan on one page and sends the Friday update before anyone has to ask for it.
Good at
- Scoping
- Release planning
- Client updates
What we value
How we treat each other and the work.
Our habits shape how projects run. These values shape how the six of us work together on a Tuesday afternoon.
Say the real number
Estimates come with the risky parts named out loud. A late surprise costs more than an awkward conversation early on.
Leave it tidier
Every change leaves the codebase a little easier to read than we found it. Small cleanups, every week, compound.
Go home on time
Tired people ship bugs. We plan for a normal working week, so the evenings stay free for the rare night that truly needs us.
Say hello
We’re not hiring right now, but say hello.
If you build software with care and want to be on our list for the next opening, send a few lines and a link to something you shipped. Clients are welcome too, of course.