Team Structure & Roles
Our team of 12 operates as a single product squad, not a hierarchy of departments. Everyone has a primary role, but everyone speaks the same language: specs, issues, and merge requests.
Roles
- Sales / Product Scout — 1 person — Uses: Claude for proposals & specs
- Functional Consultants — 5 people — Uses: Claude for spec writing & testing
- Developer Consultants — 5 people — Uses: Claude Code for development
- Tech Lead (you) — 1 person — Uses: Claude for architecture & review
Role Responsibilities in the New Framework
| Role | Primary Output | GitLab Artifacts | Claude Code Seat |
|---|---|---|---|
| Sales / Product Scout | Opportunity specs, customer pain points, feature requests | Creates Issues with stage::opportunity, writes initial business spec | Yes — drafts proposals, competitive analysis, customer-facing docs |
| Functional Consultant | Functional specs, test scenarios, acceptance criteria, customer validation | Owns the stage::spec phase — writes detailed specs, creates test issue checklists | Yes — generates BDD test scenarios, data models, process flow descriptions |
| Developer Consultant | Code, technical specs, architecture decisions, CI/CD pipelines | Merge requests linked to issues, technical design records in wiki, pipeline configs | Yes — primary user. Code generation, refactoring, test writing, PR descriptions |
| Tech Lead | Architecture decisions, code reviews, sprint priorities, framework rules | Reviews MRs, maintains project templates, manages milestones | Yes — architecture design, complex refactoring, CLAUDE.md maintenance |
Key Change
Functional consultants are no longer "just" writing Word docs. They write specs directly in GitLab Issues using a structured template. They become co-owners of quality — because if the spec is good, the AI-assisted code is good.