The Oryon method
You know what is approved, what is progressing and what comes next. The system is documented so another team can take over.
01
Describe what you want to improve, build or repair in everyday language.
An initial discussion with no commitment. The aim is to understand the real problem, beyond the first request. We ask the questions that can save money later.
02
Your needs become written, approved specifications: scope, deliverables and acceptance criteria.
A short, concrete document you understand establishes what will be done. Later changes go through priced amendments, so the scope does not drift.
03
Work progresses iteratively: you regularly see working versions.
Every stage is tested. Technical choices are documented as the work progresses. If something changes, you are told its impact on time and budget before it happens.
04
A planned launch: environment checked, backups in place and a rollback plan.
For server follow-up after launch, see our Linux management and maintenance scope.
Launch is prepared: a planned switch, performance checks in real conditions and training for the people who will use the system every day.
05
The system is followed up: fixes, improvements, monitoring and tested backups. Documented to last.
Maintenance is optional, with an agreed scope.
For software fixes and improvements, application maintenance explains how we take over code and deliver tested changes.
Maintenance is offered with a clear scope and remains optional. The code and documentation belong to you: you can take them to another provider or continue internally at any time.
Working principles
Technical decisions, procedures and access are written down. Work is not complete until it is documented.
Code delivery, a reproducible environment and a handover plan allow you to continue with the provider of your choice.
Slowness is explained through measurements and risk through an inventory. Decisions rely on facts.
The quote describes the work. Additional work is flagged and priced before it is carried out.
We say when a request needs reframing, when a solution already exists and when another kind of provider would be more suitable.
An initial discussion with no commitment.
Start step 01