Engineering work, described in full.
Six kinds of engagement. Each section below covers what is included, the stack we would reach for, a realistic timeline, and who the work suits — so you can rule us in or out without a call.
Custom Software Development
Off-the-shelf software forces your process to match its assumptions. We build the system around the process you already run — the approval chain, the pricing rules, the exceptions your team works around every day. Work starts with mapping the real workflow, including the parts that live in spreadsheets.
What’s included
- Workflow and data model mapping before any code
- Role-based access matching your real org structure
- Integrations with the systems already in use
- Migration from spreadsheets or a legacy tool
- Admin tooling so your team can operate it without us
- Full source code ownership and documented handover
Typical timeline
8–16 weeks
Stack
- TypeScript
- Next.js
- Node.js
- PostgreSQL
- Docker
Who it’s for
Companies running critical operations on spreadsheets, or paying for a SaaS tool that fits two thirds of the job.
Talk about a custom software project
SaaS Platform Development
A SaaS product is a set of decisions about tenancy, billing and permissions that get expensive to reverse. We settle those first — how tenants are isolated, what a seat means, what happens on downgrade — then build the product on top of that foundation.
What’s included
- Multi-tenant architecture with isolation at the data layer
- Subscription billing, trials, upgrades and dunning
- Role-based permissions and team accounts
- Customer-facing analytics dashboards
- Usage metering and plan enforcement
- Full source code ownership and documented handover
Typical timeline
10–20 weeks
Stack
- TypeScript
- Next.js
- PostgreSQL
- Stripe
- Redis
- AWS
Who it’s for
Founders taking a validated product to market, and teams turning an internal tool into something they can sell.
Talk about a saas platforms project
Mobile App Development
We pick the platform approach from your requirements, not from preference. Cross-platform when the feature set is shared and speed matters; native when you need deep hardware access or platform-specific interaction. Either way, we handle store submission and the review cycle.
What’s included
- Native or cross-platform build, chosen from requirements
- Offline behaviour and state sync
- Push notifications and deep linking
- App Store and Play Store submission, including review responses
- Crash reporting and release analytics
- Full source code ownership and documented handover
Typical timeline
10–18 weeks
Stack
- React Native
- Expo
- Swift
- Kotlin
- Flutter
Who it’s for
Products where mobile is the primary surface, and companies extending an existing web platform to phones.
Talk about a mobile apps project
Backend & API Engineering
Most performance problems are data model problems that surfaced late. We design the schema and the query patterns together, load-test against realistic volumes rather than seed data, and document the API so the teams consuming it are not reverse-engineering behaviour from responses.
What’s included
- Schema design with indexing and query patterns planned together
- Versioned REST or GraphQL APIs with published contracts
- Third-party integrations with retry and failure handling
- Background jobs, queues and scheduled work
- Load testing against realistic data volumes
- Full source code ownership and documented handover
Typical timeline
6–14 weeks
Stack
- Node.js
- Python
- Go
- PostgreSQL
- Redis
- Kubernetes
Who it’s for
Teams whose product outgrew its first backend, and companies exposing an API to partners or their own mobile clients.
Talk about a backend & apis project
AI Integration
AI features fail in production for ordinary engineering reasons: no evaluation set, no fallback when the model is wrong, costs that scale with usage nobody modelled. We build the feature and the guardrails around it — retrieval over your own data, measured output quality, and a defined behaviour for the failure case.
What’s included
- Retrieval over your own documents and data
- Evaluation sets so output quality is measured, not assumed
- Defined fallback behaviour when the model is wrong or slow
- Token cost modelling before rollout
- Human review steps where the stakes require them
- Full source code ownership and documented handover
Typical timeline
4–12 weeks
Stack
- Claude API
- Python
- TypeScript
- Vector search
- Postgres
Who it’s for
Teams with an existing product and a specific task to automate — not teams looking for a use case.
Talk about a ai integration project
Web & E-Commerce Development
The engineering standards we apply to platforms apply here too: real performance budgets, structured data, and a content model your team can edit without a deploy. Fixed scope and fixed price, because the requirements are knowable up front.
What’s included
- Design and build, with a performance budget enforced at CI
- CMS your team edits without a developer
- Technical SEO: schema, sitemaps, metadata, Core Web Vitals
- Payments, checkout and inventory for store builds
- Analytics and conversion tracking
- Full source code ownership and documented handover
Typical timeline
2–4 weeks
Stack
- Next.js
- TypeScript
- Sanity
- Shopify
- Stripe
Who it’s for
Companies whose current site loads slowly, ranks poorly, or needs a developer for every copy change.
Talk about a web & e-commerce project
Let’s talk
Tell us what you’re building.
A 30-minute call. Bring the problem, the constraints and the deadline — we will tell you what it takes to build, or that we are not the right firm for it.
- 01
A number on the first call
You leave with a firm timeline and a price range, not a promise to send one next week.
- 02
Engineers, not account managers
You talk to the people writing the code. Nothing gets relayed through a layer that cannot answer.
- 03
You own everything
Source code, infrastructure and documentation transfer to you. Taking it in-house is a real option.
Taking on new projects for October 2026