Fractional CTO, Architecture Reviews and Code Rescue
I review, fix and lead existing software for founders and small teams: architecture and code reviews with a written report, hands-on fixes for the risky parts, and part-time technical leadership when you need a senior decision-maker but not a full-time CTO. I run the same checks on my own products. A test pass on a school management SaaS found six real bugs in code already called done, one of which let a school read another school's data. A cross-tenant test on a hospital platform led me to rebuild 235 database links so the database itself refuses links between hospitals.
Problems I solve
- Your product works, but every new feature seems to break something else.
- The developer who built it has left, and nobody fully understands the code.
- You're about to raise money or sign a big customer, and you need to know what's really under the hood.
- You need someone senior to make technical decisions, but not a full-time CTO.
- Your team ships fast with AI coding tools, and you're not sure what's slipping through.
What you get
- Architecture and code review with a written report: what's risky, what's fine, and what to fix first
- Security and data-separation checks, including tests that try to reach other customers' data
- A prioritised fix plan with effort estimates
- Hands-on fixes for the risky parts, made structurally so they stay fixed
- Part-time technical leadership: architecture decisions, code review and roadmap, about 20 hours a week
- Written documentation, so the next developer can pick the work up
Proof: work I've shipped
- Bicitra EMS
A multi-tenant School Management SaaS built for Bangladesh, phone-first.
- HMS: Hospital Management SaaS
An MVP of a multi-tenant hospital management platform, from the front desk to the ward to the accounts office.
I also deploy and run what I build. DevOps for startups →
Stack
- TypeScript
- Node.js
- NestJS
- Next.js
- PostgreSQL
- MongoDB
- Laravel
- Docker
- Playwright
How does a project with me work?
It starts with a call and a small paid plan, then the build runs in fixed-price milestones you can check yourself, and I deploy and support what I ship.
- 1
Call. A 15- or 30-minute call in your time zone to talk through what you're building and whether I'm the right fit.
- 2
Plan. MVP scoping ($400, about five days) for a new product, or an architecture review (from $750) for an existing one. You get a written plan and a fixed quote, and the plan is yours to keep. If you go ahead with the build, the scoping fee is credited against the first milestone.
- 3
Build. Fixed-price milestones, each one something you can click through and check. 30–50% upfront, the rest billed as milestones are delivered.
- 4
Launch. Production deployment with CI/CD, monitoring and backups, plus app-store release support if there are mobile apps.
- 5
Support. Optional maintenance from $750 a month, or server care from $150 a month per server.
Further reading
Questions
- What does an architecture and code review include?
- I read the code and look at the architecture, security, infrastructure, performance and technical debt. You get a written report: what's risky, what's fine, and what to fix first, with rough effort for each. It starts from $750. If it doesn't give you clear, prioritised actions, I revise it or refund the fee.
- Can you take over a codebase another developer built?
- Yes. I usually start with a paid review, so we both know what we're dealing with before we agree on the fix or build work.
- What is a fractional CTO, and do I need one?
- A senior engineer who makes the technical decisions for you part time: architecture, priorities, code review and the technical roadmap. It fits when you have a product and maybe a developer or two, but a full-time CTO would be too much. Part-time engineering or leadership starts from $4,500 a month for about 20 hours a week.
- Can you review code written with AI tools?
- Yes. I built a hospital management platform with an AI pair programmer, so I know where AI-written code tends to go wrong: it looks finished and passes the tests written alongside it. I check it with tests it can't bend, like running against a real database instead of mocks.
- What happens after the review?
- You keep the written report and the prioritised fix plan, whatever you decide next. I can then fix the riskiest parts myself, or stay on as part-time technical leadership at about 20 hours a week, from $4,500 a month. Or your own team can follow the plan, because it's written for the next developer.
Start with a conversation
Tell me what you're building, and I'll reply with questions or a next step. See how we can work together.
Or send the details →