STATUS · ACCEPTING NEW ENGAGEMENTSARCHITECTURE REVIEW · INDEPENDENT PRACTICEREMOTE WORLDWIDENDA-FRIENDLY · TYPED REPORTS · NO DECKWARESTATUS · ACCEPTING NEW ENGAGEMENTSARCHITECTURE REVIEW · INDEPENDENT PRACTICEREMOTE WORLDWIDENDA-FRIENDLY · TYPED REPORTS · NO DECKWARE
TECHNICAL DEBT ASSESSMENT · SYSTEM DESIGN REVIEW

Your architecture has blind spots. I find them.

AGX Consulting specialises in technical debt assessment and system design review for engineering teams. I partner with CTOs and founders to pressure-test systems, surface latent risk, and produce decisions you can act on inside a single sprint — not a 90-page deck.

You get the expert. Not the junior.

Asiri Gunawardena

Asiri Gunawardena

Founder, AGX Consulting

LinkedIn →

I'm an independent architecture review consultant with over a decade of experience designing and reviewing complex platforms across fintech, gaming, and digital systems. I've led architecture at the department head level — owning decisions that shaped how platforms were built, scaled, and maintained. CTOs and engineering leads trust me because I've sat in the same seat they're in, made the hard calls, and know exactly where the risks hide.

AGX Consulting is built around two disciplines — technical debt assessment and system design review. I work with engineering teams to pressure-test existing systems, quantify and prioritise technical debt, and review system designs from the ground up — uncovering hidden risk and delivering recommendations clear enough to act on immediately.

Every engagement is run personally, end to end. No subcontracting, no juniors, no deck-driven deliverables. You get a written report — prioritised, defensible, and short enough to actually read.

Five formats. One discipline.

Every engagement ends in something written — a blueprint, a memo, a register of findings. No slideware, no recommendation theatre. The right format depends on where you are.

SVC · 01

Platform Architecture Design

Full end-to-end system design review and architecture for new platforms — from concept to blueprint. Ideal for founders and CTOs starting a complex build who want the system designed properly before a line of production code is written.

Engagement
Fixed project
Duration
2 — 4 weeks
Best for
Founders & CTOs starting a build
Output
Blueprint & decision log
SVC · 02

Architecture Review & Audit

A thorough technical debt assessment and system design review of an existing platform — identifying risks, gaps, scalability ceilings, and the debt that's quietly slowing your team down. A great first engagement that often leads to bigger work once the picture is clear on paper.

Engagement
Fixed project
Duration
1 — 2 weeks
Best for
Teams sensing limits ahead
Output
Findings & risk register
SVC · 03

Technical Due Diligence

Independent technical due diligence for investors or acquirers evaluating a technology platform before committing capital. A clear-eyed system design review covering the codebase, the team, and what you'd actually be buying.

Engagement
Fixed project
Duration
1 — 2 weeks
Best for
Investors & acquirers pre-deal
Output
DD memo · red-flag matrix
SVC · 04

Monthly Architecture Retainer

Ongoing access to senior architecture advisory on a fixed monthly basis. Covers reviews, guidance, team Q&A, and strategic input as the product evolves — a second pair of eyes always on standby.

Engagement
Monthly retainer
Cadence
Bi-weekly reviews · async Slack
Best for
Teams between major builds
Output
Written notes, on cadence
SVC · 05

Engineering Process Optimisation

A structured engagement to assess and improve how your engineering team works — covering delivery workflows, sprint cadence, code review practices, team structure, and development standards. The outcome is a leaner, faster, more consistent engineering operation.

Engagement
Fixed project
Duration
2 — 3 weeks
Best for
Teams shipping slower than they should
Output
Process audit & rollout plan

Three steps. Nothing baroque.

Every architecture review engagement runs the same way: a short call to see if it's the right fit, a written scope you can take or leave, then the review itself — an independent engineering second opinion, on a calendar, with a written deliverable at the end.

Step · 01
Scope

A short, confidential call to understand the system, the stakeholders, and the question worth asking. No obligation — you leave with a one-page memo either way.

  • 30 minutes, direct with me
  • One-page written scope memo
  • Mutual NDA on request
  • No follow-up sales sequence
Book scoping call →
The work
Step · 02
Review

The review itself. Code, infra, data, runbooks, the people on call — read carefully, in context, against an agreed brief. One written report at the end. No deckware.

  • Scoped against a written brief
  • Stakeholder interviews, on your calendar
  • Prioritised findings & 90-day plan
  • One written report, one readout
  • Post-delivery follow-up included
Start a review →
Step · 03
Follow-through

After the report, an optional standing advisory — a second opinion on designs, ADRs, and incidents while you act on the findings. Bi-weekly, written, async-first.

  • Bi-weekly written reviews
  • Async Slack for design questions
  • Quarterly, renewable cadence
  • Walk away with 30 days' notice
Continue the work →

Bring me the system. I'll bring the questions.

The fastest way in is a 30-minute scoping call. You describe the system and the worry; I describe how (and whether) I would review it. If we proceed, you have a written scope inside a week.

Sent direct to my inbox. No CRM, no sequence, no third-party tracking.
WORKING
Remote, async-first
WhatsApp