Stage 4 · Service Project
Small teams Growing businesses — Projects work for both

Defined work,
fixed price.

A Service Project is where the Plan from your Briefing or Review gets delivered. Scope agreed in writing, cost fixed at quote stage, no day-rate creep, clean handover when it's done.

Scoped to your engagement · fixed-price quote

Projects don't get quoted off a sheet. Most start from a Briefing or Review where the work has been scoped properly — that's how we keep fixed prices honest.

Service-management work, scoped and shipped.

KHITServices is a service-management consultancy — so KHIT Projects are service-management work. Process rollout, service design, supplier transition, multi-provider integration, reporting and maturity uplift. Real outcomes from your Briefing or Review, delivered cleanly. The technical doing stays with your providers; we hold the agenda and run the change.

Process design & rollout

Designing and embedding the service disciplines that keep your operation running predictably. Documented to industry standard, trained out, and held in place with your providers.

Typical engagements

  • Embed Incident, Problem and Change disciplines with your IT support
  • Stand up a Major Incident process with post-incident review
  • Implement a lightweight risk register and CSI cadence

Service design & catalogue

Defining how technology service operates end-to-end — what's offered, who delivers what, how requests flow, where escalations land. The plumbing that makes everything else work.

Typical engagements

  • Build a service catalogue mapped to your providers
  • Design 1st / 2nd / 3rd line support tiers and the routing between them
  • Define an escalation matrix that actually gets used

Service transition

Moving service from one provider, contract, or premises to another without breaking it. Scoping, knowledge transfer, joint delivery, signoff. Independent throughout, because we're not the next provider.

Typical engagements

  • Manage a supplier-to-supplier transition with clean cutover
  • Onboard a new line-of-business service into your support contract
  • Coordinate the technology side of an office move end-to-end

Service maturity uplift

Assessing where your service delivery practice sits today and building it forward. Maturity assessments, capability gaps, structured Service Improvement Plans with measurable outcomes.

Typical engagements

  • Maturity-assess your service delivery and recommend role/process changes
  • Run a Service Improvement Plan against agreed KPIs
  • Build a Service Delivery Centre of Excellence inside your business

Multi-supplier integration (SIAM)

Where you have several providers, someone has to make them work as one service to you. SIAM is that someone. Cross-provider governance, joint delivery rhythms, end-to-end accountability without single-throat-to-choke risk.

Typical engagements

  • Implement a SIAM model across your technology partners
  • Stand up cross-supplier service-review meetings and reporting
  • Define ownership matrices for issues that span providers

Service reporting design

Most service reports tell you everything except what you actually need to know. We design the reporting layer that surfaces what matters — for the board, for ops, for the supplier review.

Typical engagements

  • Design a service performance report that surfaces what matters
  • Standardise reporting format across multiple providers
  • Build a stakeholder reporting cadence (board, ops, customer)

Service management, not technical delivery.

