Milestone
Leads are managed in a working CRM
Lessons
What the lesson covers
- Prerequisites
- Checkpoint
lesson-4.7;docs/brief.mdfor the sales process. - Covers
- What a CRM is for: no lead forgotten, every lead's state known.
- Defining the pipeline stages for the student's business (for example: new, contacted, qualified, won, lost).
- Extending the data model: notes, tasks, status history.
- Screens and navigation; what to leave out.
- Do along
- Have Claude write
docs/crm-spec.mdwith stages, screens and the migration for the new tables; apply the migration. - Done when
- The specification lists every screen and the new tables exist in the database.
- Homework
- Test the stage definitions in the spec against five real enquiries and sharpen the wording; write the qualifying questions for a first call and a count of where open enquiries sit today.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.1; the browser connection from 1.6. - Covers
- The admin layout: sidebar, page header, sign-out.
- A table of leads with the key columns and status badges.
- Search, filter by status and date, sorting, pagination.
- Empty and loading states.
- Do along
- Build the list and fill the database with realistic sample leads generated by Claude.
- Done when
- The student can find a specific sample lead by name and by status within a few seconds.
- Homework
- Bookmark two or three filtered views for daily use and check the list on a phone; put the two empty-state messages into the student's own words.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.2; the browser connection from 1.6. - Covers
- The detail page: contact data, message, source, dates.
- Editing lead fields.
- Notes with author and time.
- One-click actions: call, email, open a messenger chat.
- Do along
- Build the page, add notes to sample leads, edit a contact field.
- Done when
- Notes and edits survive a page reload and appear in the database.
- Homework
- Agree a three-line shape for notes and write five more notes in it; draft the first email and messenger message to a new lead, and list what the card lacks during an imagined call.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.3; the browser connection from 1.6. - Covers
- A board with one column per stage.
- Changing status by dragging a card, and from the lead card.
- Recording every status change with its time in the history table.
- Asking for a reason when a lead is marked lost.
- Do along
- Build the board and move sample leads through the whole pipeline.
- Done when
- A status change made on the board shows in the list, in the lead card and in the history.
- Homework
- Move eight sample leads through an invented week on the board from a phone, with lost reasons; write what each lost reason would change in the business and where leads would pile up.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.4; the Telegram bot or email sending from 4.5; the browser connection from 1.6. - Covers
- Tasks attached to a lead with a due date.
- A "today" view: due and overdue tasks.
- A scheduled job that sends a daily summary to Telegram or email.
- Marking tasks done; creating the next step.
- Do along
- Build tasks and the daily summary; trigger the job by hand to test it.
- Done when
- A task due today appears in the "today" view and in the summary message.
- Homework
- Write the student's own follow-up rules and give every qualified sample lead a next step; the next morning confirm that the summary arrived by itself and note the time.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.5; the browser connection from 1.6. - Covers
- The numbers that matter: new leads, conversion between stages, win rate, response time.
- Queries that calculate them for a chosen period.
- Charts: leads over time, leads by stage; sources are added in 6.8.
- Avoiding numbers nobody acts on.
- Do along
- Build the dashboard as the admin home page and check each figure against a manual count.
- Done when
- Every figure on the dashboard matches a manual count of the sample data.
- Homework
- Predict how one status change alters the figures and check it; repeat the manual count for win rate and response time on a second period, and write one action for each figure.
What the lesson covers
- Prerequisites
- Checkpoint
lesson-5.6; the browser connection from 1.6. - Covers
- Adding a lead by hand (phone calls, referrals).
- Exporting filtered leads to CSV.
- Importing from CSV with duplicate detection.
- Deleting a person's data on request.
- Do along
- Export leads, edit the file, import it back; delete one lead fully.
- Done when
- The import adds new leads without duplicating existing ones, and a deleted lead's notes and tasks are gone too.
- Homework
- Prepare a CSV of the student's real contacts and take it as far as the import preview without confirming; write a routine for handling deletion requests.