How an engagement actually runs
Five stages, the same order every time, so you always know what comes next, what you will receive, and what we need from you.
Understand customer requirement
We start with structured discussions on your expertise, goals, and constraints, gathering the detailed insight that keeps every later decision grounded in your reality, not ours.
What we do
- Structured discovery sessions with your leadership and the people who use the systems today
- A review of your existing systems, data and documentation
- Mapping of goals, constraints, risks and how success will be measured
- Agreement on what is in scope and what is not
What you get
- A written summary of requirements and constraints
- A shared definition of success
- A prioritized list of the problems to solve
Your part: Make the right people available for discovery, and give us access to the systems and documents we need.
Propose strategy & solutions
We define the key solutions for operational optimization, scalability, and future-ready IT, mapping the BI and reporting metrics and automation opportunities that matter most.
What we do
- Options with their trade-offs, including doing less or buying instead of building
- A recommended architecture and technology approach
- Reporting, BI and automation opportunities mapped to your goals
- A phased plan with milestones and clear responsibilities
What you get
- A proposal covering scope, approach, phases and team
- A delivery plan with milestones
- Stated assumptions and risks
Your part: Review the proposal, challenge it, and decide which option and which phase to start with.
Build customer-centric solutions
We build with current technology and modular design so the system extends cleanly as you grow, with regular progress updates instead of a black box until launch.
What we do
- Delivery in short increments, with working software at each step
- Modular design so features can be added without rework
- Security and testing built into every increment
- Regular progress reviews and demonstrations
What you get
- Working releases you can see and test along the way
- Regular status updates against the agreed plan
- Documentation that grows with the system
Your part: Join the reviews, give feedback early, and make the decisions we raise.
Deliver & train
We deliver on time with a controlled rollout, and train your team to run what we've built, with documentation and a clean handover so you are never dependent on us to keep it working.
What we do
- A controlled rollout with go-live support
- Training for the people who will use and run the system
- Handover of documentation and operating procedures
- A planned transition into ongoing support, if you want it
What you get
- A production system running in your environment
- Trained users and a documented handover
- A clear handover into support
Your part: Name the owners, take part in training, and tell us what you need from support once you are live.
Maintain & improve
Go-live is the start of the system's working life, not the end of our involvement. We keep it secure and performing, and use real usage and feedback to decide what to improve next, so the system keeps pace with the business.
What we do
- Monitoring, patching and routine upkeep to keep the system secure and current
- Regular reviews of performance, usage and support requests
- A prioritized backlog of improvements shaped by how the system is really used
- Planned enhancements delivered in the same short cycles as the original build
What you get
- Regular health and usage reports
- A rolling roadmap of improvements
- Responsive support under an agreed plan
Your part: Share feedback from the people who use the system, and help us prioritize what to improve next.
The principles behind every stage
No black boxes
You see working progress regularly, not just at launch, so there are no surprises.
Workflow before technology
We map how work really happens before we choose any tools.
Modular by default
What we build this year can be extended next year without starting over.
Honest scoping
We tell you when a simpler or cheaper answer is the better one.
Security from the start
Access, data protection and logging are designed in, not added afterwards.
Frequently asked questions
Do we have to follow all five stages?
Most engagements do, because each stage reduces the risk of the next. For smaller or well-defined work we can shorten the first two, and some clients stop after delivery and run the system themselves, but we never skip the understanding stage.
How involved do we need to be?
Most involved in the first two stages, where your knowledge shapes the plan, and in the regular reviews during the build. We tell you up front how much of your team's time to expect.
How do you handle changes once the build has started?
Changes are normal. We assess each one for effort and impact, agree it with you, and adjust the plan, so scope moves deliberately rather than by accident.
How will we know how the project is going?
Through regular progress updates and demonstrations of working software, measured against the milestones in the agreed plan.
What happens after go-live?
We hand over documentation, train your team and agree a support plan. From there you can run the system yourselves, or keep us on for the final stage, maintaining and improving it as the business changes.
What does maintain and improve include?
Keeping the system secure and current through monitoring and patching, supporting your users, and working through a prioritized list of improvements based on how the system is really used. Scope and response times are agreed up front, so you know what is covered.
Can we start with just one stage?
Yes. Some clients begin with discovery and a proposal, then decide how to proceed. That leaves you with a plan you can use with us or without us.
Want to see how this applies to your project?
Tell us what you are trying to achieve and we will walk you through what each stage would look like for your project.