What we build.
Three practices, one team. Most projects touch at least two of them.
Android
Apps that behave on a mid-range phone with a bad connection, not just on the demo device.
We ship Kotlin and Flutter apps end to end — architecture, offline behaviour, Play Store review, and the unglamorous maintenance afterwards. Most of our Android work replaces a spreadsheet or a paper process, so we spend as much time with the people using it as with the code.
- Kotlin & Flutter builds
- Offline-first data sync
- Play Store release and staged rollout
- Crash triage and version upkeep
Kotlin · Flutter · Firebase · Room · Ktor
Next.js on the App Router, typed end to end, with a CMS only when someone will actually use it. We care about the boring metrics — time to first byte, layout stability, and whether your team can update a page without calling us.
- Next.js apps and marketing sites
- Headless CMS wiring
- Payments and third-party integrations
- Core Web Vitals and accessibility passes
Next.js · TypeScript · PostgreSQL · Tailwind · Vercel
Automation
The scripts and services that delete a recurring two hours from someone's week.
We map the process first, then automate only the parts worth automating. Usually that means a scheduled job, a few API integrations, and a small dashboard so somebody can tell it worked without reading logs.
- Process mapping before code
- Scheduled jobs and queues
- API and third-party integrations
- Reporting so failures are visible
Python · Node.js · Docker · Postgres · GitHub Actions
How an engagement runs.
Roughly the same shape every time. The middle stretches or shrinks; the ends don't.
- 01Week 0
Talk it through
A call, then a written summary of what you actually need. If we're the wrong fit we say so here — it costs you nothing.
- 02Week 1
Shape and price
Scope document, flows, a fixed price and a date. You approve it before a line of code exists.
- 03Weeks 2–n
Build in the open
Weekly builds on a shared link. You review as it goes, so course corrections happen while they're still cheap.
- 04Launch
Hand over
Release, documentation, credentials, and a month of watching it in production with you.
We're a small team, so we take on a handful of projects at a time. If the calendar is full we'll tell you when it isn't, or point you at someone who can start sooner.
Which of the three do you need?
If you're not sure, that's a normal place to start. Describe the problem and we'll work out the shape of it together.