Product engineering

The software your AI runs inside. We build web apps, mobile apps and backends that are tested, observable and handed over in a state your team can keep shipping.

  • WebApps, dashboards, admin tools
  • MobileiOS and Android
  • BackendAPIs, data, integrations

What we build

Three kinds of product work, each with its own page.

How a release ships

The same path on a two-week sprint as on a sixteen-week build.

  1. Tested

    Automated tests run on every change, and nothing merges while they fail.

  2. Reviewed

    Every change is read by a second engineer, or by you, before it ships.

  3. Signed off

    You try each release in staging, on real data, before production.

  4. Observable

    Logs, metrics and alerts from the first release, so problems show up before users report them.

  5. Reversible

    A rollback plan written before release, so a bad deploy is undone in minutes.

Tools we build with

Well-supported, widely known tools, so your next hire already knows them. When you have a stack, we build in yours.

  • LanguagesTypeScript, Python
  • WebReact and its frameworks
  • BackendNode.js, Python
  • MobileReact Native, or native
  • DataPostgres, and what you run
  • CloudYour account: AWS, Google Cloud or Azure
When the product needs AI

Questions about product builds

Ask anything else on the consult.

Can you take over an existing codebase?

Yes. The first week is a written review of what is there: what to keep, what to fix first, and what it would cost.

Do you design the interface too?

We build from your designs, or work with a designer we trust when you have none. You see and approve the design before it is built.

Is the price fixed?

Yes, for a scoped build: the estimate from Discovery & Architecture becomes the price. Changes are written down with their cost before work starts.

Who looks after it after launch?

Your team, with the docs and runbook from the handover, or us, through Embedded Engineering by the month.