Services
Five ways to work together. One engineer who has done each.
Most companies don't need more engineers. They need one senior person who can see the whole board and still pick up the keyboard. These are the five shapes that work usually takes — most engagements mix at least two, and the first call is where we pick.
- A week, on your team
- 2–5 days
- Typical engagement
- 3–12 months
- On site, hybrid or remote — world-wide
- Amsterdam
01
Strategy & scale-up
I audit your stack, team and roadmap, then write the plan: which platforms, in what order, with what people — and I stay to get it started.
Who it's for
Founders, CTOs and product leads choosing what to build next.
What you get
A document the board can read and the engineers will follow: platform choices, a sequenced roadmap, and the scaling work in order.
Covers
- Stack, team & roadmap audit
- Platform strategy
- Sequenced roadmap
- Scaling & performance
02
Tech lead & team leadership
I lead your mobile team from inside the codebase: planning, reviews, releases, one-to-ones, hiring — still writing code next to them.
Who it's for
Teams between leads, or growing faster than their processes.
What you get
Predictable delivery, stakeholders who get straight answers, engineers who grow, and a hiring pipeline that finds the right people.
Covers
- Planning & delivery process
- Code review & release
- Coaching & one-to-ones
- Hiring
03
Cross-platform mobile apps
I design and build native apps in Swift, and Kotlin where it's needed, from first commit to the stores' review.
Who it's for
Companies launching on any Apple and/or Android device.
What you get
A shipped app, one codebase shared across platforms wherever it pays off, and code your team can own.
Covers
- iOS, iPadOS, macOS
- tvOS, watchOS, visionOS
- Android (Kotlin)
- Swift, SwiftUI, Objective-C
04
Backend services & integrations
I build the backends-for-frontends and server-side services with Swift, plus the web and hardware integrations the app depends on.
Who it's for
Product teams whose app depends on services, hardware, or both.
What you get
The whole product shipping as one piece — not a client waiting on a server.
Covers
- BFFs & server-side Swift
- Vapor, Hummingbird
- Web & third-party integrations
- Bluetooth, NFC connectivity
- Embedded devices
05
Refactors & migrations
I move legacy code forward without stopping the release train: Objective-C to Swift, UIKit to SwiftUI, one tangled target to modules.
Who it's for
Teams whose codebase has outlived its architecture.
What you get
An incremental migration with tests and CI in place, the hardest slices done alongside your team, while features keep going out.
Covers
- Objective-C to Swift
- UIKit to SwiftUI
- Modularisation
- Test & CI foundations
How I show up
I embed, I don't hover.
Your tools, your rituals, your codebase. I join the team rather than advise it from the side, so the people you already have go further.
I write things down.
Decisions, trade-offs, and what I'd do differently — so the knowledge stays when I leave, and the next hire can read how we got here.
I plan my own exit.
Every engagement ends with someone on your side able to carry it. If that's a hire, I'll help you make it.
Marketing
Need the product to find its market, too?
Shipping is half the job. For the other half I bring in a marketing partner I've worked with for years — strategy, positioning, campaigns — so the app you launch also gets found. One team, one plan, no hand-off.
Covers
- Positioning & branding
- Go-to-market strategy
- Competitor analysis
- Content & short-form video
- Social & influencer campaigns
- Data-driven optimisation
What clients say
“His presence extended beyond the typical duties of a freelance iOS engineer — he was a leader. He helped drive positive change within the org and mentored folks along the way.”
