I join your engineering team for a few weeks, set up AI-assisted development around the process you already have, and leave you owning every file.
Past work infleet telematicsreal estate SaaSHR techrenewable energye-commerce
Services
Claude Code, Codex and the files around them, set up for your repos and your process.
An architect on retainer, without the cost of a full-time hire.
Pricing is scoped after the first call. Nothing is sold from this page.
How it works
One sprint with the team. I read the repos, sit in the rituals and watch how work flows in practice, not how it is described.
Output: a written plan of what to set up first.
Two to four weeks embedded. CLAUDE.md, skills, permissions, hooks, and the tooling the team is missing, tested on real tickets.
Output: files in your repos, used daily.
Your developers edit and extend everything. Claude, Codex or a local model, your choice.
Output: no dependency on me.
Fractional CTO, month to month, for the decisions that come after.
Optional.
Proof
# CLAUDE.md (excerpt)## Commandstest # full suite, runs offlinedeploy staging # prod only from CI ## Conventions- one git worktree per branch- never kill another dev server- hooks run lint + typecheck after every edit- tests before any "done"
mapMyCulture. Workplace culture analytics, live.
SafeMix. EU poison centre compliance for candle makers, in validation.
Both shipped solo at Tsarion, spec to production, with Claude Code and a full test suite.
“Dylan is way more than just a tech or a dev but a real partner. He brings structured out of the box ideas without being afraid of taking and owning decisions.”
“He brought his technical expertise to the table, with a complete understanding of the various elements involved to help us successfully complete our projects from scratch.”
Claude Code first, because it is what I run every day. Codex and OpenCode as alternates, local models where data cannot leave your network. Switching is a configuration change, not a migration.
It stays in your repositories. We agree on allowed providers and the permissions configuration enforces it. Secrets never go into prompts or into the repo.
Everything. CLAUDE.md files, skills, hooks, permissions, internal tools. Plain text in your repository, no dependency on me.
One sprint of diagnosis, then two to four weeks embedded. Longer when we build internal tooling. Fractional CTO is month to month.
Both. Remote from Dubai and Bali, on site in Belgium and the EU for the diagnosis days when being in the room helps.
Bring one repo and one process pain. You leave with what I would change first, whether or not we work together.
Book a 30 min call