All demos

Internal Software & CRM Β· Cedar Valley Training

Internal Software & CRM demo - Cedar Valley Training

Critical information lives in scattered documents with no shared, structured place to manage it.

Interactive internal system demo - explore freely

Cedar Valley Training

Relationship and Learner System

Role

You are signed in as Admin

Full access. Manages records, fields, statuses and settings.

Contacts

12 of 12 records Β· Β£47,050 total pipeline

  • Lead: 2
  • Proposal: 1
  • Active: 4
  • Enrolled: 3
  • On hold: 2
Cedar Valley Training contacts - name, organisation, type, stage and value
Adrian LaurentHorizon FoodsEmployerActiveΒ£9,750
Nia PatelStonebridge CareEmployerLeadΒ£4,200
Marcus DoyleRivergate LogisticsEmployerProposalΒ£7,900
Bryony FletcherOakmoor EstatesEmployerActiveΒ£11,400
Declan BurkePennine Build GroupEmployerOn holdΒ£6,300
Ella MorrisHorizon FoodsLearnerEnrolledΒ£1,200
Jordan AdeyemiRivergate LogisticsLearnerEnrolledΒ£1,100
Sofia KleinOakmoor EstatesLearnerActiveΒ£1,350
Harvey DoyleIndividual learnerLearnerLeadβ€”
AmΓ©lie RousseauStonebridge CareLearnerActiveΒ£1,250
Omar HaddadPennine Build GroupLearnerOn holdΒ£1,400
Grace OkoroOakmoor EstatesLearnerEnrolledΒ£1,200

Employer record

Adrian Laurent

Horizon Foods

Active

Β£9,750

Long-standing employer running three apprentices through the team. Renewal due in the autumn.

Shaped around Cedar Valley’s real records - this is a custom internal system, not a generic CRM. A employer connects to its learners, bookings, documents and tasks below.

Owner
Priya Shah
Email
adrian.laurent@horizonfoods.co.uk
Phone
0161 496 0182
Type
Employer

Stage

Linked records

How this employer connects across the system.

1 learner 0 bookings 2 documents 1 task

Learners (1)

Documents

  • Signed training agreementReceived
  • Levy transfer confirmationOutstanding

Open tasks (1)

  • Confirm autumn renewal numbersΒ· due 30 June 2026

Activity timeline

  1. Called Adrian - happy with progress, wants to add a fourth apprentice.

    21 Jun 2026, 09:14 Β· Priya Shah

  2. Stage set to Active after contract renewal.

    14 Jun 2026, 16:02 Β· Priya Shah

View this system as plain text

Cedar Valley Training holds 12 records - 5 employers and 7 learners. By stage: 2 Lead, 1 Proposal, 4 Active, 3 Enrolled, 2 On hold. Total pipeline value: Β£47,050.

  • Adrian Laurent - Horizon Foods (Employer), Active, Β£9,750
  • Nia Patel - Stonebridge Care (Employer), Lead, Β£4,200
  • Marcus Doyle - Rivergate Logistics (Employer), Proposal, Β£7,900
  • Bryony Fletcher - Oakmoor Estates (Employer), Active, Β£11,400
  • Declan Burke - Pennine Build Group (Employer), On hold, Β£6,300
  • Ella Morris - Horizon Foods (Learner), Enrolled, Β£1,200 - Level 3 Business Administration, 68% complete
  • Jordan Adeyemi - Rivergate Logistics (Learner), Enrolled, Β£1,100 - Level 2 Team Leading, 41% complete
  • Sofia Klein - Oakmoor Estates (Learner), Active, Β£1,350 - Level 2 Customer Service, 82% complete
  • Harvey Doyle - Individual learner (Learner), Lead - Level 2 Bookkeeping, 0% complete
  • AmΓ©lie Rousseau - Stonebridge Care (Learner), Active, Β£1,250 - Level 2 Health & Social Care, 55% complete
  • Omar Haddad - Pennine Build Group (Learner), On hold, Β£1,400 - Level 3 Construction Supervision, 30% complete
  • Grace Okoro - Oakmoor Estates (Learner), Enrolled, Β£1,200 - Level 3 Business Administration, 12% complete

