Our approach
Build the ones worth building
Scope implementation separately, with a clear decision before the build.
Nexus Advisory
Nov 13, 2026
A finding is the start of a conversation
The audit and implementation are separate decisions. A ranked recommendation helps you decide what is worth a closer look. It does not commit you to replacing your tools or commissioning every proposed fix.
Agree the scope
Doing the fixes is scoped and quoted separately. Implementation is priced in a written proposal after the audit, with your audit fee credited toward it. The fit conversation is the place to discuss what needs to happen next.
Products support the consultancy
Front Desk is our AI assistant, and The Client Portal has its own product destination. They sit alongside consulting services; they are not a reason to skip understanding the work. Both products are in development. Ask about availability and fit for your business.
Choose the next step
Keep the report if that is what you need. If a build is useful, discuss its boundaries first. Explore the products, read the current engagement path, or book a fit call.
What we look at
Start with the recommended change and the decision it is meant to improve. Define the boundary: what changes, who participates, what access is needed and how the result can be checked. A clearer handoff or an answer the business has checked may be the first useful change.
Include the failure path. What happens if an answer is missing, a request cannot be delivered or a person needs to take over? Agree how an unresolved check affects launch before authorizing production use.
Your artifact: the scope
The scope names the change, its responsible people, required inputs and the check for completion. Doing the fixes is quoted separately, with terms in writing before you sign. One-time work and any continuing plan are separate choices. A review finding does not by itself establish build timing or support responsibilities.
Example: scope outline
This is an example outline for agreeing work, not a signed scope or a promise that any product has passed acceptance.
- Purpose: the finding this change responds to and the expected useful result.
- Boundary: what is included and what needs a separate decision.
- Inputs and access: the records, content and permissions the agreed change needs.
- Responsible people: who builds, who supplies inputs and who approves production use.
- Completion check: the input, expected result and evidence that will show whether it works.
- Failure and correction: the human fallback, unresolved checks and person handling corrections.
- Handover: what you keep, who receives it and how acceptance is recorded.
- Continuing work: any separately agreed review rhythm, responsibilities and terms.
Use this outline to find an unanswered question before work starts. It is deliberately not filled with invented delivery dates or savings.
Who owns follow-through
Name the person responsible for the change in the written scope. Name the client input owner and the person who approves production use. Check the actual result before calling the work complete. Agree corrections, handover and any support responsibilities in writing. A portal screen alone does not show that delivery or acceptance happened.
Questions about implementation
Is implementation included in the readout?
No. The audit and implementation are separate decisions. Doing the fixes is scoped and quoted separately.
Is there one deadline for every build?
No universal build deadline is established by the service copy. The Customer Journey Audit clock does not apply to every build. Set the actual scope and terms in writing.
Who approves the result?
Agree who approves production use and what check applies before authorizing the build. Include how an unresolved check affects launch and who handles corrections.
Is implementation automatic?
No. Discuss scope, responsible people, review rhythm and terms if continuing help fits. How it works explains the choices after the report.