Skip to main content
How We Work

Architecture first. Then we build it ourselves.

Most consultancies hand you a deck. Most agencies hand you code with no plan behind it. We do the architecture, then build the first production version personally, then stay to help the team that runs it. Every phase ends with something you can hold.

The four phases

Stop after any phase and keep everything.

Phase 01

Discover

Understand the estate, the constraints and the regulatory context. Prove the risky part on real devices.

  • Findings report
  • Working prototype
  • Cost model for production
Phase 02

Architect

Define every domain as a contract before a screen is built, so teams work against mocks from day one. Review security and data protection.

  • Reference architecture
  • Interface definitions and mocks
  • Security review and risk register
Phase 03

Build

The first production version, built by the architect who designed it, with release automation from the first commit.

  • Production release
  • Automated versioning and publishing
  • Handover documentation
Phase 04

Operate

Fractional architect or CTO. Roadmap, governance, cost triggers and mentoring for the team that runs it, with spend staged against measured load.

  • Roadmap and governance
  • Cost trigger reviews
  • Hiring and mentoring
Engagement models

Five ways to work with us.

ModelShapeYou getBest for
Architecture review and security auditFixed scopeFindings report and a staged fix planPlatforms already in production
Discovery and prototypeShort engagementPrototype on real devices and a production cost modelNew spatial, AI or integration ideas
Production buildScopedArchitecture plus the first production version with release pipelinesTeams that need it shipped, then owned
Production rescueAs neededDiagnosis and repair of a live system under pressureEngine upgrades, vendor migrations, outages
Fractional CTO or Chief ArchitectPart-time, ongoingStrategy, governance, hiring and a cost-aware roadmapStart-ups and scale-ups in regulated markets
Principles

Applied on every engagement.

Contracts before screens

Every backend domain is defined as an interface before a screen is built. Teams build and test against mocks, and swapping in the real system is a one-line change.

Build once, deploy everywhere

One solution for browser, native, mobile or headset. Uses well defined architecture to prevent duplication and ensure consistency across platforms.

Investment staged against measured load

Home-lab-first and free-tier-first infrastructure. Cloud spend arrives in phases, each paid for only when the measurements demand it.

Security and data protection as defaults

Security audits that find unprotected writes and committed secrets. GDPR-compliant deletion. Zero Trust single sign-on. Role-to-scope access mapping.

One automated release gate

The same versioning, testing and publishing automation on every repository, client or open source.

Open foundations, private delivery

We build with open source technologies and publish tooling of our own to give back. Client projects are never published, and the intellectual property stays with the client.

After you email

What happens next.

No pricing is published because every engagement is scoped to the estate in front of us. This is how a first conversation runs.

Step 01

A reply with a first view

We reply with what we would look at first and the questions we would need answered. Usually within two working days.

Step 02

A scoping call, under NDA if you prefer

Thirty to sixty minutes on the problem, the estate and the constraints. Governance questions belong here: clinical safety, information governance, security posture, continuity and references.

Step 03

A written proposal for the first phase only

Scope, deliverables, duration and price for Phase 01 or a fixed-scope review. Nothing beyond that is committed until you have seen the output.

Get in touch

A few lines by email is enough to start.

Tell us what you are trying to do and what is in the way. We will reply with what we would look at first.