Advisory

What I do

I work with mobile teams whose codebase has outgrown the architecture it started with — where every feature costs more than the last one, releases have become tense, and nobody wants to be the person who touches the legacy module.

I am not a contractor who disappears into a backlog. I work alongside your team, on your code, and the goal is always that they can keep going without me.

Who it’s for

• CTOs who need an honest read on whether the mobile codebase can carry the next two years of roadmap.
• Mobile leads who know what the problem is but need external weight behind the argument for fixing it.
• Teams mid-migration — Swift 6 concurrency, SwiftUI adoption, or modularisation — that have stalled halfway.
• Scale-ups hiring fast, where onboarding a new iOS engineer takes weeks instead of days.

Engagements

• Architecture audit — a fixed-scope review of the codebase, delivered as a written report: what’s load-bearing, what’s rotting, what to do first, and what to deliberately leave alone.
• Migration plan — a sequenced, incremental plan for Swift 6 concurrency, modularisation, or SwiftUI adoption, sized so the product roadmap keeps moving.
• Ongoing advisory — a recurring half-day: design reviews, pairing on the hard parts, and a second opinion for your lead.
• Team workshop — hands-on training on Clean Architecture, testing strategy, or on-device AI, taught on your codebase rather than a toy project.

How it works

• 01

  Call. 45 minutes. You describe the situation, I ask the uncomfortable questions. Free, and sometimes it ends with me telling you that you don't need me.

• 02

  Scope. I send back a short written proposal — what I'll look at, what you'll receive, how long it takes, and what it costs. Fixed price.

• 03

  Work. I go into the codebase with your team, not around them. Findings are shared as I go, so nothing in the final report is a surprise.

• 04

  Handover. You get the written deliverable plus a working session with the team, so the decisions survive after the engagement ends.

What you get

Written deliverables your team can act on without me in the room, decisions explained with their trade-offs rather than asserted, and a plan sized to your actual constraints — because an architecture your team cannot maintain is not an improvement.