Skip to content

08 Contact

Start a technical brief.

Not a discovery call with an account manager. A 45-minute conversation with the engineering lead who would be accountable for the work, about the specific thing you are stuck on.

01 The brief

What to bring.

The more precise the constraint, the more useful the first conversation. None of this is mandatory — a paragraph is a perfectly good start.

  1. 01 The constraint — what decision or process is being made badly, and how often.
  2. 02 What you already have — data, sensors, systems, previous attempts.
  3. 03 The number you are trying to move, and what it is worth.
  4. 04 The date that matters, and why it matters.
  5. 05 Anything that makes this environment unusual — segmentation, safety, audit, scale.

Prefer email

[email protected]

Briefs are read by the engineering lead who would own the work. If you need an NDA in place before sharing detail, say so and we will sign yours or send ours.

Brief form

We use what you send only to reply to you. It is not added to a mailing list, and this site runs no advertising trackers and sets no cookies. See our privacy note.

02 Engagement models

Four ways this usually starts.

Most relationships begin with the first one. Fixed scope, fixed price, and a written assessment you keep regardless of what you decide next.

E1

2–4 weeks

Diagnostic sprint

A fixed-scope investigation into a specific constraint — data readiness, architecture, delivery throughput or an AI opportunity. Ends with a written assessment and a costed option set.

Right when — You suspect where the problem is but want it named precisely before committing budget.

E2

1–2 quarters

Proof to production

We take one high-value use case from hypothesis to a live, monitored, owned system. Narrow scope, full depth — including the unglamorous parts that make it survive.

Right when — You need one undeniable reference case inside your own organisation.

E3

Quarterly, rolling

Embedded engineering pod

A senior, cross-functional pod embedded alongside your team — architecture, engineering, ML, quality and platform — operating on your board with your standards raised to ours.

Right when — You have a roadmap and need durable capacity plus a raised engineering bar.

E4

Retained, light touch

Technical advisory

Architecture review, AI strategy, hiring calibration and a second opinion on the decisions that are expensive to reverse. Selective, and deliberately low-volume.

Right when — You own the delivery and want senior judgement on tap.

These models combine and sequence. Most enterprise programmes begin with a diagnostic, move to a proof on a single high-value use case, and continue as an embedded pod once the target state is agreed.