Services

We take products from an idea to something people pay for. That covers interface and architecture design, the build itself, the infrastructure it runs on, and the release process afterwards. We stay on past launch, because the first few releases are when you find out which of your assumptions were wrong. If there is a decision to make about how something should behave, we will raise it in week one rather than let it surface in a bug report in month six.

You have something built and you want an outside read on it. We get access to the codebase, spend a few days in it, and talk to the people who work in it every day. Then we write up what we found, ordered by what we would fix first, with a rough estimate of what each one costs. Sometimes the conclusion is that the code is fine and the real problem is in how the team is set up. We will say that too.

We join your team as engineers. Your repositories, your tracker, your review process, your standups. The same people stay on the project for its whole duration, so the context they build up stays where it is useful. We are not trying to become permanent: engagements end, and the good ones end with a handover that takes an afternoon.