Free assessment or paid assessment?
Free evaluation
It is used to understand the general problem, check if GXN can help and suggest a starting point. This is not a complete audit.
- Initial reading of the situation
- Key visible issues
- Possibly relevant intervention
- Proposed next step
In-depth assessment
It becomes useful when it is necessary to examine access, code, data, infrastructure or several scenarios before defining the scope.
- Current status and dependency
- Risks and priorities
- Options and compromises
- Roadmap and budget category
The project is progressing in visible stages.
Evaluation
You describe the situation with your words. GXN determines whether an initial orientation is sufficient or whether an assessment is necessary.
Situation · Issues · DirectorateAssessment
When facts must be established before quantifying, the assessment documents the current state, risks, dependencies and priorities.
Facts · Risks · PrioritiesRecommendations
The options are compared with their advantages, limitations and consequences. Changing nothing remains a valid option.
Options · Arbitration · DecisionProposal
The scope, exclusions, responsibilities, schedule and costs are defined before the intervention begins.
Scope · Responsibilities · CostsDesign
The structure, pathways, data or architecture are prepared according to the mandate. The decisions to be made are made visible.
Structure · Route · ArchitectureWeb development
The work progresses in verifiable stages. A finding that changes the scope is explained before being added.
Production · Visibility · ControlVerification
Functions, content, mobile, measurement, security and critical scenarios are tested according to the nature of the project.
Tests · Corrections · ValidationOnline
The transition is planned with backups, redirections, access, monitoring and a return plan when necessary.
Transition · Continuity · RecoveryOngoing support
Access, responsibilities and decisions are documented. The platform can then be maintained and improved without becoming a black box again.
Documentation · Monitoring · EvolutionClarity is part of the deliverable.
A digital project is not governanceable if management does not know where it is. Open decisions, risks, changes in scope and necessary validations are presented in understandable language.
The documentation is proportionate to the project. It must be clear enough to allow maintenance, transfer and continuity, without becoming a mass of documents that no one consults.
Responsibilities are named before the job.
GXN specifies what is part of the mandate, what depends on your team or an external provider, the required access and the expected validations. An unresolved dependency is a project risk; it must not remain hidden.
No unlimited development is promised. A new request is evaluated based on its impact on scope, cost and schedule before being integrated.
After going live, ongoing management can cover hosting, maintenance, security, monitoring and planned evolution.
See continuous management