Overview
Sometimes the useful thing is an honest assessment
Not every engagement should be a build. If you have an environment that mostly works, a team that mostly manages it, and a specific problem you cannot get past, what you need is someone who has seen the problem before rather than a proposal for a rebuild.
- Independent reviewWe are not selling you licences and have no incentive to recommend more platform than you need.
- Written findingsA documented assessment with prioritised recommendations, not a verbal summary and an invoice.
- Realistic remediationRecommendations sequenced by risk and effort, so you can act on the first three without committing to all twelve.
- Support that is definedResponse times, scope and escalation written into the arrangement rather than left informal.
Architecture
Findings, ranked
Every recommendation is plotted by risk against effort, so you can act on the top-left corner this quarter without committing to the whole list.
What is included
How we help
Architecture review
An assessment of your current environment against your actual requirements, with findings and prioritised recommendations.
Governance design
Site provisioning, naming standards, permission models, retention and lifecycle policy — documented so it can be enforced.
Permissions audit
Mapping who can access what across your tenant, identifying broken inheritance and over-permissioned groups, and proposing a cleaner model.
Adoption support
Training, documentation and champion programmes for organisations where the platform is fine but usage is not.
Ongoing support
A monthly arrangement covering maintenance, small enhancements and administrator backup with defined response times.
Second opinion
Independent review of a proposal or design from another vendor, before you sign it.
In practice
What an architecture review actually produces
A review is typically one to three weeks depending on environment size. We interview the people who administer and use the platform, inventory the tenant, examine the permission structure and customisations, and test the specific problems you have raised.
The output is a written document: what exists, what is working, what carries risk, and a prioritised list of recommendations with an estimate of effort against each. Where something is genuinely urgent — an exposed permission, an unsupported dependency — you hear about it immediately rather than waiting for the report.
You are free to act on it yourself, hand it to another vendor, or engage us for remediation. The document is yours either way.
Questions
Common questions
Will you tell us if we do not need what we asked for?
Yes. It is a short-term cost to us and the reason clients come back.
Can you review work done by another vendor?
Yes, and we do so regularly. We assess against your requirements rather than against how we would have built it.
What does ongoing support cover?
Scope is agreed at the start — typically maintenance, minor enhancements, administrator support and defined response times for issues.
Do you offer training for our administrators?
Yes, tailored to your environment rather than generic platform training, and delivered against your actual configuration.