Implementation and oversight
Implement the agreed changes, with a clear scope and handover.
Implementation & Architecture Oversight
If the problem and the finish line are already clear, AZ Innovations scopes the implementation directly. Complex or uncertain work gets a separate planning engagement only where a responsible fixed price cannot be set from a short scoping call.
Two ways in
Which one applies to you
The default
Scope the implementation directly
Most work goes this way. A short call establishes the trigger, the finish line, the access and the dependencies, and the implementation is quoted as one fixed scope. Nothing is billed for the call.
You are here when
- The problem is already identified, even if the fix is not designed yet
- There is a deadline, a renewal, an audit, or a vendor exit driving it
- The environment is one tenant with no active incident or migration in flight
- Someone on your side can approve a change window
The exception
Agree a separate planning scope
Used only where genuine complexity makes a responsible fixed price impossible: multiple tenants, public folders, hybrid Exchange, compliance holds, a third-party archive, unusual identity dependencies, or unresolved ownership. The plan is bought on its own and the implementation is quoted from it.
You are here when
- A fixed implementation quote would be guesswork rather than judgment
- The dependencies have to be counted before anything can be committed to
- Several destinations are still genuinely open
Delivered work
See a documented implementation
Migration rescue
Before
A file migration to SharePoint required investigation of source-to-destination differences and user access issues.
After
The handover package contains an as-built, validation reports, comparison scripts and recorded exceptions. These support a documented reconciliation process; they do not establish that every source file was recovered.
Anonymized client engagement
Follow-on only
Fractional Architecture Oversight
Scheduled architecture review for a business that needs continued technical judgment after the delivery work is complete.
Price fixed after a short scope call.
Three-month initial term. Offered after a delivered engagement.
When it applies
IT ownership left with a key person, or the environment needs someone accountable for architecture decisions without a managed-IT contract.
The named outputs
- One scheduled monthly architecture review
- Review of up to two planned changes, designs, or vendor proposals per month
- A written decision log and recommendations
- A quarterly posture and roadmap review
What it is not
Managed IT, ticket queues, unlimited email or chat, help-desk work, continuous monitoring, emergency response, same-day availability, or production implementation. Implementation is separately scoped and priced. Asynchronous requests are acknowledged within two business days.
Talk About Architecture Oversight →How this is priced
Each engagement describes its scope and price basis on its service page. Where a fee is not published, it is quoted after scope and dependencies are confirmed. There are no prepaid hours, no metered consulting clock, and no managed-IT contract you cannot leave. The scope and the price are agreed in writing before any access is granted.
Where an engagement genuinely cannot be fixed-priced from a scoping call, the planning is bought separately, and the page selling it says so plainly. The planning fee is billed on its own and is not credited against the implementation.
See every engagement and what it costs →Describe what needs to be working differently
A reply comes within one business day with the most direct next step, or a clear answer that AZ Innovations is not the right fit.
Get a Fixed Price in Writing →