Skip to content

How we deliver

From concept to business as usual.

Blacklight takes responsibility from the first business problem to a supported, working service. This page sets out each stage in plain English: what happens, what you receive and what you need to decide.

Three ways to work with Blacklight

  • The whole journey

    Blacklight takes responsibility from discovery to business as usual: analysis, design, delivery, adoption, go-live and support.

  • A defined part

    Blacklight takes a clearly bounded piece, such as discovery and design, a Dynamics 365 workstream or an integration, alongside your team or other suppliers.

  • Support and improvement

    Blacklight looks after a live system, including one someone else delivered, and keeps improving it against an agreed roadmap.

Phase 1

Shape the right solution

Understand the problem and agree what is worth doing, before money is committed to a build.

01

Discovery

Understand the business problem before anyone proposes a solution. Business analysts talk to the people who do the work, map the processes and systems involved, and agree with you what a good outcome looks like.

You receive

  • A clear problem statement
  • Current processes and systems mapped
  • Desired outcomes, agreed in writing

You decide

  • Is the problem worth solving now?
  • Who on your side owns it?
02

Requirements

Turn the findings into requirements people can check. Each one has a priority, so the most valuable work comes first, and acceptance criteria, so everyone knows how it will be judged.

You receive

  • Prioritised requirements in plain language
  • Constraints and assumptions recorded
  • Acceptance criteria

You decide

  • What is in scope, and what is not
  • What "done" means
03

Options and business case

Compare the realistic routes: configure a platform you already own, integrate existing systems, buy a product, develop a bespoke component, or improve what you have in phases. Each option is set out with its trade-offs, risks and rough cost.

You receive

  • An options appraisal
  • Risks and trade-offs for each route
  • A recommendation with reasons

You decide

  • Which route to take
  • Whether to start with a smaller first phase
04

Solution design

Agree how the solution will work: the architecture, the user experience, the data model, security and access, and how it connects to your other systems. Your IT and information governance leads take part in the decisions that affect them.

You receive

  • A solution design
  • Integration and data flows
  • Security and access model

You decide

  • Sign-off of the design
  • Data, hosting and security choices

Phase 2

Deliver it with confidence

Plan, develop, integrate and test in increments you can see, with changes managed in the open.

05

Delivery planning

Set out who does what, the milestones, the dependencies on your teams and other suppliers, the budget assumptions and the points where you will make decisions.

You receive

  • A delivery plan with milestones
  • Named responsibilities on both sides
  • Budget assumptions and decision points

You decide

  • Approval to start delivery
  • Who attends progress reviews
06

Build and integration

Develop and configure the solution in manageable increments. You see working software at regular demonstrations, not only at the end. When something needs to change, its effect on cost, time and scope is shown before you agree to it.

You receive

  • Working software at each demonstration
  • Regular progress reports
  • Change requests with impact assessed

You decide

  • Feedback on each increment
  • Approval of changes
07

Quality and acceptance

Plan testing from the start. The team tests functionality, integrations and security, validates migrated data, and supports your users through acceptance testing.

You receive

  • A test approach
  • Test results and migration validation
  • Support for user acceptance testing

You decide

  • Acceptance against the agreed criteria

Phase 3

Keep it working

Prepare people, go live safely and keep improving the service after launch.

08

Adoption

A system only works if people use it. Training, user guides and administrator documentation are prepared before launch, and the people who will own the system day to day are agreed.

You receive

  • Training for users and administrators
  • Documentation
  • An agreed operational owner

You decide

  • Who owns the system in business as usual
  • Training plan and timing
09

Go-live

Agree that the business is ready, plan the cutover step by step, and agree how to roll back if something goes wrong. The delivery team stays close during the first weeks of live use.

You receive

  • A readiness check
  • A cutover plan with rollback steps
  • Early-life support

You decide

  • Go or no-go
  • Cutover date
10

BAU and improvement