KHIT Projects are scoped service-management work. We coordinate, design, document, project-manage, and hold the agenda — but the technical hands-on work stays with your providers. Honest scope, no overreach.

  • Not hands-on technical implementation — we don't push patches, configure servers, or build things
  • Not software development or product engineering
  • Not 24/7 support or operational delivery — that's your IT support, not us
  • Not hardware procurement and physical installation (we'll coordinate, not deliver)
  • Not vague-scope retainers — every Project has a defined endpoint
  • Not a path to a software resale — we don't have one
  • Not a way to backfill a missing IT manager — that's VSDM
  • Not a fixed-price guess — every Project is quoted from a real Briefing or Review

Quoted in writing, paid in milestones.

Project pricing is genuinely variable — a one-day supplier renegotiation and a six-week service redesign are both Projects but they don't share a price tag. We won't anchor a number that wouldn't apply to your situation. We will quote in writing before any work starts.

Fixed-price quote
scoped per engagement · written before work starts

Cost is fixed at quote stage. No day-rate surprises, no scope-creep invoices, no surprise "we-found-something" emails. If scope genuinely changes mid-Project, we agree it with you before any extra work happens.

Typical payment shape

On Project Agreement signature30%
At an agreed midpoint milestone40%
On completion and handover30%

Smaller Projects (under a couple of weeks) often run as 50% upfront, 50% on completion. Anything more complex picks up a midpoint stage or two. The shape is agreed in your Project Agreement.

What's in the Project Agreement

  • Scope of work — what's in, what's out, in plain English
  • Fixed price for the agreed scope
  • Payment milestones — what triggers each invoice
  • Deliverables — what you walk away with at the end
  • Timeline — start date, end date, key dates between
  • Cancellation and refund terms (per our policy)
  • Who owns the output — you do, fully

The Project Agreement is signed by both sides. It's the document that governs the engagement — short, plain, and meant to be readable by anyone, not just lawyers.

From identified work to clean delivery.

Projects don't appear in isolation — they emerge from a Briefing or Review where specific work has been scoped. Here's the path end-to-end.

1

Briefing or Review

Specific work identified during your earlier engagement. We know what's needed.

2

Project scope

Scope agreed in writing — what's in, what's out, what done looks like.

3

Quote & Agreement

Fixed-price quote and Project Agreement. Both sides sign before any work starts.

4

Delivery

The work, run to schedule. Status updates against milestones. No surprises.

5

Handover

Documented output, knowledge transfer, sign-off. Optional onward route into Ongoing.

Projects are scoped from a Briefing or Review — there's no public booking link on this page.

Enterprise experience. SMB pricing.

Thirty years of running technology service for organisations that can't afford to get it wrong, applied to businesses that don't have a dedicated team.

Truly independent

We don't sell products. We don't take supplier kickbacks. We manage what you already have and tell you the truth about it.

Enterprise experience

Three decades of technology service management across financial services, public sector, transport and defence — applied at SMB scale.

No jargon

No acronyms, no overwhelm. Plain English recommendations — whether you're a small team or a growing business.

Fixed price

Quoted in writing before work starts. No day-rate creep, no surprise invoices.

Service Project FAQ

If yours isn't here, book a 15-minute chat.

Do I need a Briefing or Review before a Project?

For anything substantial — yes. Without a Briefing or Review, we're guessing at scope, and guessed-at scope produces bad fixed prices. Either we'd lowball it (and resent the work) or pad it (and you'd resent the bill). Neither helps.

For small, well-defined work — a single day's worth of consultant time on something specific — a 15-minute chat can be enough. We'll tell you which path your situation needs.

What size are typical Projects?

They genuinely vary — that's why we don't publish anchor prices. The smallest Projects we run might be a single day's consultant time on a specific deliverable (a contract review, focused procurement support, a defined process design). The largest are multi-week engagements spanning several modules of work.

Most fall in between. Your Briefing or Review surfaces what's actually in scope, and the quote follows from that.

What if scope changes mid-Project?

We agree it with you before any additional work happens. There are no surprise invoices, ever. If something genuinely emerges that wasn't in the original scope, we explain what we found, propose a scope change in writing, and you decide whether to add it. The original scope's fixed price doesn't change unilaterally.

If we hit something that's our problem — bad estimating, missed dependencies — that's on us, not on the bill.

Do you do hands-on technical work as part of a Project?

No — and we'd rather be honest about that than have you frustrated halfway through. KHITServices is a service-management consultancy. Our delivery is design, coordination, project management, documentation, training, supplier management, governance work. Real outcomes — but the technical doing (configuring, deploying, fixing) sits with your providers.

Most Projects involve close coordination with your existing IT support or other technical partners. We hold the plan; they execute the technical bits.

Can a Project lead into VSDM or Service Advisor?

Yes — and often does. A Project that hands over cleanly might leave you wanting ongoing oversight without another formal engagement. Either ongoing product can pick up from a completed Project.

The handover at Project end is the natural point to talk about whether ongoing makes sense — we won't pre-sell it during the Project.

How do payment milestones work?

For most Projects: 30% on signature of the Project Agreement, 40% at an agreed midpoint, 30% on completion. Smaller Projects often run 50/50 (signature/completion). Larger ones might pick up a couple of midpoints.

Each milestone is tied to something concrete you can see — a deliverable, a stage gate, a sign-off — not just a date. The shape gets agreed in your Project Agreement.

What happens if I'm not happy with the work?

Tell us, immediately. Most issues we hear about late were small enough to fix earlier and got worse from waiting. The midpoint milestone exists partly to surface this — if there's a quality concern, we want it on the table at midpoint, not at handover.

If there's a substantive disagreement, the Project Agreement sets out how it gets resolved. As a default, we'd rather rework or refund a stage than ship something neither side is happy with.

Who owns the output?

You do, fully. Documents, designs, processes, plans — all yours, with full rights to use, modify, or share with other partners. We don't keep "consultant copyright" over your improvement plans or governance frameworks.

The only exception is generic methodology — frameworks and approaches we use across many clients. Those remain ours; specific outputs for your business are yours.

Can I cancel a Project once it's started?

Yes. Each Project Agreement sets out specific cancellation terms based on the engagement shape, but the principles are in our Cancellation & Refund Policy: a free cancellation window before work starts, fair pro-rata for work delivered, and a clean handover of completed work.

We don't bill for time that hasn't been delivered.

Are Project sessions recorded?

Yes — sessions with a KHIT consultant are recorded as part of the engagement record. The recording lets your consultant focus on the conversation rather than scribbling notes, gives us accurate action capture for follow-up, and protects both sides if a question comes up later about what was agreed.

The detail:

  • Used internally for consultant notes and engagement follow-up only
  • Held only for the duration of your active engagement with KHITServices
  • Deleted when your engagement closes
  • Never shared externally without your explicit written consent
  • Subject to your full UK GDPR data rights — request a copy, request deletion, or ask us to stop recording at any point

Your consultant will reaffirm the recording at the start of every session. If you'd rather not be recorded, tell us — we'll stop the recording (we may take more written notes during the session as a result). Recording terms also appear in your Project Agreement.

Every Project starts with a Health Check.

Free, ten minutes. Routes you to the right Briefing or Review, where the Project itself gets scoped honestly. The Project then follows from real work, not a guess.

Start Health Check Book a 15-min chat