Our Process
A clear, collaborative, and proven approach that keeps your project on track from day one — with no surprises at handover.
Why Process Matters
Good engineering delivery isn't just about working hard. It's about ensuring the right things get done — in the right order — with the evidence to prove it.
Every successful engagement depends on:
- ✓Defining what success looks like — before any work begins
- ✓Making risks visible early — so you can make informed decisions
- ✓Capturing evidence and documentation — not just doing the work
- ✓Handing over outputs that can be maintained — by someone other than us
This page describes how we do that.
A Predictable Process
Six stages. Clear outputs at every step. No surprises at the end.
Fit Check & Discovery
›Before we scope anything, we make sure we're a match.
We start with a structured conversation to understand your goals, existing constraints (timeline, budget, team size, environment), and whether HNES is the right fit for your challenge. This isn't a sales call — it's a mutual due-diligence step. We want to walk away knowing exactly what success looks like for you, and you should know exactly how we plan to deliver it.
Blueprint / Audit Sprint
›When scope is unclear, a paid sprint builds the map.
If your problem is well-defined, we move straight to design. But when scope is ambiguous — which is more common than people admit — we recommend a focused sprint to produce a usable plan before committing to a full engagement. This de-risks the project for both sides and produces a deliverable you own regardless of what comes next.
Design & Planning
›Requirements, architecture, and a plan you can hold us to.
We translate your goals into written requirements with measurable acceptance criteria. Architecture decisions are documented — not just made — so you understand the trade-offs. We build a milestone plan with defined output at each stage, giving you clear visibility and review points throughout the engagement.
Build & Integration
›Staged delivery. Work stays reviewable and testable throughout.
We deliver in stages — not as a big-bang release at the end. Each stage produces reviewable, testable output that you can inspect and give feedback on before we proceed. This keeps risk low, catches misalignments early, and means you're never waiting months for a first look. Integration with your existing systems or teams is planned explicitly, not treated as an afterthought.
Validation & Iteration
›Evidence, not assertions. Risk reduced before handover.
We don't ask you to trust that something works — we produce evidence. Test notes, validation reports, and documented known limitations are captured at this stage. Where issues are found, we iterate before declaring a milestone complete. Any known edge cases or limitations are explicitly documented, not quietly left for someone else to find.
Documented Handover
›Everything you need to own and maintain what we built.
The final stage isn't an afterthought. We produce structured handover documentation: repositories with clean build and run instructions, CAD/manufacturing files where applicable, a runbook or operating guide, and a summary of known limitations and future considerations. We offer an optional walkthrough call to make sure your team can confidently pick up everything we've handed over.
Quality Gates
Four formal gates — each with a defined evidence checklist — that must be passed before work progresses.
Requirements & Acceptance Criteria
No work progresses to design until requirements are written and agreed. This gate ensures both parties are aligned on what "done" looks like.
Evidence Checklist
- ✓Written requirements brief signed off by client
- ✓Acceptance criteria defined per milestone
- ✓Constraints and non-requirements documented
- ✓Stakeholder sign-off recorded
Design Review + Risk Register
Before build begins, architecture and design decisions are reviewed. Risks are made explicit and entered into a living register.
Evidence Checklist
- ✓Architecture / design notes documented
- ✓Key design decisions recorded with rationale
- ✓Risk register created and reviewed
- ✓Mitigation actions assigned
- ✓Client or peer design review completed
Integration & Validation Evidence
Integration and testing results are captured as evidence—not assumed. Known limitations are written down before handover is considered.
Evidence Checklist
- ✓Test notes and results documented
- ✓Integration verified in target environment
- ✓Validation evidence reviewed by client
- ✓Known limitations explicitly recorded
- ✓Outstanding issues triaged and accepted/resolved
Handover Checklist
Handover is a structured gate, not an email with attachments. Every item on this checklist must be ticked before the engagement closes.
Evidence Checklist
- ✓All documentation delivered and reviewed
- ✓Repositories and file packs transferred
- ✓Runbook / handover notes complete
- ✓Optional walkthrough call completed
- ✓Client sign-off on handover received
How We Collaborate
Good delivery depends as much on communication structures as on technical skill. Here's how we keep your project running smoothly.
Communication Cadence
Scheduled check-ins at each milestone boundary. You always know when the next touchpoint is — we don't go dark for weeks at a time.
Responsibilities & Interfaces
Roles are defined upfront. We document who is responsible for input, who reviews, and who signs off — on both sides of the engagement.
Decision Points & Approval
Key decisions are flagged in advance and given a clear approval deadline. We don't let undefined decision turnaround stall delivery.
Change Control
Scope changes are documented as formal change requests. We assess impact on timeline and cost before proceeding — no silent scope creep.
What You Receive at the End
A structured handover — not just a final email. Every item below is expected as standard.
Code Repositories
All source code with clean build and run instructions. No mystery commands, no missing dependencies.
CAD & Manufacturing Files
Native and export formats where applicable — fully dimensioned and ready for fabrication or review.
Test Notes & Evidence
Documented test results and known limitations. You know what was tested, how, and what was found.
Documentation & Runbook
Operational guides, system overviews, and maintenance notes — written for the person who takes it over.
Optional Walkthrough Call
A structured session to walk your team through everything handed over — questions answered in real time.