Design & engineering studio · Vermont
We design and engineer software for daily use.
Web apps, mobile apps and internal tools, built in South Burlington and looked after once they are live.
- 9
- products built in 2025 and 2026, each with a case study
- iOS, Android, web
- one studio for every platform
- Every 1–2 weeks
- a working preview link while we build
- Since 2022
- in South Burlington, Vermont
What we do
Four kinds of project. Design and engineering are part of every one. All services
Web applications and SaaS
Customer-facing products, from the sign-in screen to billing and the admin side, on a stack your next engineer will already know.
Recent: Split & Pay, FrogSky
Web applicationsMobile apps for iPhone and Android
iPhone and Android from one codebase, with native work where the platform asks for it: watch apps, Live Activities, the lock screen.
Recent: StackPilot, Pacelit
Mobile appsInternal tools and business systems
The spreadsheet that runs the business, turned into software the whole team can use, with exports that match how the books are kept.
Recent: MD Motors
Internal toolsModernizing older software
Moving an ageing system onto a maintained stack without stopping the business that depends on it, one piece at a time.
Modernization
Built and running
A few recent products, with the decisions behind them. All 9 case studies
A failed release sits at the top of the log with its error and a one-tap rollback.
Spend is projected against the monthly budget. Apps that cost money on almost no traffic are flagged as leaks.
Pacelit
A private activity tracker for runners, cyclists and hikers, with an Apple Watch companion.
Read the case study
Pace, timer and distance stay on the lock screen in a Live Activity, with Pause and Lap one tap away.
Split & Pay
Photograph the receipt, split by item or by share, and settle up in seconds.
Read the case study
Everyone at the table claims their own items from their own phone.
The dealer’s Google Sheet stays the source. VIN details are decoded per vehicle, only when the dealer asks.
How a project runs
The same people stay on it from the first conversation to the release after launch.
01
Understand
The business, the people who will use the software, and what has been tried before.
02
Plan
A written scope: what gets built first, what it costs, and what is left out on purpose.
03
Design and build
Design and engineering run together. Working software reaches a preview link every week or two.
04
Launch and look after
Code, accounts and documentation are yours. We stay on to maintain what we built.
Tell us what you are building.
A few lines about the project and when it needs to ship is enough to start.