Bookings: 3 Jul Portfolio review (Jordan Adeyemi); 7 Jul Induction follow-up (Grace Okoro); 9 Jul Early completion review (Oakmoor Estates); 12 Jul Assessment session (Ella Morris); 16 Jul Mid-programme review (Stonebridge Care); 23 Jul Final progress meeting (Sofia Klein).

Most teams do not need a huge CRM. They need a clean place where their real work fits. Every record, booking and document above is fictional mock data held only in this page.

What this demonstrates

  • Most teams do not need a huge enterprise CRM. They need a clean internal system that matches their real records, stages, documents, users and responsibilities.
  • Scattered documents and spreadsheets become one shared operational system.
  • The tool is shaped around the organisation's real records, not a generic template.
  • Roles mean each user sees and does only what they need.
  • Appointments, tasks and documents sit beside the records they belong to.
  • Every action is captured in an activity timeline, so nothing is lost in email.

Popular internal systems I can build

Pick one to see who it is for, what it adds and what it could include.

Lightweight CRM

Medium

A clean place to manage contacts, stages, tasks and notes, shaped around your process rather than a generic template.

Typical users
Small teams who find big CRMs too heavy and end up back in spreadsheets
Value added
The system fits how you already work, so people actually use it.

Could include

  • Contacts
  • Pipeline stages
  • Tasks
  • Notes
  • Search and filters

Want one place for your team's records?

You do not need a perfect brief. A messy process is enough to start.

Discuss a projectTalk through an idea

Next demo

AI Tools - Practical AI on a real task, with a human in control.

Open AI demo
What a real build could include Β· read as plain text

What a real build could include

The pieces a production version would be assembled from, in plain terms.

  • Authentication and user roles

    Sign-in and permissions so each kind of user sees and does only what they should.

  • Custom data models

    Records shaped around your real entities - contacts, learners, employers, bookings.

  • Search, sort and filters

    Find any record in seconds across every field.

  • Record detail pages

    Tasks, notes, linked records and documents for a relationship in one view.

  • Activity timeline

    A running history of every action taken against a record.

  • Booking calendar

    Appointments and resources scheduled beside the records they relate to.

  • Document tracking

    Checklists of received and outstanding documents per record.

  • Admin settings

    Manage fields, statuses and users without touching code or spreadsheets.

Read plain explanation

The situation

Cedar Valley Training (Admin staff managing learners, employers and placements). Critical information lives in scattered documents and spreadsheets with no shared, structured place to manage it. Contacts, learners, bookings and documents live in separate files, so no one is sure which version is current and follow-ups slip through. This demo shows how document sprawl becomes one clean internal system shaped around how a training provider actually works - not a generic crm clone.

How it would be built

  1. Model. Map how the team actually works day to day - the real records, stages and steps.
  2. Build. A clean, structured tool replaces document sprawl and one-off spreadsheets.
  3. Trust. Everyone works from one reliable source of truth, with the right access for their role.

What the demo points out

  • 01. Lightweight CRM. A contacts table holding the organisation's real employers and learners, with stage and value. The system is shaped around how the organisation works, not forced into generic enterprise software. Value: Better fit - the tool matches the work instead of the team bending to the tool.
  • 02. Roles and permissions. A role switcher that changes which controls and fields are visible. Different users can see and do only what they need, so records stay safe. Value: Safer operations - sensitive values and edit controls only appear for the right people.
  • 03. Admin portal. A settings area where the team manages records, fields, statuses and roles. Teams can manage records, fields and statuses without editing spreadsheets or code. Value: Controlled flexibility - the people who run the data keep the system shaped around their work.
  • 04. Record detail. A contact opening into employer info, deal value, tasks, notes, linked learners and documents. Everything about a relationship sits in one place instead of across separate files. Value: Less context switching - the full picture of a person is one click away.
  • 05. Booking system. A calendar of scheduled sessions, reviews and meetings linked to their records. Appointments, reviews and tasks sit beside the records they belong to. Value: Less context switching - fewer tools and less double-booking across the team.

What this demonstrates

  • Most teams do not need a huge enterprise CRM. They need a clean internal system that matches their real records, stages, documents, users and responsibilities.
  • Scattered documents and spreadsheets become one shared operational system.
  • The tool is shaped around the organisation's real records, not a generic template.
  • Roles mean each user sees and does only what they need.
  • Appointments, tasks and documents sit beside the records they belong to.
  • Every action is captured in an activity timeline, so nothing is lost in email.

Want one place for your team's records?