The Coders Guild

People, Tools & Issues

Who's involved in the apprenticeship lifecycle, what tools they use, what jobs they need to get done, and the cross-cutting issues that affect everyone.

Who's involved

Personas & Jobs to Be Done

Four perspectives on the same process. Click a persona to explore their jobs, pain points, and opportunities.

T
TCG Internal
Crispin, Francesca, Shelley, and Rob - each with distinct jobs but shared pain around disconnected systems and manual processes.
4 sub-personas
View details
E
Client / Employer
SMEs with 20-200 people, buying apprenticeships to upskill their team. Busy, expecting fast time to value, not form-filling.
Decision makers
View details
L
Learner / Apprentice
Existing employees on Level 4 programmes, balancing learning with their day job. Need clarity, relevance, and minimal admin.
On programme
View details
A
Auditor
DWP, Ofsted, compliance bodies. Want clean, consistent, accessible records. The stakes are existential - funding clawback is real.
Regulator
View details
T
TCG Internal
Four sub-personas running the apprenticeship business
Crispin (MD)
Francesca (Commercial)
Shelley (Compliance)
Rob (Operations)

Founded TCG 15 years ago. Wrote the curriculum, built the relationships. Wants to move to non-operational, growth-focused role but Allison's departure pulled him back in. His time is the scarcest resource.

Jobs to Be Done
When I'm building the pipeline, I want to generate leads that don't depend on my personal network, so the business can grow beyond my capacity.
When an employer shows interest, I want to qualify them quickly for commitment and fit, so we don't waste time on businesses that want a quick fix.
When we're selling, I want the company brand to carry the conversation, so I'm not the bottleneck in every deal.
When I'm planning cohorts, I want reliable pipeline visibility six weeks out, so I can book trainers and commit to start dates.
When I look at how we run internally, I want our operations to reflect the AI expertise we're teaching, so we're not undermining our own credibility.
Pain Points
Founder-led sales. Most conversions come through Crispin's personal brand and network. That's a ceiling on growth.
No single source of truth. Information lives in Monday, Google Drive, email, and people's heads.
Still runs initial assessments and handles employer introductions despite wanting to be strategic.
Opportunities
AI skills gap assessment as a lead tool - employers experience TCG's expertise before signing anything.
Automated qualification from discovery call transcripts, reducing Crispin's time in every deal.
Pipeline dashboard with six-week-ahead visibility for trainer booking and cohort planning.
E
Client / Employer
SMEs, 20-200 people. Decision makers buying apprenticeships to upskill their team.
Jobs to Be Done
When considering upskilling my team, I want to understand what skills gaps we actually have, so I can make a business case.
When evaluating providers, I want to see evidence of quality before I commit, so I'm not taking a punt on box-ticking.
When working out funding, I want to know quickly whether we're using the levy, paying directly, or doing a transfer, so I can budget.
When I've decided to go ahead, I want the paperwork to be fast and painless, so my team can start learning.
When my apprentice is learning, I want to see progress against real skills that matter to my business, so I know it's paying off.
When something isn't working, I want early warning and a plan, so we can fix it before it's a problem.
Pain Points
Onboarding is compliance-led. First touchpoints after signing are forms, insurance certificates, and government system connections - not learning.
Payment type confusion slows things down. Levy transfers can block enrolment entirely.
Have to repeat information already given during sales because it doesn't flow through to delivery.
No self-service way to assess team skills gaps before committing. Quality difference invisible until after signing.
Opportunities
Skills gap tool as the entry point - get a capability map before any commitment. Experience AI in action.
Employer-facing progress dashboard with live visibility of apprentice development.
Onboarding redesigned around the learner, not compliance. Documents collected as a background process.
Hackathons and workshops for employer teams to drive cultural change beyond the apprentice.
L
Learner / Apprentice
Existing employees on Level 4 programmes, or recruitment candidates being matched to roles.
Jobs to Be Done
When told I'm doing an apprenticeship, I want to understand what's expected of me (time, portfolio, project work), so I can plan around my workload.
When filling in forms, I want to do it once and have it count, so I'm not repeating myself across systems.
When learning new skills, I want the content to be relevant to my actual job, so I can apply it immediately.
When recording hours and evidence, I want it to be quick and easy from my phone, so it doesn't feel like a second job.
When building my portfolio, I want clear guidance on what counts as evidence, so I'm not guessing.
Pain Points
Initial onboarding is form-heavy. Application, English/Maths, SGA, right-to-work - all in quick succession.
Experience fragmented across Slack, Google Drive, PICS, and the Laravel app. No single place.
Portfolio requirements uncertain - assessment approach may change, won't be confirmed until April 30th.
Some enrolled by employers who haven't explained the commitment. Expectations misaligned from day one.
Opportunities
Skills gap output from sales becomes the personalised learning plan from day one. No repeated data collection.
Single learner dashboard: progress, schedule, evidence, hours, next steps - one place.
Alumni community with structured CPD and peer learning. Relationship doesn't end at completion.
Talent pool for recruitment candidates - people who don't match one role get held for future opportunities.
A
Auditor
DWP, Ofsted, compliance bodies. Not adversarial by default - they want clean records and proof that learning is happening.
Jobs to Be Done
When reviewing records, I want every apprentice's documentation complete, consistent, and accessible, so I can verify compliance without chasing.
When checking a role's suitability, I want a job scan that maps clearly to the occupational brief, so I can confirm the right exposure.
When verifying off-the-job hours, I want accurate, timestamped records matching the training plan.
When assessing quality, I want evidence of KSB tracking and intervention when apprentices fall behind.
Pain Points
Documents stored across multiple systems (Google Drive, Monday, email) make completeness verification harder.
If information was captured verbally and never formalised, it doesn't exist for audit purposes.
Manual checking at scale will inevitably have gaps. Error rate goes up with volume.
Opportunities
Compliance-by-design - every record auto-checked for completeness at each stage. Missing documents flagged before they become findings.
Audit-ready record structure - single view per apprentice with all required documents, exportable and verifiable.
Government reporting outputs generated as a by-product of normal operation, not a separate process.
Systemic problems

