6.1Guided practical cases
The essentials in 30 seconds
- Assemble: a real project combines form → database → automation (+AI) → app — each link with the right tool.
- Link: linked records, typed fields and driven views beat copy-pasting.
- Govern: filter early, secure secrets, make failure visible, document and measure time saved.
Lina thread — one year on: two chains running in Oran
Lina, digitalisation officer in Oran, looks back on her two landmark projects of the year: the lead-management chain that used to lose requests between the form, the spreadsheet and forgotten follow-ups, and the mini-CRM rebuilt without a developer for the sales team. Both cases below replay her sequence: frame, collect cleanly, structure into a linked database, automate, add AI with guardrails, deliver and measure.
Each case follows Context → Steps → Result: replay it on your own processes.
Putting the bricks end to end
The previous levels laid the bricks (Notion, Airtable, Make/Zapier, n8n + AI, app builders); here we assemble them under real conditions: starting from a fuzzy need, choosing the right tool for each link, connecting everything and measuring time saved. Two cases played out from A to Z.
Case 1 — An end-to-end lead-management chain
Context: A very small business receives requests via a form and by email, handled manually (copy-pasting into a spreadsheet, forgotten follow-ups). Goal: capture, structure, route and follow up automatically, without losing anything.
Déroulé :
- Frame (L0): describe the process (trigger = submitted form, rules = routing by type, current time) and check it is a good candidate (stable, clear rules).
- Collect (L5.3): a Tally form with typed, required fields and choice lists — clean data from the point of entry.
- Structure (L2): an Airtable Contacts ↔ Requests base (linked records), Status field (select), delay formula, “To follow up” view.
- Automate (L3): a Make scenario — submitted form → create the row → filter (ignore spam) → router (business vs individual) → notify the right salesperson.
- Add intelligence (L4): an AI step that summarises and classifies the request (category in JSON); secrets protected, retry + alert on failure.
- Deliver & measure (L5): a Softr portal to track leads, quantified ROI (time saved × frequency) and documented workflow.
Result: No more lost requests, automatic routing, reliable follow-ups — a complete form → database → automation (+AI) → portal chain, with measured ROI.
Case 2 — An in-house mini-CRM with no developer
Context: A sales team manages its customers in a chaotic spreadsheet (duplicates, free-text columns, no follow-up tracking). Goal: a clean, shareable mini-CRM with no developer.
Déroulé :
- Model (L2): Airtable Customers ↔ Opportunities ↔ Interactions base (linked records), typed fields, rollups (total, number of opportunities).
- Calculate (L2.4): “to follow up” status via a delay formula, filtered view driven by that status.
- Protect usage (L2.5): an Airtable Interface (dashboard + customer record) instead of access to the raw base.
- Mobilise (L5.2): a Glide app from the base for the field team (everyone sees their own customers, record and note-taking).
- Automate reminders (L3): a scheduled scenario that notifies each salesperson of the day’s follow-ups.
- Govern (L5.5): workflow documentation, naming conventions, owner and recovery plan (export).
Result: A clean relational mini-CRM, usable on mobile, with automatic follow-ups and governance — built without writing a single line of code.
Ready-to-say script — framing a no-code project before building (30 s)
«Our process: the trigger is [submitted form], the rules are [routing by type], the current time is [duration × frequency]. It is a good candidate because [stable, repetitive, clear rules]. We start with a quick win: [which one].»
Copy-paste template — replayable case sheet
PROCESS to handle (fuzzy need, volume, frequency): ...
TRIGGER + rules + current time (L0): ...
COLLECTION (form, typed, required fields): ...
BASE (tables, linked records, status, views): ...
SCENARIO (trigger → early filter → router → actions): ...
AI (summary + JSON category, secrets, retry + alert): ...
DELIVERY (interface / app, owner, doc, export): ...
ROI (time saved × frequency): ...VSE / small budget
Replay a single case on a quick win: simple form, two-table base, three-step scenario, ROI noted.
SME Algeria
Adapt routing to local realities: request types, team availability, usual notification channels.
Remote / hybrid
Double traceability at a distance: written notifications, shared portal and a named owner per workflow.
Intercultural
Check local practices before transposing a case: labels, statuses and channels must speak to the team.
48h challenge — apply tomorrow
Take 1 real process (requests, follow-ups, tracking) and write its chain in 6 steps (frame → collect → structure → automate → secure → measure). Identify the quick win.
- I can assemble the bricks into a complete chain.
- I have a replayable case sheet for my next process.
- I did the 48h challenge or scheduled its date.
Lina wants to stop losing leads between form, spreadsheet and follow-ups. Which sequence follows the guide?