How we ship
What has to be true before we call it shipped
The same four stages whether it is a six week build or a four year retainer. Here is what happens in each one, and which part of the stack it touches.
How the work runs
Four stages, and what each one touches
Each stage touches a different part of the stack.
Design
- Figma
- FigJam
- Framer
- Storybook
- Illustrator
AI
- Claude
- Cursor
- MCP servers
- GitHub Copilot
- ChatGPT
- Gemini
- Perplexity
- LangChain
- Mastra.ai
- Vercel AI SDK
- RAG
Engineering
- React
- Next.js
- TypeScript
- JavaScript
- Node.js
- HTML
- CSS
- Tailwind CSS
- shadcn/ui
- Chakra UI
Mobile & Desktop
- React Native
- Electron
Infrastructure
- GitHub
- Git
- GitHub Actions
- Vercel
- Netlify
- AWS
- Google Cloud
- Cloudflare
- Terraform
- Serverless
- Docker
- npm
- pnpm
Data
- PostgreSQL
- Supabase
- Sanity
- Vector stores
Testing
- Playwright
- Cypress
- Jest
- Testing Library
Observability
- Sentry
- PostHog
- CloudWatch
Collaboration
- Slack
- Notion
- Confluence
- Google Docs
- Zoom
- Google Meet
- Microsoft Teams
Project management
- Linear
- Jira
- Trello
- Asana
Across every stage
- AI workflows
- Prompt engineering
- Evaluations
Where we stop
Four things we will not do
- Quote a large engagement without paid discovery first. Estimating a codebase we have not read is guessing with your money.
- Take work we cannot also support afterwards. Shipping something nobody will be there for is how systems get fragile in the first place.
- Let anything important live in one person’s head. A system nobody can explain a year later is a liability, however well it runs today.
- Agree to a date we do not believe in. Saying yes to an impossible deadline is choosing to fail later, more expensively.
Questions
The ones we get asked most
Tell us what you have
Email, phone, or a fifteen-minute call, whichever you prefer. We will tell you what we would do with it.