How we work
The 4MTR Velocity Model combines twenty-five-plus years of project, programme and product expertise with AI-augmented build and a growing library of pre-built platform components. It is the combination — not either piece alone — that lets a small studio ship companion apps in months, not years, without sacrificing quality, compliance, or care.
The combination that makes it work
The PM half
The AI half
Either half on its own produces ordinary results. AI without programme discipline produces fast code that doesn't ship — or ships and fails compliance. Programme discipline without AI produces well-managed twelve-month builds. The Velocity Model is the combination, and the combination is the moat.
The framework
A complete idea-to-shipped-product lifecycle, anchored to ISO 21502 (project management) and ISO 42001 (AI management systems), with PDCA continual improvement closing the loop.
The application and intake process. Partner ideas are screened against the ethos, the anti-criteria, and the studio's strategic fit before any build work begins. Most ideas are politely declined here — that is the point.
Standards: ISO 21502 §6.1 Initiating · BS 25800 safeguarding screen · ethos anti-criteria
Discovery work — user persona, problem definition, value proposition, ethical-fork pre-decisions, business model. Output is a versioned PRD that everyone can sign off and that future versions inherit from.
Standards: ISO 21502 §6.2 Planning · PRD discipline · BS 25800 design-time safeguarding
AI-augmented build under direct PM oversight, drawing on ~60–70% pre-built platform components. Decisions documented as they happen; ethical defaults pre-locked. The phase where the Velocity Model earns its time advantage: a typical two-week sprint compresses into roughly one day of focused work — fast enough to outpace traditional studios, with built-in contingency for proper review.
Standards: ISO 21502 §6.3 Executing · ISO 42001 §8 AI lifecycle
Sprint output is verified against acceptance criteria — functional, UX, accessibility, compliance, AI behaviour. Where the work touches sensitive content or vulnerable users, additional scrutiny is mandatory.
Standards: ISO 21502 §6.4 Controlling · ISO 42001 §9 Monitoring · BS 25800 safeguarding verification
Findings from test & review are folded back in — code corrected, PRD updated, decisions re-logged. The loop between 3, 4 and 5 may iterate several times before a sprint is judged ready to ship.
Standards: ISO 9001 §10 Improvement · PDCA "Act"
Production release — to staged users first where appropriate (BETA, advisor cohort), then to general availability. Release is recorded, monitored, and accompanied by documentation that satisfies auditability.
Standards: ISO 21502 §6.5 Closing (per release) · ISO 42001 §8 Deployment
Post-release review — user feedback, operational metrics, incident learnings, platform-component improvements that benefit the next app. Findings cycle back into step 1 (what to build next), step 2 (PRD refinements), and into the platform itself. This is the loop that compounds: each app makes the next one better.
Standards: ISO 9001 §10 / ISO 27001 §10 / ISO 42001 §10 Continual Improvement · BS 25800 ongoing safeguarding posture · PDCA full cycle
Why it matters
A traditional studio takes twelve to eighteen months to ship a single companion app. AI-only build studios produce fast code but stumble on compliance, accessibility, or ethics review. The Velocity Model compounds across the portfolio: every app inherits the discipline of every earlier one, every platform component built once is reused many times, every PRD decision is auditable years later.
It is — in other words — exactly what a programme professional with twenty-five years of project, programme and product development experience builds when given modern AI tooling. The model is the founder; the framework is the proof.
The Velocity Model is the engine. Your idea is the input. We invest the time and platform; you keep the majority.
Apply for equity-for-build →
4MindsThatRoam