Comparison · Fol. I · Bureau vs agency

Orchestrix vs transformation agencies.When a working system beats another roadmap.

Honest comparison · UK SMB context

Digital transformation agencies are built for multi-team programmes that need coordination at scale. Most UK SMBs don’t. They need one operational fix, shipped, owned. This page is the honest version of when each approach wins.

Quick answer

A digital transformation agency wins when the engagement requires multi-discipline coordination at scale: change management, cross-team training, parallel workstreams across departments. The bureau wins when the engagement is a specific operational fix that can ship fixed-fee in weeks. UK SMBs who choose an agency often pay for a strategy phase, then a delivery phase, then a quarterly retainer. The bureau skips the strategy phase entirely.

Fol. II·Side-by-side
Dimension
Transformation agency
Orchestrix
What you get
Agency · A team. Strategy consultant, project manager, designers, developers. A delivery org with capacity.
Orchestrix · One operator. Direct work, no project manager between you and the code.
Engagement model
Agency · Strategy phase + delivery phase + ongoing retainer. Fees compound.
Orchestrix · Free triage + fixed-fee audit + fixed-fee build + optional managed retainer.
First deliverable
Agency · A roadmap document, a phased delivery plan, a 40-slide steering deck.
Orchestrix · A written punch list with fixed-cost proposals for each fix.
Time to first working build
Agency · Often 4–8 months from initial conversation to deployed system, depending on phase length.
Orchestrix · 6–14 weeks from triage to deployed build, depending on scope.
Pricing model
Agency · Discovery fees, project fees, change fees, retainer fees. Often opaque until contract negotiation.
Orchestrix · Fixed-fee, agreed before work starts. Numbers visible on the website.
Best for
Agency · Multi-team transformations, change management at scale, regulated industries with parallel workstreams.
Orchestrix · Specific operational fixes, custom builds, workflow surgery, scoped engagements.
What stays with you
Agency · Code in their repo (sometimes). Documentation in their format. Ongoing dependency.
Orchestrix · Code in your repo. Plain-English documentation. No dependency on Orchestrix to run it.
Exit cost
Agency · Notice periods, knowledge transfer fees, dependency on agency-specific tooling.
Orchestrix · None. Cancel the optional retainer with 30 days' notice. The build keeps running.
Fol. III·When the agency wins
When to hire an agency · Fol. III

Sometimes
you genuinely need a team.

The bureau is honest about its scope. An agency is the better choice in these cases:

  • Multi-team change at scale

    Programmes that touch finance, operations, IT, and HR simultaneously. Hundreds of users, parallel training streams, political layers, executive steering committees. Genuinely needs an org-shaped delivery model.

  • Heavy change management

    When the technical build is the small part of the engagement and getting humans to use the new system is the hard part, agencies bring people-skills capacity the bureau doesn’t.

  • Continuous capacity

    If you need a delivery team available 12 months a year for a rolling backlog of changes, a retainer with an agency makes economic sense. The bureau does fixed-fee engagements, not retained capacity.

  • Regulated programmes with audit oversight

    Some sectors require formal vendor accreditations (ISO, Cyber Essentials Plus, sector-specific). Mature agencies have the certifications. The bureau, as a sole operator, doesn’t.

Fol. IV·When the bureau wins
When the bureau wins · Fol. IV

When you want
a working system
fast.

The bureau wins when the work is contained, the buyer is close to the operation, and the goal is a shipped fix rather than an ongoing relationship:

  • The decision-maker is the operator

    Owner-operators, MDs, and heads of operations who already know what’s broken. There’s no internal political layer to manage. A 15-minute conversation gets to a real plan; an agency’s discovery phase would just slow it down.

  • The fix is contained

    One workflow, two systems, three reports. A scoped problem with a scoped solution. Agencies are built to handle large programmes; for a single workflow, their delivery overhead is most of the cost.

  • You want to own the asset

    The build lives in your repository on delivery. Documentation in plain English. Any developer can maintain it. No agency-specific tooling, no platform lock-in, no quarterly retainer just to keep the lights on.

  • You've been burned by a roadmap before

    If you’ve paid for a transformation strategy and ended up with a deck and an invoice, the bureau is the inversion of that pattern. Audit produces a punch list, not a roadmap. Build ships a working system, not a phased plan.

  • Speed matters more than capacity

    A bureau build ships in 2 to 12 weeks. An agency strategy-then-delivery cycle often takes 6 to 12 months. If the operational pain is bleeding hours every week, fast wins.

