The V2E Framework
Engineering at Variable Velocity
Build. Stabilise. Extend, each at its own speed.
Software systems cannot evolve using the same engineering approach at every stage. What drives speed early often creates fragility later. The V2E Framework aligns engineering velocity with the maturity of the system.
Most systems are built for speed,not evolution.
Push one approach through a system's whole life and it frays into the same five signals: one root problem, surfacing everywhere at once.
- Teams avoid modifying parts of the systemRisky areas get worked around, not fixed.
- Stability issues increase over timeSmall regressions become recurring incidents.
- Maintenance effort begins to dominateMore time on upkeep than on what's next.
- Features take longer to shipEvery change touches more than it should.
- Rewrites start feeling unavoidable“Start over” becomes the default proposal.
Yet many teams continue using the same engineering approach throughout the system lifecycle.
- Early
Early systems prioritise speed.
- Growth
As products grow, complexity increases, dependencies expand, and engineering priorities begin to shift.
- Maturity
What was once fast becomes difficult to change.
- Aging
What was once flexible becomes fragile.
- Breakdown
This is where engineering velocity begins to break down.
Engineering velocity shouldevolve as systems grow.
Different stages of maturity demand different engineering priorities. The V2E curve moves through three, each with its own velocity, its own focus, and its own way of going wrong.
Build
Speed & validation
Validate the idea and reach product-market fit before the architecture locks in.
Stabilise
Reliability & control
Add reliability and architectural control as complexity and load grow.
Extend
Capability & scale
Scale into performance and advanced capability on a system built to hold it.
Right approach. Right stage. Right velocity.
The V2E Framework aligns engineering priorities with the maturity of the system.
What happens when engineeringvelocity stays constant.
Systems struggle when engineering approaches fail to evolve alongside the platform.
Teams optimise for speed long after systems require stability.
They introduce unnecessary complexity before the product is ready.
In both cases, engineering effort becomes misaligned with system maturity.
Slower development, increased fragility, and costly architectural decisions.
How AlterSquareapplies theV2E framework.
Every engagement begins by understanding where your system sits in the V2E lifecycle, then aligning engineering strategy with the stage it's actually in.
- 01
Build systems designed to evolve
Move quickly without creating unnecessary architectural constraints.
- 02
Stabilise fragile systems
Strengthen platforms through controlled, incremental improvements.
- 03
Extend platform capabilities
Introduce AI, automation, and specialised engineering capabilities.
Product teams and technology leaders who ship with us.
Let's talk
Where is your systemon the V2E curve?
Understanding the stage of your platform helps determine the engineering approach required for future growth.
Senior engineers reply within one business day.