Move into business as usual under an agreed support arrangement. Maintenance keeps the system working through platform updates, monitoring covers the parts where it is agreed, and a prioritised roadmap turns user feedback into improvements.

You receive

  • An agreed support arrangement
  • Maintenance and updates
  • A prioritised improvement roadmap

You decide

  • Support scope
  • Which improvements come next

Proportionate by design

Not every engagement needs a programme.

The stages are a checklist, not a bureaucracy. A change to one form in a live system may need a short conversation, a demonstration and a sign-off. A new case-management system across several departments needs a full plan, a steering group and formal acceptance.

The level of process is agreed with you at the start and reviewed when the work changes. The aim is the same either way: you know what is happening, why, and what comes next.

Governance

Know where the project stands. Understand every decision.

Governance at Blacklight is practical. Each arrangement below exists so you can see progress, understand decisions and avoid surprises.

  • Clear ownership

    A named delivery lead at Blacklight and a named owner on your side. Responsibilities for decisions, testing, data and sign-off are agreed at the start.

    You always know who to ask.

  • Scope, priorities and acceptance

    Agreed scope, priorities in order of value, and acceptance criteria set before work starts.

    "Finished" means the same to both sides.

  • Risks, assumptions, issues and dependencies

    One shared log with owners and actions. Dependencies on your teams and other suppliers are named early.

    Problems surface while they are small.

  • Progress and demonstrations

    Regular progress updates in plain language and demonstrations of working software.

    You know where the project stands.

  • Budget visibility and change control

    Spend tracked against plan. Every change is assessed for cost, time and risk before you agree to it.

    No surprises on the invoice.

  • Architecture, security and data decisions

    Significant decisions are recorded with the reasons and the alternatives considered, and agreed with your IT and governance leads.

    You understand why the system works the way it does.

  • Testing, acceptance and release readiness

    A test approach agreed early, supported user acceptance testing, and a readiness check before every release.

    Releases happen when they are ready.

  • Escalation and operational handover

    A known escalation route on both sides, and a planned handover of ownership, documentation and support before go-live.

    Nothing falls between the project and BAU.

Good governance supports good decisions. It does not, on its own, make a system compliant with any regulation. Where regulatory requirements apply, they become requirements and acceptance criteria, and your compliance owners stay part of the decision.

AI in delivery

AI-assisted work. People stay accountable.

The team uses AI-assisted tools where they help: summarising discovery notes, drafting documentation and test cases, and supporting code review and development. They can speed up parts of the work.

They do not replace judgement. A named person is responsible for every design, line of code, test and document, and reviews any AI-assisted output before it is used. Security, quality and acceptance decisions stay with people.

Your data is used with AI tools only where your engagement allows it. Model choice, data handling and controls follow the requirements agreed with you.

AI in customer solutions →

Questions about delivery.

Does every project go through all ten stages?

Every project touches each stage, but the effort varies a great deal. For a small enhancement, discovery may be one conversation and go-live a short checklist. A multi-department implementation needs each stage in full. The level is agreed at the start.

Can we bring you in part-way through?

Yes. Blacklight can pick up a project at any stage, take a clearly defined part of a larger programme, or take over support of a live system. The first step is a review of where things stand.

How do we know what it will cost?

Discovery is scoped and priced before it starts. Delivery is estimated from the agreed requirements and design, with budget assumptions written down. If something changes, you see the effect on cost before you agree to it.

Who owns the software and documents?

You do. The systems Blacklight develops for you, and the documentation that goes with them, are yours. That stays true if you later move to a different supplier.

What happens after go-live?

The project moves into business as usual under an agreed support arrangement, with maintenance, monitoring where it is part of the agreement, and a prioritised improvement roadmap. Support hours and response arrangements are set in your support agreement.

Talk to us

Start with the problem.

You do not need a specification. Tell us what is not working and what good would look like, and we will suggest a sensible first step.

Get in contact