A contract tech lead for engineering and product teams
I join your team for the work that needs senior judgement: platform architecture, design systems, payment flows and AI features. Fifteen years across government, global platforms and startups, most recently leading the platform team behind a national publisher's subscriptions.
Tell me about your team and the problem. I reply within two working days, with an honest view on whether I'm the right fit.
Where I'm most useful
- Architecture your team can keep changing
- Frontend and service architecture, designed or reviewed with your engineers. Typed contracts, errors handled by design, and a migration path the team can follow without me.
- Design systems that reach production
- Figma tokens carried through to working components, so a design change ships without a re-implementation ticket.
- Security from the first commit
- Authentication, token handling and access policies designed in, with dependencies, secrets and code reviewed for vulnerabilities before release.
- Checkout and payment flows
- The flows where a bug costs revenue. Subscriptions, payments and back-office tools, built defensively and tested end to end.
- AI and data features
- LLM pipelines, knowledge graphs, maps and graph visualisation, shipped as product features rather than demos.
- A second lead for a stretched team
- RFC review, release planning and mentoring, and a technical voice for your product manager when scope and trade-offs need one.
One lead, backed by a team of AI agents
I work with a team of capable AI agents, tuned for quality, security and continuity. They draft, test and review alongside me, and keep the context of your codebase from one week to the next. I set the direction and make the calls, so the work is fast, decisive and accurate, and I stand behind every line that reaches your repository.
How an engagement runs
A first conversation
You describe the team, the product and the problem. I tell you plainly whether I can help.
A written plan
A short discovery, then scope, risks and a definition of done, agreed with engineering and product.
Work inside your team
Your repository, your rituals, your review process. Progress shows up in pull requests, not status reports.
A clean handover
Decisions recorded, docs written, and your engineers owning the code before I leave.
The name comes from 因, cause: the reason something gets built. I also keep room for non-profits and social enterprises, at rates a grant budget can carry. Read about my approach.