Opposable Heads

Work

Software and hardware, made to fit.

Every engagement starts with the same question: what does a good day look like once this exists?

Practice areas

What we build.

Mobile applications

Field data capture, patient-facing tools, classroom companions. Designed for one-handed use, patchy connections, and devices that live in a pocket or a glovebox.

Web applications

Dashboards, portals, scheduling, reporting, integrations. Server-rendered where it should be, interactive where it counts, and observable in production.

3D printing & prototyping

CAD modelling through to printed parts: anatomical and mathematical models, jigs and fixtures, sensor housings, and short-run production pieces.

Systems that connect them

APIs, data pipelines, and device integrations that let the app, the instrument, and the spreadsheet finally agree with each other.

Sectors

Domains we know.

  • Education

    Tools for teachers and learners, from interactive practice applications to printed manipulatives that put a hard concept in a student's hands.

  • Medicine

    Research and clinical support software built around real protocols — careful with data, legible under pressure, auditable after the fact.

  • Civil

    Inspection, asset, and works-management systems for teams who split their week between a site and a desk.

Process

How an engagement runs.

Leverage the best practices, the best tools, to create the best outcome.

  1. Understand the workflow

    We watch the current process end to end and write down where it costs you time. That document becomes the scope.

  2. Prototype the risky part

    Whatever is least certain — an integration, a print tolerance, an interaction — gets built first, while changing course is still cheap.

  3. Ship in slices

    Working software in your hands early and often, on real infrastructure, with tests and deploys wired up from the first slice.

  4. Hand over cleanly

    Documentation, source control, and a runbook. Keep us on for support, or take it in house — both are a good outcome.

Bring us the awkward one.

The project that spans a device, a database, and a deadline.