Architecture review
A fixed-scope review of your code, hosting setup, data flows and integrations. It ends in a map of what you have and what to change first.
Who this is for
- Merchants facing a major build, upgrade or replatform decision, on Adobe Commerce or elsewhere
- New CTOs and engineering leads who inherited a store and need an honest picture fast
- Agencies taking over a codebase from another vendor
What you get
A map of the system as it is
Modules, customizations, integrations and hosting on one diagram, with who owns each part.
Risks ranked by cost
Every finding with its business impact and an effort estimate in hours, so you can plan a budget.
A roadmap for the first 90 days
The three to five changes to make first, in order, with the reasoning written down.
A walkthrough with your team
One session to go through the findings with your developers or agency, questions included.
How it works
Week 1
Discover
Week 2
Analyze
Final week
Present
In detail
Most online stores grow under deadline pressure. Each new promotion or warehouse adds a module or an integration, and the old ones rarely go away. After a few years nobody can say with confidence what talks to what, or which change will break checkout.
An architecture review gives you that picture before you spend money on the next big decision. I read the code, the configuration, the hosting setup and the integrations with your ERP, payment and fulfillment systems. Then I map how an order moves through the system, from checkout to the warehouse.
You get a short plan ranked by cost and risk. It says what to fix now and what to decide before the next project starts. Parts that work and cost little to keep stay off the list.
I started this work in Magento’s original Expert Consulting Group and do it today at MarketNation, on a deeply customized Adobe Commerce build.
We start with one week of discovery. I get access to the code and monitoring and talk briefly with the people who run the store. The whole review takes two to three weeks.
Questions
How long does an architecture review take?
Two to three weeks, at a fixed scope. Week 1 is discovery, with access to your code, hosting and monitoring and short interviews with the people who run the store. Week 2 is analysis. In the final week I present the report, the architecture map and the roadmap to your team.
What do you need from us?
Access to the code, the hosting setup and your monitoring. I also need short interviews with the people who run the store, so the review reflects how your business actually sells.
What do we get at the end?
A written report, a map of your system as it is and a roadmap for the first 90 days. Every finding comes with its business impact and an effort estimate in hours. The roadmap names the three to five changes to make first, in order, with the reasoning written down.
Can our developers or agency take part?
Yes. The review ends with one session where we go through the findings with your developers or agency, questions included. The review also suits an agency that is taking over a codebase from another vendor.
Related case study
3Engineers led
Leading a custom Adobe Commerce build for fundraising
Read the case study