Engagement Model - How We Work With You

Flexible statements of work, clear framework, no bureaucracy

How we work with you

The slowest part of many IT initiatives isn’t delivery — it’s the contracting and admin around change. Our model is designed to remove that friction while keeping both sides protected.


We don’t lock customers into rigid, multi‑year arrangements where every adjustment becomes a renegotiation. We aim for clear terms, fast starts, and delivery that can adapt as reality changes.


Simple model:
The framework defines how we trade.
Statements of work define what we deliver.

Single point of contact:
You get a dedicated account manager. One person who takes ownership, coordinates delivery, and keeps things moving.

The framework: how we trade

Our Framework Agreement sets the ground rules: confidentiality, security expectations, support, billing, liability boundaries, and the practical rules of engagement. It is there for clarity and protection, not to slow delivery.


Once the framework is in place, you should not need to renegotiate basics every time you need something done.


Policies: how we operate

The framework sets the contractual foundation and a statement of work defines what you have asked us to do. Our policies set out how we run services in practice: what we will do, what we will not do, and how we manage risk.


Where relevant, policies are incorporated into the framework and are kept publicly available for transparency.


Updates and stability

Policies evolve as technology, threats, and regulation change. Where practical, we notify customers of material updates via the HelpDesk and/or registered contacts. Urgent changes required for legal, regulatory, or security reasons may take effect immediately.

Statements of work: what we deliver

A Statement of Work (SoW) is what authorises delivery. It can be formal or lightweight — the point is shared understanding.


What an SoW typically covers

For everything except Technical Support via the HelpDesk, a Statement of Work can define any or all of; Objective, scope, assumptions, deliverables, timescales, responsibilities/dependencies, and pricing (time & materials or fixed price). A statement of work CANNOT define contract terms.

For Technical Support via the HelpDesk, the Statement of Work is the ticket you raise.

SoW examples (all valid)

  • A written scope and quote for a project
  • An email: “Please review this design and call out the risks.”
  • A HelpDesk ticket to investigate and resolve an issue
  • A short call that ends with: “Yes — please proceed.”

What you get

  • A fast start with minimal admin
  • Work that scales up or down
  • Clear time & materials or fixed‑price options
  • Support and escalation when it matters

Partnership

We are not trying to be the cheapest provider. We focus on reliability, responsiveness, and long‑term relationships. The aim is simple: do good work, stay accountable, and be there when you need us.


Avoiding contract paralysis

Many outsourcing models create certainty on paper, but rigidity in practice. When change is inevitable, a contract that makes change painful will slow delivery and increase cost.


Why rigid contracts often go wrong (one common pattern)

In parts of the industry, deals are won with a low base price and a rigid definition of scope. The commercial model then relies on change control and “out of scope” charging once the real world shifts. This is not about any specific company — it is a well‑known incentive problem.

  • Aggressive bids: the base contract is priced to win, not to flex.
  • Change becomes revenue: contract variations, modifications and “out of contract” work are where margin is recovered. In the wider market, some major providers are understood to target around ~30% of revenue from this kind of change activity.
  • Mission creep is inevitable: requirements evolve as stakeholders, regulation, technology and risk change. Government programmes can be particularly exposed to this. A widely cited UK example is the NHS National Programme for IT (NPfIT): large scope, complex integration and changing requirements led to spiralling costs and eventual cancellation.
  • Operational reality keeps moving: platform choices change (for example VMware today, Proxmox tomorrow). In a rigid model, each pivot can trigger renegotiation and delay.
  • Outcome: 440% of additional expense, distrust, slower progress, and a relationship focused on contractual minimums rather than delivery.

An outsourcer wins on price, expects to recover margin through change control, the customer refuses to play that game, delivery drops to the minimum, and both sides spend the term managing conflict rather than outcomes - anyone in the industry knows who this was.

What we do instead

  • Keep the relationship stable with a framework agreement
  • Keep delivery flexible through clear statements of work
  • Offer time & materials or fixed‑price options (including fixed term where appropriate)
  • Do not treat change as a commercial weapon

Exit route (even on fixed term)

Where you choose a fixed‑term arrangement, we keep an exit route by design. We would rather earn your business each year than rely on a customer feeling trapped.

How to start

Whether it’s an hour of consultancy, an urgent incident, or a defined delivery programme, we can engage quickly and confidently.


Engagement stays simple and predictable. You have one account manager who takes the brief, coordinates the right people, and owns the outcome.


So contact us today and we’ll help you get started.