Corporate Solutions

Make system behaviour explicit. Put it to the test.

Research partnerships, focused engineering and practical training for teams working with complex systems. Each engagement must contribute to our research, evidence, sustainable resources or strategic capability.

Discuss an engagement Read what we decline ↓

The mission test

Every engagement must make a defined contribution.

The strategic plan’s mission-alignment criteria require funded work to meet at least one of four tests. Work that meets none is declined. Before agreeing a scope, we identify the contribution and how it will be assessed.

Advance the research agenda: Address an explicit question about modelling complex systems, their behaviour or the correctness of their implementation.
Produce applied evidence: Test a claim in practice and record the result, including failures, limits and conditions under which it holds.
Generate sustainable resources: Provide a credible contribution to sustaining research after delivery costs and ongoing commitments are accounted for. A fee alone does not establish this.
Build strategic capability: Strengthen reusable architecture, systems research, formal methods, domain modelling or the ability to document and independently review the work.

We also assess delivery costs, ongoing obligations, capacity and dependencies under the plan’s decision rules. Paid research, engineering and training can sustain the wider programme, but revenue does not override these checks. We decline work we cannot resource or sustain alongside protected research. The plan’s numerical research-capacity floor is still to be set.

What we take on

Three ways to work with us.

Engagements can combine these activities. The scope is defined by the question, the output and the evidence needed to judge it.

Research

Investigate and model a live system

Investigate a defined systems question in production or legacy workflows. Make hidden rules, states, transitions and invariants explicit.

Research agenda · Applied evidence

What the work produces

A reviewable model, documented assumptions and failure cases, and a specification or research report with findings and limitations.

Engineering

Test a model through engineering

Test an explicit model through a bounded prototype or technical review. Examine conformance through cases such as delayed data, replay and reconciliation.

Applied evidence · Strategic capability

What the work produces

A prototype or architecture review with rules traced to model clauses, test fixtures, and a record of where behaviour conforms or the model needs correction.

Training

Build the capability to use the work

Practise reading, applying and challenging models through workshops, cohorts and facilitated reviews. Use concrete workflows, failure cases and reusable exercises.

Strategic capability

What the work produces

A worked model or conformance exercise, reusable materials, and an assessment of participants’ ability to explain and test system behaviour.

What we decline

Some work belongs elsewhere.

A commercial opportunity must support the mission and leave room to pursue it. These boundaries apply even when a project is funded.

General development and staff augmentation. We do not take on feature backlogs, team cover or open-ended platform delivery. Engineering engagements need a bounded question, an explicit model and an agreed way to test the result.
Tools without a published model. We decline requests to ship, share or use a tool in delivery ahead of its model, hide rules only in code, or let a tool decide what its model leaves undefined.
Routine collections operations. Debt recovery, outsourced account handling and ongoing incident-response cover are outside this offer. Our contribution is modelling, investigation and validation.
Generic training. We decline broad motivational or systems-thinking sessions without a concrete model, workflow or capability for participants to practise and assess.
Work that blocks scrutiny or displaces protected research. We decline terms that prevent required model publication or honest reporting of limitations, and commitments we cannot resource sustainably.

Before work starts

Bring a problem we can examine.

A useful first conversation starts with three things.

Your problem: What does the system do? What is uncertain or failing?
Available evidence: What records, examples or access can help us examine it?
Your constraints: What timing, budget and data restrictions should shape the scope?

Before committing, we agree a written scope: the question, mission contribution, outputs, evaluation criteria, delivery capacity and cost. We also agree data access, confidentiality and publication terms that protect partner data while allowing required model publication and honest reporting of findings.

Start a conversation Read the strategic plan →