Our work

The projects above are roughly seven years of shipped work across five industries. Each one started with a conversation about a real problem. A research group was drowning in manual soil data. A mortgage broker wanted a better customer portal. A sports startup needed to generate a lot of athlete content. An equipment retailer was moving their catalog online. None of them started as a tech project. They started as a problem. The tech was just the tool we chose for the job.

We think hard about tech fit. The wrong pick compounds over years. The Canadian Soil Database runs on Golang and PostgreSQL. We chose that stack because the data pipelines move millions of records. The team that maintains the system wanted something simple to deploy. Athlete Era CoachHub uses LangChain and LangGraph. Its content pipeline has many branching steps. A graph-based tool fits that shape. Northern Plains Equipment runs on Next.js and Shopify. The client needed a fast storefront on top of a mature commerce backend. Combine World has been on Magento since 2018. It was the right call at the time. The investment has paid off every year since.

A portfolio that spans this many industries is unusual for a small shop. We think it is a feature, not a bug. Working across fields forces us to stay curious. A pattern we learned from soil science often turns out to be useful in an e-commerce build. A storage strategy we used for spatial data shapes how we index documents for a retrieval system. So when a new client arrives with a problem we have not seen, we usually have a nearby experience to draw on. We are also happy to say what we do not know. That honesty tends to lead to better scoping and fewer surprises down the road.

Each entry in the grid links to the live production system when one is available. If a project looks like what you are trying to build, mention it when you reach out. We enjoy talking about the work. The details we share on a call are often the most useful part of a first conversation. Several projects also have case studies or blog posts. If you want more depth before getting in touch, those are a good place to start. And if you just have a quick question, email works too. We read every message and reply within a day or so.

Most of the work you see here was delivered by a small, senior team. We do not scale up to a dozen people for a single project. We stay close to the code. That means the person who writes your first architecture doc is the same person who deploys the system to production. It also means you get direct answers, not account-manager summaries. If that model fits how you want to work with a vendor, we would love to hear from you. If it does not, we will say so early and point you in a better direction.