How we work.
Five ways to engage. They differ in who holds accountability and for how long, not in how hard we work on the problem.
Each one below says what it is not suited to. That is deliberate. Being placed in the wrong model is the most common way a good engagement goes badly, and it is usually decided before anyone writes a line of code.
01Engagement models
Five ways to engage.
- 01
Advisory
Strategy, architecture and decision support.
Short, senior and scoped to a decision. Typically a target architecture, a business case, a build-or-buy assessment, or technology due diligence. The output is a decision you can defend, with the tradeoffs written down.
Suited to
- A large commitment is about to be made
- Internal opinion is split and needs an independent read
- An investment case needs technical substantiation
Not the right model if the decision is already made and what you need is delivery capacity.
- 02
Build
Engineering, AI, data and platform delivery.
A defined outcome, delivered. ValueQue engineers own the work and the architecture decisions inside the scope, and are accountable for the result rather than for hours booked.
Suited to
- The problem is understood and the constraint is delivery
- A capability is needed that does not exist internally yet
- A proof of concept has to become something operable
Not the right model if the requirements are still moving weekly. Start with Advisory and come back.
- 03
Transform
Multi-phase enterprise transformation.
Strategy, architecture and delivery under one accountability, sequenced so value arrives during the programme rather than at the end of it. The operating model is part of the scope, because a target architecture no organization is shaped to run is a document, not a plan.
Suited to
- Modernization, AI adoption or a data programme at scale
- Several workstreams that keep blocking each other
- A previous attempt stalled and needs re-founding
Not the right model without an executive sponsor who can change how the organization works, not only what it builds.
- 04
Extend
Embedded teams working alongside yours.
ValueQue engineers and architects working inside your teams, on your board, in your review process. Distinct from staff augmentation: the work is scoped to outcomes and our accountability travels with it.
Suited to
- Deep expertise is needed for a phase, not permanently
- A capability should be transferred to your team, not retained by us
- Delivery is underway and a specific gap is blocking it
Not a way to buy developer days. If headcount is the requirement, a staffing partner will serve you better and cost less.
- 05
Retain
Ongoing technology advisory and architecture leadership.
A standing relationship: architecture review, technology decisions, vendor assessment and a senior second opinion available when it is needed rather than when a statement of work can be raised.
Suited to
- No CTO or chief architect, and decisions keep waiting
- A board or investor wants independent technical oversight
- Architecture governance exists but has no senior challenge
Not the right model for a single decision. That is Advisory, and it costs less.
02How we work
We do not sell technology. We solve technology problems.
Consultancies that only think produce decks. Firms that only build produce technical debt. The model below is one continuous engagement, and the last stage is the only one that counts.
- 01
Think
Strategy, architecture, business case.
What is actually worth building, what it is worth, and what has to be true for it to work. The answer is sometimes that the programme should not proceed as scoped.
- 02
Design
Target architecture, operating model, roadmap.
The target state, the sequence that reaches it, and the organizational shape that can run it. Roadmaps that ignore the operating model do not survive contact with delivery.
- 03
Build
Engineering, platforms, AI, data and infrastructure.
Senior engineers building the thing, alongside your teams. Architecture decisions get made by the people who have to live with them.
- 04
Scale
Governance, optimization, adoption.
The phase most programmes skip. Cost, reliability, governance and adoption are where value is either realised or quietly lost.
- 05
Value
Measurable business outcomes.
Defined at the start, instrumented during, and reported against afterwards. If it cannot be measured, we say so before the work begins rather than after.
Not sure which one fits?
Describe the problem rather than the engagement. Choosing the model is our job, and getting it right is most of the value.