Architecture & decision engagement
Know what you own, what it costs, and what to fix first.
You get a verified map of the systems, a named owner against each, the decisions in priority order, and next actions with prices on them. Leadership or another provider can act on it directly.
PricePrice fixed after a short scope call.
Delivery10 business days, the review window this engagement runs to.
What you receive · illustrative sample
A review should leave you with a decision.
Illustrative findings record. Defined follow-on work can be quoted; unresolved dependencies carry assumptions and estimates.
| Finding | Decision needed | What you receive |
|---|---|---|
| Unclear system ownership | Confirm accountable owner | Owner/dependency register |
| Renewal or capacity choice | Compare equivalent options | Dated assumptions and cost basis |
| Priority correction | Agree scope and acceptance | Plan with responsibilities and next steps |
Meet the person responsible for delivery.
Alwatheq Zboun leads the agreed work. A sample shows the format; the statement of work defines your deliverable and acceptance checks.
Engagement context
When this engagement applies.
You inherited a Microsoft setup nobody can explain. That makes it hard to approve a budget, change provider, plan a move, or sign off a security plan.
Scope considerations
- Read-only review
- Named decision owner
- Microsoft 365 and Azure scope agreed before access is granted
The defined work
Engagement scope.
- 01
Tenants, subscriptions, administrators, connected applications and licensing are verified against the live environment.
- 02
Ownership gaps, unnecessary access and recurring cost without a clear owner are recorded.
- 03
Findings are ranked by operational risk, cost and decision urgency.
- 04
The next work is sequenced and priced so leadership or another provider can act on it.
Acceptance
Completion has an agreed standard.
Done when every critical in-scope system has a verified owner or an explicit ownership gap, and the agreed decisions can be made from the record.
The environment record is verified against the live tenant
Every finding has an owner and a severity
Findings are prioritized. Defined follow-on fixes can be quoted at a fixed fee; unresolved dependencies carry explicit assumptions and estimates
Commercial basis
Price, scope and timing are considered together.
Engagement price
Price fixed after a short scope call.
The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:
What determines the scope
- Number of tenants
- Applications authenticating through Microsoft 365
- Azure footprint and whether infrastructure is in scope
- Whether endpoints are included
Scope & responsibilities
The full engagement boundary.
Review the exclusions, required client participation, change controls and operational handover for this engagement.
Exclusions
- This engagement does not change production settings
- No fixes, penetration testing, or restore testing
- Implementation is quoted separately from the findings
Client responsibilities
- Provide read-only access to the systems in scope
- Nominate someone to answer ownership questions
Change and rollback method
- No production settings are changed during the review.
- Findings are supported by read-only evidence from the systems in scope.
- Any implementation requires a separately approved scope and change plan.
Operational record and handover
- Verified estate, administrator and application inventory
- Ownership and recurring-cost register
- Prioritized findings with named next actions
- Implementation options and fixed proposals where the work is defined
Before you commit
A clear first step.
You stay in control.
Start with the problem and the result you need. The initial fit conversation is free and does not require access to your systems.
Check client feedback on Upwork ↗Prefer to contract through Upwork? Contact Alwatheq there. Existing Upwork engagements continue through Upwork.
Who will actually do the work?
Alwatheq Zboun leads the scope, technical work and handover. If a specialist collaborator is needed, their role is agreed with you before work starts. Your proposal names the responsibilities and delivery windows.
What happens before you get access?
We agree the scope, fee and completion checks in writing. Access uses named accounts and only the permissions the work requires. Approved access is reviewed and removed at handover.
How do we know the change worked?
Your scope defines the pilot, test cases and acceptance checks. Results and exceptions are recorded. Recovery options and their limits are agreed before production changes; a failed check is addressed before the next approved stage.
Will we need an ongoing retainer?
A defined project can end at handover. Your team receives the agreed configuration records, runbook and walkthrough. Any limited support period is written into the proposal; ongoing support or additional work is a separate agreement.
Discuss this engagement
Put the scope in context.
Describe the problem, systems and deadline. Alwatheq will review the fit and the scope questions before preparing a written proposal.
Start the Ownership Review