Architecture audit
An architecture audit before you sign off on a rewrite
In five business days I review your store and answer one question: what to change, in what order, and what it will cost. Fixed scope, fixed price, written report.
Good fit if
- A vendor or your own team wants to rewrite the store, and you want a second opinion before you sign.
- Your Bitrix, Laravel or PHP store is slow, and nobody can show you exactly where.
- You're planning a redesign or a headless move and don't want to lose search traffic.
- You're switching vendors and want to know what you're being handed.
- A new CTO or an investor needs a technical picture of the platform.
What the audit is not
I don't fix things or write code during the audit. If I find something critical, like an exposed vulnerability, I'll tell you the same day. And I'm not selling a rewrite. If the system is fine and the problem is process, the report will say so.
What's included
System map
Storefront, backend, ERP and warehouse, CRM, payments, delivery, search. Who owns what and where the source of truth is.
Bottlenecks with evidence
Profiling, slow queries, logs, speed metrics. Numbers from your production, not opinions.
Risk map
Which pages make money, which URLs and SEO signals must survive, which integrations cannot stop for even a day.
A call on each major component
Keep, move or replace, with reasons.
First stage
Boundaries, acceptance criteria, an estimate range and a rollback plan.
Report and call
A 15–25 page report and a 60–90 minute call to walk through it with you and your team.
How it runs
- 1
Day 0
Brief, access, contract and NDA.
- 2
Days 1–4
Code, infrastructure, data and metrics. A short call with your developer if needed.
- 3
Day 5
Report and walkthrough.
What I need from you: Read access to the repository and server (or log exports), analytics access, and one or two hours from someone who knows the system.
Timing and price
- Timing
- Five business days
- Price
- Price agreed before we start, after the brief
Scope is fixed at the brief. Once we start, the price doesn't change.
Proof
Proof
A 28,000-SKU catalog: Next.js on top of 1C-Bitrix
The PHP backend stayed in place with orders, pricing and integrations. The storefront and search moved to Next.js and Elasticsearch, and the SEO structure carried over.
Read the case studyQuestions
- What if five days isn't enough?
- Scope is fixed at the brief. If the system is large, say several storefronts or a custom ERP, I'll tell you before we start and the price will reflect it. Once we start, the price doesn't change.
- Can you do it without code access?
- Yes, but the conclusions are weaker: external metrics, HTML, APIs and a conversation with the team. I'll flag which findings are hypotheses.
- Does the audit commit me to anything?
- No. The report is yours to hand to any team.
You work with me
Ivan Ponamarev, senior full-stack engineer, 10+ years in production. You talk to the person who makes the technical decisions and writes the critical code.
Show me the system, I'll show you the risks
Describe the store in a few sentences. I reply within one business day and suggest a time to talk.