Technical strategy
Architecture reviews, build-vs-buy calls, and a roadmap your team can execute.
// deliverables
Architecture reviews, build-vs-buy calls, and a roadmap your team can execute.
Role design, calibrated interview loops, and sit-ins on final calls.
Find where the team loses weeks, and change the ship-rate without adding headcount.
Agency and contractor selection, SOWs, and quality checks on what ships.
// process
Stack, team, backlog, velocity, known pains — written diagnostic at the end.
Architecture plan, hiring plan, and the priorities that unblock the team.
Weekly cadence across strategy, hiring, vendors, and selective hands-on work.
Recruit the right technical lead and hand over with context, not a cold brief.
// good fit
Non-technical founders who need a senior technical co-pilot.
Startups that have outgrown their first engineering hire.
Enterprises standing up new digital products.
Teams with a lead engineer but no senior architecture sanity check.
// further reading
// note · 5 min read
A word slipped onto a 1970s shampoo bottle doubled consumption. A 1956 gear ratio still runs your mornings. Defaults are where UX either serves you or quietly sells you out, and the snooze button is the clearest case of the second one.
read// note · 7 min read
Why a shampoo bottle is the clearest way to explain UI/UX to a developer, what the critical 0.05 seconds actually buys you, and the ten tools I lean on to bridge code and craft.
read// note · 7 min read
Affordance is the contract an interface makes with the human in front of it. Most software breaks that contract quietly, and blames the user.
read// also available
UX advisor. Audit, direction, and a plan you can ship