Cross-cutting Issues

Problems that span multiple stages. These won't be fixed by improving a single process.

Founder-led sales
Crispin's personal brand drives opportunity. The 60-70% email open rates work because it's him. The business depends on his network and credibility - that's a ceiling on growth.
No single source of truth
Information lives in Monday.com, Google Drive, PICS, Google Forms, spreadsheets, Slack, email, and people's heads. Nobody has a complete picture without checking several systems.
Manual data movement
Every tool transition is manual. Eventbrite CSVs enriched in Apollo, entered one-by-one into the CRM. SGA results manually copied into funding calculator. No automation connecting systems.
Conversation data lost
Essential information from sales calls doesn't make it into the CRM. Calls are transcribed but nobody processes them. Shelley and Rob re-ask questions the employer already answered.
CRM not fit for purpose
Monday.com works as a basic CRM but struggles with multiple deals per employer, different products with different start dates, and recruitment mixed with existing staff pathways.
Delivery team flying blind
Rob has no visibility into pipeline. Needs six weeks to book trainers but gets no structured signal. Historically, numbers that materialise differ from numbers promised.
Compliance drives complexity
Much onboarding exists for audit, not for employers or apprentices. Job scans, SGAs, assessments - all mandatory, all paper-heavy. Getting it wrong means funding clawback.
Scale is the test
Everything works at current volumes. The question is whether it survives 60 apprentices, then 200 by Christmas. On-programme management is the biggest concern.
Patterns across personas

Three Themes

Patterns that appear across all four personas.