Fol. V·The strategy-phase trap
The trap · Fol. V

You paid for
a roadmap.

The pattern most UK SMB owners describe when they arrive at the bureau:

Step 1

Discovery / strategy phase

6 to 12 weeks of workshops, interviews, and stakeholder mapping. Output: a roadmap document and a phased delivery proposal. Cost: £15k–£40k.

Step 2

Delivery phase begins

Quoted as 6 to 18 months. Slips. Each phase has its own scope-change process, each scope change has its own fee. Cost: £50k–£250k+.

Step 3

Quarterly retainer

After the delivery phase ends, you’re offered a retainer to handle changes and ongoing optimisation. Cost: £5k–£20k/quarter.

The bureau version

The bureau’s version of the same engagement: a free triage, a one-day audit (£2,500), a fixed-fee build (£2,000 to £15,000 for most SMB workflows), and an optional managed hosting retainer (£150/month) if there’s an actual server that needs watching. No strategy phase. No retainer until there’s something worth retaining.

Fol. VI·Common questions
Common questions

The things prospects ask.

When is a transformation agency genuinely the right call?
When the engagement requires multi-discipline coordination at scale: change management, large-team training, parallel workstreams across departments, ongoing supplier oversight. Enterprise programmes with hundreds of users and political layers genuinely benefit from agency capacity. The bureau is a wrong fit there, and will say so at the triage.
What's the strategy-phase trap?
Agencies often start with a strategy phase: a 6 to 12 week engagement that produces a roadmap document and a phased delivery proposal. The strategy phase is billable, the roadmap is generic, and the actual build comes after on a separate fee. SMBs end up paying twice for what could have been a one-day audit and a fixed-fee build. The bureau skips the strategy phase entirely.
Why is a quarterly retainer a problem?
Retainers are economically rational for the agency: predictable revenue, the team stays staffed, the relationship persists. They're often economically irrational for the SMB: paying every quarter for capacity you may or may not use, with no clean exit point. The bureau prefers fixed-fee per engagement and an optional managed retainer that covers actual ongoing work (hosting, monitoring, evolution), not retained capacity.
What if I'm already mid-engagement with an agency?
The bureau will tell you honestly whether to finish the agency engagement and then come back for the build, or whether you'd be better off cutting losses and starting over. Some agency strategy phases produce useful spec documents that a bureau build can execute against. Others don't. The audit settles which.
Doesn't a one-operator shop have capacity risk?
Yes, and the bureau is honest about it. Single-operator engagements scope at fixed-fee, fixed-timeline, fixed-scope so the risk is bounded. The build ships in 2 to 12 weeks, not in a multi-year programme. The code lives in your repository on delivery, so you can hire any developer to maintain or extend it. If continuity is the deciding factor, an agency may be the right call. The bureau won't pretend otherwise.
Can the bureau coordinate with an agency I'm already using?
Yes, on the right terms. A common pattern is the bureau handles the high-impact automation or custom build while the agency handles broader change management or training. Each side scopes its own work fixed-fee, no ongoing co-management, no shared retainer.
Fol. VII·Closing

Got a roadmap
and nothing shipped yet?

The 15-minute triage looks at the roadmap, identifies which fixes can ship in weeks, and ends with an honest answer. Sometimes the answer is “finish the agency engagement, then come back”. Sometimes it’s “the roadmap is the strategy phase you already paid for; let’s build from it directly.”