Services

What we build, and how we charge for it

Four ways to work with us. Most projects start with the first one and only move on once the shape of the work is clear.

Product engineering

End-to-end development of a web or mobile product: interface, backend, database, deployment. Suited to a first release or a rebuild of something that has outgrown its original design.

  • Web applications, dashboards, internal tooling
  • Native and cross-platform mobile clients
  • API design and third-party integration
  • Migration off legacy systems

Consumer technology software

The software that surrounds a physical product. We take on the parts that sit between the device and the customer, and the services those parts depend on.

  • Companion apps and first-run setup
  • Device provisioning, pairing, identity
  • Telemetry collection and fleet reporting
  • Over-the-air update and rollback pipelines

Cloud & platform

Infrastructure that a small team can actually operate. Sized to the traffic you have, with a clear path to the traffic you expect.

  • Architecture review and cloud setup
  • CI/CD, environments, release process
  • Monitoring, alerting, incident runbooks
  • Cost analysis and reduction

Ongoing engineering

A retained block of time each month for teams that have shipped and now need maintenance, small features and someone on call when something breaks.

  • Feature work on an existing codebase
  • Dependency and security updates
  • Performance and reliability work
  • Agreed response times for incidents
A group of developers working together at a table

Engagement

Fixed scope or a block of time

Well-defined work is quoted as a fixed price against a written scope, so you know the number before anything starts. Work that will obviously change shape as it goes is billed as a monthly block of engineering time instead — it is more honest than a fixed price nobody believes.

  • A written scope before an invoice exists
  • Fixed price where the requirements are stable
  • Monthly retainer where they are not
  • No lock-in period on retained work

Scope

What we do not take on

Saying this up front saves a call for both of us.

Physical manufacturing

We build the software around a device. We do not do industrial design, tooling or production.

Marketing and SEO

We will build the site or the platform. Campaigns, content and ad spend are somebody else's craft.

Rescue work without access

We do not take over a codebase we are not allowed to read, or a system nobody will give us credentials to.

Tell us what the problem is

A few sentences is enough to start. If it is not a fit, we will say so and point you somewhere better where we can.