Theme 01
Capture once, use everywhere
Every persona suffers from the same problem: data collected in one place doesn't flow to where it's needed. Employers repeat themselves. Rob can't see the pipeline. The auditor can't find documents because they're scattered.
Theme 02
Compliance as a by-product
Shelley and the auditor both want the same thing: clean, complete records. The difference between a compliance burden and a well-run programme is whether records are generated by doing good work or assembled as a separate exercise.
Theme 03
Earlier signals, faster decisions
Crispin needs pipeline visibility six weeks out. Rob needs a cohort trigger. Francesca needs payment type identified earlier. Shelley needs quality signals before onboarding. The information exists somewhere - it arrives too late.
Current stack

Tools Landscape

What's in use, what it does, and where it falls short.

Monday.com
CRM (leads, deals), email sequencing, recruitment, delivery schedule
Clunky for multi-deal employers. Expensive. Automations don't surface the right info.
Apollo
Data enrichment. Cold email outreach being phased out.
Not providing expected value. Manual CSV workflow. May be replaced.
LinkedIn Sales Nav
Prospecting, follow-up, engagement tracking, ICP interaction
Laborious but effective. Being considered as the prospecting CRM.
Google Drive
Compliance document storage (structured folders). Recordings, slides.
Documents separated from CRM data. Manual organisation.
Google Calendar
Trainer scheduling coordination. Syncs with Monday.com delivery board for session dates and availability. (Mar 17 follow-up)
Manual sync with Monday.com. No capacity visibility built in.
PICS / LMI
Learner management. Application forms, English/Maths (BKSB), enrolment, funding claims. AAF compliance dashboard (OTJ hours planned vs actual, requirements met/not met, withdrawals, aim on planned break, end-point assessment organisation data). QAR achievement rates dashboard. Learner breakdown and coach caseload dashboard. Monthly payment submission to government - Shelley runs reports. (Shelley, Mar 18)
Workflow-driven but rigid. Dashboard data only visible to Shelley - doesn't flow to coaches or anyone else. Being updated.
Google Forms
Skills Gap Analysis (SGA) - initial skills self-assessment against KSBs before programme start. (Mar 17 follow-up)
Standalone. Not connected to PICS or funding calculator.
Eventbrite
Webinar registration and attendee management
Manual download of attendee lists. No CRM integration.
Slack
Cohort communication channels. Alumni group. Document sharing.
Per-cohort channels. Manual setup. Alumni community informal.
Spreadsheets
Funding calculator, trainer schedules
Manual data entry. Not connected to other systems.
Calendly
Meeting booking for discovery calls
Works fine for its purpose.
DocuSign
Contract and agreement signing
Works fine for its purpose.
DAS (Gov)
Digital Apprenticeship Service - government system for apprenticeship enrolment. Levy transfers processed here. Employer connection can take weeks to establish. (Mar 17 follow-up)
External system. Levy transfer process is slow. Connection delays can hold up enrolment.
Google Workbook ("Matrix")
Apprentice learning platform: training plan, tasks, coach feedback, progress, attendance, portfolio. Used by coaches in meetings, Shelley for monitoring, apprentices for progress.
Central to delivery but entirely manual. No integration with any system. THE key automation candidate.
Laravel App
Apprentices self-log OTJ (off-the-job) hours. Connected to PICS data. KSB progress tracking. Coaches and Shelley monitor. Basic apprentice and admin logins exist. (Mar 17 follow-up)
Early stage. Employer/admin multi-view logins not yet commissioned. Will eventually replace the matrix.
BKSB
English and Maths initial assessments, used alongside PICS for learner onboarding. (Mar 17 follow-up)
Works well. Automated via PICS.
Working document

March 2026. Sources: Feb discovery, Mar 4 coordination, Mar 10 and Mar 17 process mapping workshops, Rob's ops notes, Shelley's Mar 18 PICS dashboard screenshots, and product strategy discovery questions.

Created by Specs for The Coders Guild