A method built to end,
not to renew itself.
Most consultancies are structured to extend the engagement.
Below process is designed so that — Quenora is structured to finish the assignment —
from the first diagnosis to the deliberate handover.
Six phases,
fourteen weeks, one handover.
Timelines shift with scope — these are indicative, not promises.
What does not shift is the phase:
diagnose before scoping, demonstrate before integrating, transfer before leaving.
- Phase 01 · FrameWeeks 1–2Find the real constraint
Exit condition A written position on what to build first — or a recommendation to build nothing.
We spend the first weeks understanding what actually happens, not what the process documentation says happens. That means sitting with the people doing the work. That first look is where the constraint nobody mentioned tends to surface.
- Phase 02 · FoundationWeeks 3–6The unglamorous layer
Exit condition Baseline evaluation scores to judge every change that follows.
The data joins, the permissions, the evaluation baseline. This is the layer that decides whether anything later reaches production, and it is the layer most pilots skip.
- Phase 03 · IntegrateWeeks 4–10Into what you already run
Exit condition A staged rollout running against real data in a non-production environment.
Engineering in short cycles against your real systems, with something demonstrable at the end of each. You see working software, not status decks. The person who scoped the work is the person building it.
- Phase 04 · ShipWeeks 10–12Under real change control
Exit condition In production, under your existing controls — no exceptions.
Into production under the same governance, review and release process as everything else you run — not beside it, and not on an exception.
- Phase 05 · ProveWeeks 9–12Against the agreed number
Exit condition A written result — including the uncomfortable version if that’s the truth.
Measured against the number agreed in Phase 01, using the evaluation harness built in Phase 02. If it did not move, that is what the written result says.
- Phase 06 · Hand overWeeks 12–14And then we leave
Exit condition You own it, you run it, we’re gone. That’s the definition of done.
Documentation, runbooks, architecture decision records, paired operation with your engineers, and a named owner. The engagement is not finished until your team can run it without us.
Four positions
we will not negotiate
We don't do it for you. We clear the way.
A rocket booster does not fly alone. A signal booster generates no signal. We attach to the mass you already have — your people, data, processes, market position — and make it go further than it could by itself.
No handoff between sellers and builders
The people in the room during scoping are the people writing the code. The industry standard of senior partners selling and junior staff delivering is where most of the disappointment in this sector comes from.
Honest timelines, stated early
If your deadline is not achievable we say so before the contract is signed. It costs us work in the short term and saves both sides a failed programme in the long term.
The engagement is designed to end
Success is your team running the system without us. We would rather be recommended than retained indefinitely, and the commercial model is built that way on purpose.