Claude Code AI-Native Development Flow — Full Transition & Implementation

Overview We are , a UK-based high-volume email marketing platform processing over 1 billion emails per month. We want to transition our entire development team to an AI-native workflow built around Claude Code. We're looking for a Claude Code expert who has done this before — ideally someone who has already led a team through this transition and can show measurable productivity outcomes on the other side. What We Needed - Audit our current dev workflows and identify where Claude Code creates the most leverage - Set up Claude Code across all developer machines with consistent configuration - Configure MCP (Model Context Protocol) servers relevant to our stack - Write CLAUDE.md constitutions and project context files for our repos - Update our sprint SOPs and code review processes for AI-native development - Train developers (varying skill levels) on effective Claude Code usage patterns - Define agentic workflows for scaffolding, QA, and documentation - Establish a productivity measurement framework so we can track the before/after Our Stack - Languages: Go (primary), PHP , Vue 2/3 etc - Infrastructure: OVH bare-metal, Rocky Linux 9 - Version control: GitHub - Services: RabbitMQ, ClickHouse, MySQL, HAProxy etc - Existing context: We already have a CLAUDE.md constitution and MCP architecture in place for one part of our infra — this is about scaling it across the full team --- Deliverables 1. Dev workflow audit and Claude Code opportunity map (Week 1) 2. Claude Code + MCP setup across all developer environments 3. Repo-level CLAUDE.md documentation 4. Sprint SOP updated for AI-assisted development 5. Developer training sessions (live or recorded) 6. Productivity measurement framework 7. 30-day post-implementation advisory --- Ideal Candidate - Has led a real team through a Claude Code transition (not just personal use) - Can show productivity or efficiency outcomes from past engagements - Familiar with MCP architecture and agentic coding workflows - Experience with Go/PHP backend stacks is a plus - Communicates clearly and can work async --- Budget: Open to discussion Timeline: Kickoff within 1–2 weeks Engagement: Fixed-price project, with potential for ongoing retainer Please share examples of teams you've transitioned and the outcomes you measured. Looking forward to speaking with you.