Services
What I Deliver
Hands-on senior software engineering and practical AI enablement: production code with tests, workflows with guardrails, and adoption that lasts after I leave.
Senior Software & Full-Stack Engineering
Hands-on senior engineering: APIs, microservices, full-stack features, payments and integrations, delivered through pull requests with tests and CI.
Teams that need a senior engineer who owns features end to end: Java and Spring Boot backends, TypeScript and Node.js services, React and Next.js front ends.
The roadmap is bigger than the team, and new people slow things down unless they work independently, write tested code and make sound design decisions from day one.
I join your team as a senior engineer and ship. I design the change, write the code and the tests, review my colleagues' pull requests and leave the codebase cleaner than I found it. I use AI coding assistants with discipline: they speed up the typing, while tests, review and design keep the quality. Having led agile teams and a SAFe release train, I also help with refinement, slicing and cross-team dependencies.
Key Outcomes
- Features shipped end to end, from design to production
- Well-tested code, with automated tests running in CI
- Clean APIs and sound design decisions
- A senior reviewer and mentor inside the team
- An engineer who has led Scrum, Kanban and SAFe, and helps the team plan and flow better
AI-Assisted Engineering Enablement
Hands-on rollout of Claude Code and GitHub Copilot across teams, typically over 12 weeks, with working agreements, quality guardrails and clear adoption signals.
Engineering leaders and teams rolling out Claude Code, GitHub Copilot or other AI coding assistants beyond a first pilot.
Licences are bought, but usage is uneven. Some developers love the tools, others do not trust them, and nobody can show whether quality and delivery actually improved.
I work inside your teams, in the code and in the workflow. Together we set up repository instructions and reusable skills, agree where AI helps and where it needs a human, add review and test guardrails, and track adoption and quality signals so leadership can see what changed. The goal is everyday, disciplined use, not a one-off demo.
Key Outcomes
- Consistent, everyday use of AI coding assistants across teams
- Shared prompting patterns, repo instructions and reusable skills
- Review and test guardrails that keep code quality intact
- Adoption and quality signals leadership can act on
Related Case Study
AI-Assisted Development EnablementAgentic Workflow Design & Delivery
Design and build of agentic, MCP-enabled workflows with human-in-the-loop approval, evals and cost budgets built in from day one.
Product, engineering and delivery teams with repetitive, multi-step work that an AI agent could prepare, with people still deciding.
Teams try agents in isolation, without evals, budgets or approval steps. The demos look great, and then nobody trusts the output in real work.
I map the workflow, decide what the agent may do on its own and where a person must approve, connect the tools through MCP, and add evals, logging and cost budgets. The result is an agent your team can inspect, trust and improve, with a person accountable for every output.
Key Outcomes
- Less manual preparation and repetitive work
- Human approval gates at decision-critical points
- Evals, logging and budgets that make agent behaviour inspectable
- Reusable agent skills your team owns and improves
Related Case Study
Agentic AI Enablement for Agile DeliveryAI Adoption & Governance at Scale
An adoption playbook and lightweight governance for AI in software delivery: usage policies, guardrails, AI literacy and the metrics to steer by.
CTOs, heads of engineering and AI adoption leads who need AI usage to be safe, measurable and consistent across many teams.
Teams adopt AI tools team by team, with different rules and no shared picture of risk, cost or value. The EU AI Act now also expects AI literacy for staff who use these tools (Article 4).
I help you set the rules of the road once and roll them out across teams: which tools and data are allowed, where human review is required, how to train people (including AI literacy under the EU AI Act), and which signals show that adoption is working. Governance stays light enough that teams keep moving.
Key Outcomes
- One adoption playbook instead of team-by-team experiments
- Clear usage policies and guardrails for AI in delivery
- AI literacy for engineers, product people and leaders
- Metrics that connect AI usage to delivery and quality
Related Case Study
AI-Assisted Development EnablementHands-on AI Workshops & AI Literacy
Interactive workshops where people practise with Claude Code, Copilot and agentic workflows on their own work, and leave with habits they use the next day.
Engineering teams, product organisations and leadership groups that need to learn AI tools by using them, not by watching slides.
Passive AI training does not change habits. People nod along, return to work and keep doing things the old way.
Every session is built around doing: participants work on real tasks from their own backlog, compare results and agree on team practices. I use participation-first methods (Training from the Back of the Room, Liberating Structures) so even large groups stay hands-on. Sessions run from a 5-person team to 50+ people, for engineers, product people and leaders.
Key Outcomes
- Hands-on practice on real work, not demos
- AI literacy that meets EU AI Act expectations
- Team agreements on how and when to use AI
- High engagement, from small teams to 50+ participants
Related Case Study
AI-Assisted Development EnablementDelivery at Scale for AI Programmes
Release-train-level delivery leadership for AI programmes, drawing on my experience coordinating 10+ teams and planning events for 50+ people.
Organisations running AI initiatives across several teams that need planning, alignment and delivery to work together.
AI initiatives stall between pilot and scale: dependencies across teams, unclear ownership and no shared plan.
I bring the delivery-at-scale toolkit (joint planning, dependency management, stakeholder alignment from executives to engineers) to AI programmes, so pilots turn into working capability across teams. Because I am an engineer first, I can also challenge technical decisions and surface risk early.
Key Outcomes
- A shared plan from pilot to scale across teams
- Earlier visibility of dependencies and risk
- Alignment between leadership intent and engineering reality
- Predictable delivery of AI initiatives
Engagement Models
How We Can Work Together
Every engagement is designed around your context and goals โ not a fixed retainer or a generic statement of work.
Advisory + Implementation
I operate across both โ setting direction and staying for the execution. No handoff from strategy to a junior team. Senior thinking, delivered all the way through.
Fractional AI Enablement Lead
Ongoing AI enablement leadership on a fractional basis, for organisations that want a senior lead for AI adoption without a full-time hire.
Workshop-Led Engagement
Structured around a series of high-value workshops โ alignment, design, enablement, or retrospective โ with clear outputs and next steps after each session.
Partner-Delivered Enterprise Engagements
Available to boutique consulting firms and AI practices that need a hands-on AI enablement lead for enterprise client work.
Remote-First, Structured Collaboration
All engagements can operate fully remotely with structured async and synchronous collaboration โ built for distributed and global delivery environments.
Fixed Offers
Four Ways to Start, With a Clear Scope
Not ready for a long engagement? Start with a fixed scope, a fixed price and a concrete result. Each offer can grow into a longer rollout, but it is useful on its own.
AI-Assisted Engineering Workshop
One hands-on day with Claude Code and GitHub Copilot on your own codebase, with team rules, guardrails and a way to measure impact.
- Duration
- 1 day (or 2 half-days remote)
- Format
- On-site or remote ยท up to 12 engineers
You get
- Intake call and a quick tooling and repo check
- Hands-on exercises on your own code: each pair ships one reviewed change
- A written team playbook and starter instruction files in your repo
- An adoption baseline and a follow-up call after 30 days
AI Literacy for Teams
How AI tools work, where they fail and your house rules, for everyone who uses AI at work, with a record that supports EU AI Act Article 4.
- Duration
- Half a day (3.5 hours)
- Format
- On-site or remote ยท up to 20 people
You get
- Plain-language explanation of how LLMs work and fail
- Hands-on exercises in your approved tools
- A one-page "AI house rules" draft for your organisation
- Attendance list and summary for your AI literacy file
AI Delivery Readiness Assessment
A clear picture of where AI-assisted development stands in your teams today, and a 90-day plan to roll it out with guardrails.
- Duration
- 2 weeks
- Format
- Remote with 1-2 on-site days
You get
- Interviews with engineers, leads and product
- Review of repositories, CI and review practices
- Risk, data and governance check for AI tools
- 90-day rollout plan with guardrails and adoption metrics
Agentic Workflow Pilot
One real, repetitive workflow turned into an agent your team can inspect and trust, with people approving the decisions that matter.
- Duration
- 4-6 weeks
- Format
- Remote, milestone-based
You get
- Workflow mapping and agent boundaries
- MCP tool integration with human approval gates
- Evals, logging and a cost budget from day one
- Handover: docs, runbook and a team that can extend it
Fixed price, agreed upfront after a free 30-minute intro call. Free, no obligation. We talk through your role or project and whether I am a good fit.
Selected Engagements. Senior Commitment.
If you need a senior engineer for Java, Spring Boot or TypeScript work, are rolling out Claude Code or GitHub Copilot, or want agentic workflows that are safe and measurable, I am open to selected conversations.
Discuss an Engagement