One CRM.
A useful next step.

WHERE EACH TOOL FITS

Find → understand → organise → act → learn.

DistroNow demonstrates the lead workflow. Treg provides access to external tools and data. Attio, HubSpot, folk and Twenty organise customer relationships. LEGIT AGENTIC and Ora help inspect website readiness. Okra CRM describes an AI-led inbound qualification workflow.

The products are not interchangeable. A discovered contact is not an interested customer; an audit score is not evidence of demand.

VERIFIED SHORTLIST

Pick for your team and task.

Plan details are a snapshot of official pages on 5 October 2026. Prices shown are USD where specified; annual billing is a commitment, not a month-to-month price. Features and limits can change. Recommendations below are our teaching judgement.

ATTIO / 12-MINUTE PRACTICAL

Five records, one reliable next action.

Prepare an account before class. Use a dedicated exercise workspace; connecting your personal inbox is unnecessary. These steps follow Attio's public import documentation; they have not been tested inside a signed-in Attio account.

1. Minutes 0–2: define the list. Create a list for companies called “First client experiment.” Decide what “Identified,” “Reviewed,” “Contacted,” and “Replied” mean.
2. Minutes 2–5: prepare and map. Download the fictional companies CSV. Map Company name to the company Name and Domain to Domains. Create list fields for Stage, Source, Fit evidence, Next action and Due date. Do not mix people, companies and deals into one unplanned import.
3. Minutes 5–7: preview and inspect. Check column mapping, unique domains and values before importing. Review all five resulting records. The reserved .example domains identify fictional organisations; they are not real leads. If the product rejects them, create a manual demonstration record rather than substituting a real company's identity.
4. Minutes 7–9: assign responsibility. Add the real teammate responsible as owner, set a future due date and write a concrete next action. Owner is assigned after import to avoid treating fictional names as users.
5. Minutes 9–11: simulate one event. Add a note clearly labelled “role-play,” move that record to Reviewed, and update its next action. Do not mark Contacted unless a real message was sent; this lab has no real sending.
6. Minute 12: capture evidence. Export the visible table or capture an anonymised screenshot. Explain why the fields and workflow fit your project. Label the exercise as practice, then plan a real validation test.

Official CSV import guidance · Official list-import lesson · Export guidance

Completion check: five clearly labelled demo records, sensible fields, an owner, a dated next action, and an explained choice. No paid AI feature is needed. A spreadsheet using the same fields is an equivalent fallback.

DISTROnow / FACILITATOR DEMO

Follow a lead without sending anything.

On the instructor-provided DistroNow instance, open /leads-finder. The repository documents this route as a fictional browser-local workspace. Confirm the demo label before starting. A public deployment address was not verified for this guide.

1. Review the fictional buyer Alex Morgan and explain the evidence of fit.
2. Approve the buyer and simulate verification.
3. Generate a draft, edit it, save it and approve it.
4. Simulate sending, then record a fictional reply.
5. Record booked and held meeting outcomes separately.
6. Inspect the activity log and explain where each total came from.

All results are simulated and support workflow practice only. Actual customer validation must be separately collected and labelled.

Repository demo and setup instructions · Current Treg API documentation

LEGIT AGENTIC + ORA

Make the website easier to understand and use.

1. Open LEGIT AGENTIC's public audit or is-agentic and inspect your team's public prototype.
2. Select one relevant issue with a visible effect on the customer journey.
3. Record the original observation, make a justified change and repeat the check.
4. Ask a person to try the relevant task. Keep that observation distinct from the automated audit result.

LEGIT AGENTIC's methodology separates technical readiness from measured AI visibility. Ora's announcement describes its partnership with Vercel. A higher score does not establish more recommendations or more clients.

OKRA IS DIFFERENT FROM ORA

A candidate to evaluate, not a required purchase.

Okra CRM describes AI responses, qualification, routing and meeting booking for inbound teams. Its public site advertises trials, but the plan buttons lead to anchors and the visible pricing blocks leave the applicable terms unclear. A working student onboarding route, export flow, and classroom price have not been verified.

Before choosing it, demonstrate with a fictional enquiry: what information is collected, which questions qualify the lead, when a person takes over, and whether the record can be exported. Until then, discuss the workflow using the tools already available.

AI CONNECTIONS / OPTIONAL

Prove the manual flow before adding an agent.

Attio and folk advertise MCP connections; Twenty documents a native cloud MCP server. Availability and permissions depend on the product and plan. MCP lets a compatible assistant access tools; it does not establish that an action is correct or authorised.

Suggested extension: ask an assistant to summarise a fictional record and propose the next action. Review it before any write or message. The core class requires no MCP setup.

Attio MCP · folk MCP guide · Twenty cloud FAQ

THE ASSIGNMENT CONNECTION

Explain your choice with evidence.

In Tool choices, write: “We chose [tool] because [specific need]. We checked [cost, seats and needed feature]. Its limitation is [constraint]. We demonstrated [workflow].”

In Testing, distinguish a fictional CRM exercise, an automated website check and real user observations. In Iterations, show what changed because of the evidence. In Individual reflection, explain your own work and judgement.

The eight required items and existing grading remain unchanged. Tool spending, automation volume and client counts do not create extra grading criteria.