Design and engineering for software that can’t afford to fail.

A-001 Site & survey

Question the brief before answering it.

The most expensive mistakes are made before the first line of code. So every engagement starts on site, with a discovery sprint of two to four weeks that surveys the ground before anything is built.

1. Q1

   Who is it for, and what are they trying to get done?

2. Q2

   What must never fail, and what happens when it does?

3. Q3

   Which rules apply: KYC, PSD2, GDPR, retention, disclosure?

4. Q4

   What will success look like, in numbers you already track?

You leave with Problem framing · research findings · a risk register · a clickable prototype · a costed plan.

S-100 Foundations

What you never see, but everything stands on.

Regulated products are judged on what happens underneath. These commitments sit under every engagement, written into the contract, not the pitch.

1. F1

   Security by default

   Least-privilege access, audit trails, dependency scanning and a secure development lifecycle.

2. F2

   You own everything

   Code, designs and IP are yours from day one.

3. F3

   EU-based, GDPR-native

   Bucharest, Romania. Data and contracts under EU law.

4. F4

   Ready for audit

   Every decision traceable, every change recorded. We design for consent, retention and explainability from the start.

5. F5

   Accessible by default

   WCAG 2.2 AA is the target on every product, not an extra.

6. F6

   Quality you can inspect

   Automated tests, code review, CI, observability, documentation and a clean handover. NDA as standard, with weekly demos and reporting.

1

accountable team

0

hand-offs

100%

IP ownership

EU

based, GDPR-native

S-200 The core

One accountable team. No hand-offs.

Strategy, design and engineering rise through one shaft. The senior people who scope the work lead the work, so ideas meet reality the same day instead of at the end of a hand-off.

1. C1

   Strategy

2. C2

   Design

3. C3

   Engineering

Construction sequence

1. 01
   Discover 2–4 weeks

   Problem framing, research, risks, a clickable prototype and a plan.

2. 02
   Design

   Journeys, interfaces and a design system, validated with users.

3. 03
   Build

   Production code from the first sprint: tested, reviewed, documented.

4. 04
   Launch

   Release, monitoring and handover.

5. 05
   Evolve

   Iterate, scale and support.

Forms of contract and how a project starts: see A-700 Programme.

Remove friction, not people. Faster delivery comes from clearer decisions, not longer hours. Around the core, a vetted network of specialists joins when the work needs more hands, and the core stays accountable.

S-300 Structure

Five capabilities. One frame.

Each floor carries its own load and rests on the one below. Select a floor, here or on the drawing.

1. L5

   Team extension

   Senior design or engineering leads, embedded in your team.

2. L4

   Platform & delivery

   Cloud on AWS, Docker and Kubernetes, CI/CD, observability, quality engineering.

3. L3

   Engineering

   Web front-ends, back-ends and APIs, payments integration, search, identity and access.

4. L2

   Experience & interface design

   UX, UI, interaction design, accessibility and design systems.

5. L1

   Product strategy & discovery

   Problem framing, research, prototypes and roadmaps.

M-400 Systems

Design for failure.

In money flows, a retry must never charge twice. Every service is routed through the core, and we build for the unhappy path first.

A-500 Envelope

The face your customers touch.

The envelope is where structure meets people: journeys, interfaces and design systems that stay consistent across every screen, accessible from the first sketch.

1. E1

   Journeys & UX

   The route a customer takes, from the street to the thing they came for.

2. E2

   Interface & interaction

   Clear screens for decisions that involve money, data and consent.

3. E3

   Design systems

   One module, repeated with discipline across products, brands and markets.

4. E4

   Accessibility

   Step-free by default. WCAG 2.2 AA from the start.

A-700 Programme

How to work with us.

Four forms of contract and one way of working: the same senior core leads each of them, and every one can start small. What changes is how much we take on, and for how long.

1. W1

   Discovery sprint

   Fixed scope

   What it is

   A short survey of the problem before anything is built: users, risks, rules and a plan.

   Shape

   2–4 weeks, fixed scope, led by the senior core.

   You get

   Problem framing, research findings, a risk register, a clickable prototype and a costed plan.

   How it starts

   An intro call, then a short written sprint proposal.

2. W2

   Product build

   Phases or a dedicated team

   What it is

   We design, build and launch the product end to end, then help it evolve.

   Shape

   Fixed phases with agreed scope, or a dedicated team on a rolling plan.

   You get

   Production code from the first sprint, a design system, weekly demos, documentation and a clean handover.

   How it starts

   With a discovery sprint, or with yours if it already answers the four questions on A-001.

3. W3

   Team extension

   Senior leads embedded

   What it is

   Senior design or engineering leads, embedded in your team, your rituals and your tools.

   Shape

   Rolling, and reviewed with you at every milestone.

   You get

   Senior judgement where the team needs it, and the standards, reviews and habits that stay after we leave.

   How it starts

   An intro call about the gap, then a lead proposed to fill it.

4. W4

   Platform modernisation

   Legacy to cloud, in stages

   What it is

   Moving a legacy platform to the cloud without stopping the business that runs on it.

   Shape

   In stages: one slice at a time, each one releasable on its own.

   You get

   An architecture assessment and a staged migration plan, then working increments on AWS with CI/CD and observability.

   How it starts

   A discovery sprint on the current platform: its dependencies, its risks and the first slice to move.

How a project starts

1. 01Intro call

   Our leadership team listens: what you’re building, what it must never do and which rules it lives under. NDA first, if you need one.

2. 02A discovery-sprint proposal

   We reply in writing: the questions the sprint will answer, who leads it, what you get and when. Not a template.

3. 03Kick-off

   We start on site with your team: stakeholders, access and constraints on the table, and the first weekly demo in the diary.

Book an intro call

G-001 General notes

Seven notes that apply to every drawing.

Each note is demonstrated on its own sheet. This is the index; follow a reference to see it drawn.

1. 1Question the brief before answering it.Four questions, answered on site before anything is built.A-001
2. 2Ready for audit.Poured into the foundations, not added at the end.S-100
3. 3No hand-offs.One shaft carries strategy, design and engineering.S-200
4. 4Remove friction, not people.Specialists join around the core; accountability stays in it.S-200
5. 5Design for failure.Retry the payment: more attempts, still one charge.M-400
6. 6Ship the front door first.Phase 1 opens the door while the floors above are built.A-500
7. 7Configuration over releases.Switch the industry: the shell changes, the core stays.A-600