— SERVICE / REVIEW
SaaS Architecture Review — what compounds
An architect's review of your SaaS — what compounds, what costs you, and what to fix first.
Two to three weeks of senior architectural review. A written report of the decisions that compound, the ones that cost you, and what to fix before the next round of growth — investor, customer, or feature.
- — Investment
- $2,000–3,500
- — Timeline
- 2–3 weeks
— Who it's for
Right fit when…
- — Your SaaS product is past launch and you're starting to feel the architecture in places.
- — You're approaching a fundraise, an acquisition, or a major release and want an independent technical read.
- — You're considering multi-tenant, internationalization, or another structurally heavy move and want a second opinion before committing.
- — You're not looking for a code review — you want an architectural read that names trade-offs, not bugs.
— Deliverables
What you get
- — A written report (15–25 pages) covering structural decisions, data model, multi-tenant readiness, security posture, observability, and operational risk.
- — A prioritized fix list: what to do this quarter, next quarter, the year after.
- — An honest section on what's working well — most reviews skip this; it's often the most useful part.
- — A 90-minute walkthrough call with you and up to two engineers.
— Process
How it runs
-
01
Discovery call
30 minutes. Fit check, scope, what kind of decisions you're trying to make in the next twelve months.
-
02
Repository access and interview
I get read access to the repo, the schema, and the runbooks. A 90-minute interview with your lead engineer or CTO.
-
03
Review week(s)
I read code, schema, infrastructure, runbooks, and any architectural documents you have. Async questions over Slack or email.
-
04
Report drafting
Written findings, prioritized fix list, and a section on what's working. Draft is yours to review before the walkthrough.
-
05
Walkthrough call
90 minutes. Q&A on the report, agreement on what to fix first, written notes after.
— FAQ
Honest questions
- What's the difference between this and a code review?
- A code review finds bugs and style issues. This finds structural decisions that compound — the multi-tenant boundary, the data model, the migration order, the deployment shape. Different layer, different value.
- Will you talk to my team?
- Yes. The 90-minute interview at the start, the 90-minute walkthrough at the end, plus async Slack or email during the review week.
- What if my SaaS is in a domain you don't know?
- I'm domain-agnostic on architecture. I've reviewed payroll, AI document platforms, dog daycare operations, and AI core platforms — what compounds in one compounds in another.
- Will you implement the fixes?
- Not in this engagement. The review is independent. Follow-up implementation work is a separate scoped engagement, including possibly the fractional architect retainer.
- Can I share the report internally?
- Yes. The report is yours. Most clients share it with their engineering leadership and use it to drive the next quarter's roadmap.
Want an architect's read of your SaaS before the next round of growth puts pressure on the wrong decisions?
Let’s talk.