Custom engagement · About one month
From scattered systems to a documented target architecture
A scoped engagement of about one month in which we document how your identity, devices, network, servers, cloud services and data fit together today, rate the weaknesses, design where they should be, and lay out a phased roadmap with budget ranges.
Proposed price
Quoted after discovery
- SKU
- PC-ARCH-REVIEW-001
- Billing
- Quoted after discovery
Proposed pricing pending approval. Your final price is confirmed in a written quotation.
At a glance
- Product ID / SKU
- architecture-review / PC-ARCH-REVIEW-001
- Pricing basis
- Custom quotation after a discovery consultation; scope and price confirmed in a written statement of work
- Billing frequency
- One-time, with milestones as set out in the quotation
- Delivery method
- Remote and on-site workshops where available, with weekly check-ins over roughly four to five weeks
- Purchase mode
- Consultation required: a discovery call precedes any quotation, and nothing is sold online
- Eligibility
- Organizations of roughly 20 to 200 employees facing growth, mergers, a major refresh or repeated incidents
- Not included
- Implementing the roadmap, hardware or licences, and enterprise multi-cloud landing zones
What the architecture review delivers
Our single-area assessments answer focused questions. The architecture review answers the bigger one: given where the business is heading, is the overall technology design right, and what should change over the next one to two years? It is intended for organizations that have grown, merged, opened new locations or experienced repeated incidents, and now need a coherent plan rather than another round of fixes.
Over about a month we work with your leadership and any internal IT staff to document the current state across identity, devices, network, servers, cloud and software-as-a-service applications, data and backup, and security operations. We rate what we find, design a target state that fits your size and budget, and translate the gap into a phased roadmap. The engagement ends with an executive readout and documents you can use with any implementation partner.
Deliverables
Current-state architecture
Written documentation and diagrams of identity, endpoints, network, servers, cloud services, data flows and backup.
Findings register
Every weakness rated Critical, High, Medium or Low by likelihood and business impact, with supporting evidence.
Target-state design
A recommended architecture with the reasoning behind each major choice and the alternatives considered.
Phased roadmap and readout
A 12 to 24-month plan grouped into phases with indicative budget ranges and dependencies, presented in an executive readout.
Engagement scope
The statement of work sets the final boundaries. A typical review covers:
Typically included
- Stakeholder interviews with leadership, department heads and IT staff
- Identity and access design, including Microsoft 365 and Entra ID
- Endpoint management and security approach
- Network topology across sites, including remote access
- Server, storage and cloud service placement
- Backup, recovery and continuity design
- Software-as-a-service application inventory and integration points
- Weekly check-ins and a final executive readout
Not included
- Implementing any roadmap item
- Hardware, software and licence purchases
- Enterprise Azure, AWS or Google Cloud landing zones and complex cloud governance, which we refer to CloudArchitects.expert
- Custom software, AI agents or workflow automation design, which we refer to Mars Innovation Technology
- Penetration testing or legal and regulatory opinions
Prerequisites
- A discovery consultation and an accepted statement of work
- An executive sponsor who can make decisions and attend the readout
- A technical contact available for weekly check-ins
- Read-only or administrative access to systems in scope
- Existing documentation, contracts and recent assessment reports, if any
Who this is for
Growing organizations
Businesses of roughly 20 to 200 employees that have outgrown an ad hoc setup and need a deliberate design.
After a merger or new location
Organizations combining systems or adding sites and needing a single target architecture.
Smaller or narrower needs
Teams under about 20 people, or with one focused question, are usually better served by an assessment or a One-Day IT Consultation.
How scope and price are set
There is no fixed online price. Effort depends on the number of sites, systems and stakeholders, and on how much documentation already exists. After the discovery consultation we send a statement of work listing deliverables, workshops, milestones and price.
Where you have already purchased an assessment from us, such as the IT Infrastructure Health Check, those findings are reused and the quotation reflects the reduced effort. Implementation of the roadmap can be quoted afterwards, delivered by your internal team, or handed to another partner; the documents are yours.
Engagement timeline
Roughly four to five weeks is typical once the statement of work is accepted; it depends on stakeholder availability.
Week 1: Kickoff and interviews
We confirm goals, constraints and stakeholders, and gather access and documents.
Weeks 2–3: Current-state analysis
We document and diagram each area and build the findings register.
Week 4: Target design and roadmap
We draft the target architecture and phased roadmap and review them with your sponsor.
Week 5: Executive readout
We present the final documents to leadership and agree next steps.
Terms
Scope, price, milestones and terms are confirmed in a written statement of work after a discovery consultation and remain subject to business and legal approval. Budget ranges in the roadmap are indicative estimates, not quotations. Taxes are calculated on each invoice.
Frequently asked questions
Why can’t we buy this online?
The effort varies too much between organizations for a fixed price to be fair. A short discovery consultation lets us scope it accurately.
Do we have to use Podium Catchers to implement the roadmap?
No. The documents are yours and are written so any competent partner or internal team can act on them.
What if we are moving heavily into Azure or AWS?
For enterprise landing zones and complex cloud governance we refer you to our sister brand CloudArchitects.expert, and can coordinate with them.
How much of our team’s time does it need?
Typically a few hours of interviews in the first week, a weekly check-in with your technical contact and the final readout.
Talk through your architecture goals
Book a discovery consultation. We will confirm whether an architecture review fits and send a written statement of work.