Adobe Commerce consulting
An architect for stores on Adobe Commerce or Magento Open Source, with 17 years on the platform and the Adobe Commerce Architect Master certification.
Who this is for
- Merchants running their store on Adobe Commerce or Magento Open Source
- Teams planning a version upgrade or a new storefront
- Stores that have become slow or hard to change after years of custom modules and extensions
- Merchants whose project with an agency or in-house team has stalled
What you get
A clear picture of your build
Custom modules, extensions, integrations and hosting mapped in one place, with the risks ranked by cost.
Platform decisions in writing
Upgrade or replatform, Hyvä or headless, extension or custom code, agency or in-house, each with its cost and one recommendation.
Faster pages on the store you have
Caching, indexing, database and theme work, measured before and after every release.
A stalled project moving again
The blockers found in the code and the backlog, then the next releases planned in order with estimates in hours.
How it works
First call
Talk
Weeks 1 to 3
Review
After the review
Deliver
In detail
Adobe Commerce and Magento Open Source can carry very large catalogs and order volumes, and they give a team many ways to change how the store behaves. After a few years most stores run dozens of extensions and custom modules, and some of the integrations behind them were never written down. Upgrades slip and pages slow down. Each change takes longer than its estimate, and nobody can say for sure what a release will break.
I work with merchants who run their store on Adobe Commerce or Magento Open Source and need one person who knows the platform from the inside to own those decisions.
The work covers the platform decisions and the engineering behind them. Each area has its own page with the details.
An architecture review maps your modules, customizations, integrations and hosting on one diagram and ranks what to change first by cost and risk. An audit and code review reads the code that runs in production and finds the extensions and custom code that will block your next upgrade, each finding with evidence and an estimate in hours.
For migrations and upgrades I list every module and integration with a decision to keep, replace or drop it. I rehearse the data migration against a copy of production and plan the cutover so search rankings survive. The same method covers version upgrades, including a move off Magento 1, and hosting moves to Adobe Commerce Cloud.
Performance optimization starts with the full-page cache hit rate, the indexers, slow database queries and the weight of the theme. Every fix is measured before and after its release, so you see what each hour bought.
Integrations connect the store to ERP, payment, subscription and fulfillment systems such as NetSuite, SAP, Stripe, Braintree, Zuora and ShipStation. I move slow calls out of checkout into message queues and make every call safe to repeat, so a failure at night does not leave stock or orders out of step by morning.
B2B and multi-channel work puts wholesale buyers and marketplaces on the same catalog and inventory as your own store. On Adobe Commerce that includes company accounts, tiered pricing, a separate B2B catalog and business checkout flows.
Storefront strategy compares a Hyvä theme with a headless build on PWA Studio or ScandiPWA. Each option is priced for the build and for the years of maintenance after it, and you get one written recommendation.
A project can also stall. An agency misses release dates, or an in-house team inherits code it does not trust. In that case I start from the code and the backlog, find what blocks the next release and fix that first. Then I set the code-review standards that keep the same problems from coming back.
If you need someone to own all of this month after month, I work as your fractional CTO. That means the roadmap, the architecture decisions, code review and vendor calls on a fixed allocation of days each month.
You get one person accountable for the technical side of the platform. Every decision comes with its trade-offs and an estimate in hours. Your team or agency gets standards it can keep following after I step back.
My depth on the platform goes back to 2009. From 2009 to 2011 I was a member of Magento Inc.’s original Expert Consulting Group. There I led an 11-engineer team on Easton-Bell Sports and a 4-engineer team on Longines for the Swatch Group, and I was on call for urgent escalations. From 2015 to 2023 I was Principal Adobe Commerce Engineer at Guidance, working on 8-figure-GMV stores such as The Great Courses, where typical page-load times came down by about half. Since 2020 I have owned the technical roadmap at Teabloom, including a dedicated B2B wholesale site on Adobe Commerce next to seven sales channels. Since 2024 I have led a three-engineer team at MarketNation on a deeply customized Adobe Commerce build for fundraising and donations. All 17 of my years in e-commerce have been on Magento and Adobe Commerce, and I hold the Adobe Commerce Architect Master certification.
The written plan from the review belongs to you, so your own team or agency can carry it out with or without me.
Questions
Do you work on Magento Open Source as well as Adobe Commerce?
Yes. All 17 of my years in e-commerce have been on Magento and Adobe Commerce, starting with Magento 1 in 2009. Reviews, upgrades, performance work and integrations cover both editions, and the first call is the same either way.
How do we start, and how long does it take?
We start with a 30-minute call about your store and what is not working. Most engagements then begin with a fixed-scope review of one to three weeks that ends in a written plan. After that I can deliver the work as a fixed-scope project or stay on with a monthly retainer.
Can you work alongside our agency or in-house developers?
Yes, that is the usual setup. I can lead the technical decisions and review the work your team or agency delivers, or I can take on parts of the work hands-on. Findings come with file references and estimates in hours, so the people who own the code can act on them.
What do you need from us to begin?
Read-only access to the repository and a staging copy, plus a short call about the problems you already know. Access to your monitoring helps if you have it. A review needs nothing more than that.
We are still on Magento 1. Where do we start?
We start with an inventory. Every custom module and integration gets a decision to keep, replace or drop, and the data is migrated in rehearsal runs against a copy of production. I started on Magento 1 Enterprise in 2009 and work on current Adobe Commerce builds today, so I know both ends of the move. I quote the migration after the inventory.
Related case study
−50 %Typical page load
Halving page-load times for an 8-figure e-learning store
Read the case studyRelated posts
My Adobe Commerce performance checklist
Twelve checks, in order, that show where most of the page-load time goes on a typical Adobe Commerce store before any code is written.
PerformanceWhen to go headless on Adobe Commerce
Headless pays off only with a frontend team and a budget for two applications. How I decide between Hyvä and a separate storefront on Adobe Commerce.
HeadlessHow I use AI coding agents on Adobe Commerce projects
Which Adobe Commerce tasks I hand to Claude Code, which I keep, and what changes for the merchant. Hooks, skills and MCP hold the agent to the same review process as any engineer.
AI