Platform Architecture
Modular-monolith commerce platforms with module boundaries enforced in CI, migrated off legacy stacks with every URL and ranking kept by design.
designed for zero SEO loss01 Commerce platforms · Business systems · AI & automation
I’m Amirali Yaghouti — a software architect and senior engineer. I take a business problem through architecture, production code and measurement: commerce platforms, CRM and customer operations, AI assistants, automation. Most of it is running today under real traffic, and I lead the 12-person team that operates it.
Based in Tehran. Built for businesses in Iran, Austria, Canada and the US.
Commerce platforms, CRM and operations tooling, AI assistants and automation — built to be measured, reversible and handed over.
02 From problem to production
Before any code changes, I find out how the thing actually behaves in production: which pages are slow, which routes are hot, where the database is under pressure, and where the team is working around the software instead of with it.
03 What I build
Six areas that keep showing up in the work: the platform itself, the identity and security around it, the AI on top of it, the money it moves, the speed it runs at, and the automation that keeps it operating.
Modular-monolith commerce platforms with module boundaries enforced in CI, migrated off legacy stacks with every URL and ranking kept by design.
designed for zero SEO lossFail-closed customer identity, REST shields, route allowlists, staged approval gates and threat-modelled boundaries around live commerce.
fail-closed by defaultCatalog-grounded AI sales assistants with OpenAI function-calling, vision and voice, released through staged-rollout safety gates.
grounded, gated rolloutAppend-only wallet and loyalty ledgers in exact integer money, proven with mutation testing before a single balance goes live.
4 money defects caught pre-releaseTTFB, cache layers, route pressure, query reduction and asset strategy with measurable before/after results.
61% lower PDP TTFBn8n workflows, Telegram and CRM bots, reporting pipelines and operational tooling — with human review where the decision matters.
human review where the decision matters04 By business
Six kinds of business these systems already run in, with the modules each one uses — and four they would move to as they are.
Running todayA live watch and jewellery store: catalogue and filters, checkout with phone verification, payments, back-in-stock and cart-recovery SMS, spreadsheet-driven price and stock operations.
Modulescatalogue filtersfull-page cachecheckout + OTPback-in-stockcart recoveryprice & stock syncbulk discountssimilar products
Running todayA B2B platform for a watch distributor: dealer catalogue as a PWA, assisted ordering, reseller approval, per-brand exports, and brand microsites reading one central catalogue.
Modulesdealer catalogue PWAassisted ordersreseller approvalbrand micrositesprice monitoringExcel exports
Running todayA pre-owned watch marketplace: seller intake, bench inspection, custody, reservation only against a confirmed payment, settlement — each step a state, each transition audited.
Modulesseller intakeinspection & certificationcustodyreservations & depositssettlementseller rank
Running todayA ledger-based loyalty club on a live store: points, tiers by spend, wallet, referral, birthday offers by SMS. Every balance is derived from an append-only ledger; money is an integer.
Modulespoints ledgerspend tierswalletreferraloccasion SMSmulti-channel earningoperator views
Running todayA repair and after-sales module inside the customer-operations system: intake opens the customer's account by phone, quotes are approved in the customer panel, deposits, technician sheets, a PIN at hand-over, price books that learn from history.
Modulesintakequotes & approvaldepositstechnician queuehand-over PINprice & battery books
Running todayAn operator app with eleven working queues, a commission report the page, the dashboard and the Telegram bot all agree on to the Toman, counter-sales import from accounting exports, a shop-phone call bridge, and one daily report to the owner.
Modulesoperator queueswin-backlead importcommission reportcall bridgeTelegram order cardsdaily digest
Nothing below is a claim of past work. It is the honest map of which running modules a business like this would start from.
05 Selected engineering proof
A concise look at systems built around bottlenecks, architecture, KPIs and commercial outcomes—not surface-level project cards.
A modular monolith for a watch and jewellery retailer moving off WooCommerce: pricing, stock, orders and payment as modules with typed interfaces, boundaries enforced in CI, and a migration designed to keep every URL and every ranking.
06 Engineering range
No single stack covers a commerce platform, the operations around it and the automation on top. This is the ground I work across — listed as range, not as a checklist.
Production commerce platforms end to end — PHP/WooCommerce and TypeScript/NestJS — with custom architecture, safe boundaries and operational controls.
Deep investigation of TTFB, cache behavior, database pressure, slow routes and hidden backend friction.
Business workflows that connect people, data, reviewed summaries and operational approvals without losing control.
Typed backend services, snapshot APIs and AI assistants that stay grounded in real business data.
Responsive, premium interfaces that make complex systems usable for customers, operators and managers.
Safer public surfaces, controlled routes, provider integrations and production-ready recovery logic.
Internal tools that reduce manual work and connect sales, service, operations and reporting.
Clear specifications, modular architecture, code review discipline and practical decision-making for non-trivial commerce systems.
07 How I work
Four steps, whether the work is a live store, a remote engineering team, or a business that needs one person who can connect a technical decision to what it does to sales and support.
At Javaherian Gallery I own the online platform and lead its engineering, and I direct a 12-person cross-functional online team — development, sales, SEO, CRM operations, product support, design and social — that turns platform decisions into daily commercial results.
Find out how it behaves under real load — slow pages, hot routes, checkout risk, API pressure, database growth — before touching code.
Design modular plugins, safe fallbacks, cache boundaries, data snapshots, admin controls and rollback paths.
Ship the modules, APIs, dashboards, workflows and automations — production-grade, behind flags, reversible.
Same metric, same traffic, before and after: TTFB, queue size, route pressure, report latency, manual work removed.
08 Ways to work together
Some businesses need a system configured and running on a known scope. Others need architecture and engineering for a problem that has no off-the-shelf answer. I do both, and they are priced and scoped differently.
Path 01
A2 is the configurable operational core I extracted from years of building real sales, CRM, automation and commerce tools. You get a known scope and a faster start, instead of a system designed from zero.
For teams that need a reliable operational foundation for customers, follow-ups and core workflows.
For teams that need automation, recovery workflows, segmentation and deeper operational control.
For teams that want governed AI inside real sales and operational workflows — not a chatbot bolted on the side.
AI in A2 does not own business truth. It works through governed tools and verified operational data.
Discuss scopeBuilt on Growth or AI Pro, with organization-specific architecture, deployment and integration scope: multiple companies or brands, ERP, POS and accounting integration, SSO, private or customer-hosted deployment, complex migration, custom connectors and reporting.
Add-ons such as retention, after-sales, supplier automation and product-content automation stay independent of the package.
Path 02
For problems that need architecture, a rebuild, a migration or an integration designed around your own constraints.
System audit, bottleneck analysis, integration and migration planning, risk analysis, and a technical roadmap you can act on.
Catalog, pricing, inventory, checkout and order flows, payment integration, admin operations, performance and technical SEO.
Customer records, lead workflows, assignment and SLA, operator tooling, attribution, recovery and reporting.
Assistants grounded in real data, tool-based LLM systems, messaging and workflow automation, management summaries.
REST APIs, adapters and connectors, ERP/POS/accounting integration, data synchronization, idempotency and retry design.
Performance diagnosis, cache and query analysis, background jobs, observability, error handling and release safety.
09 Work with me
I’m a good fit when the problem sits between engineering and the business: a platform that needs architecture rather than another plugin, operations that need tooling, or a decision someone has to explain to both the developers and the people running the shop.
A focused look at what you’re running now: architecture, performance, the risky parts of checkout and payments, API pressure, what could be automated — and a roadmap you can act on rather than file away.
11 Start the engineering conversation
Send the URL, the bottleneck, or just the business problem. You’ll get back a plain technical plan: what’s wrong, what I’d do, in what order, and what could go wrong.