Leads wait too long
A new enquiry arrives, but the reply depends on who notices it and when.
Practical automation for growing businesses
Fix the task your team repeats every day.
Tell me where work gets stuck. I’ll map the bottleneck and show whether a focused automation can make it faster, clearer, and easier to control.
Free 15-minute fit audit. No obligation. Third-party tools are priced separately.
Lead follow-up · demoTEST DATA
NA
New enquiryWebsite form · 14:03
Validated01 Captured
02 Owner alerted
03 Reply sent
Human-controlledNo AI API required
Different industries. Familiar bottlenecks.
Start with the work that should not depend on memory.
The same data is entered twice
Your team copies information between forms, email, WhatsApp, spreadsheets, and other tools.
Follow-up lives in people’s heads
Reminders and status changes are manual, so the next action can be missed.
Lead Follow-up System · prototype
One recurring problem, handled from start to finish.
This synthetic demo shows a reusable follow-up flow that can be adapted to schools, agencies, appointment businesses, and other teams.
- 01
A new enquiry arrives from an approved source.
- 02
Required fields, consent, and possible duplicates are checked.
- 03
The responsible person is alerted and an approved acknowledgement is sent.
- 04
Scheduled follow-ups stop after a reply, booking, opt-out, or staff status change.
- 05
The team keeps control of every status and next action.
Demo data is fictional. Messages, integrations, consent rules, and stop conditions are configured separately for each client. Important decisions stay with people.
Run the interactive demoLIVE LOGICDEMO MODE
01New enquiryForm · Ad · Approved source
02Validate + dedupeConsent · fields · existing lead
03AAcknowledgeApproved channel
03BAlert ownerHuman handoff
04Follow up—or stopReply · booking · opt-out · status
Free automation fit audit
A useful diagnosis—not free implementation.
We inspect one repeated process and decide whether it is worth automating before anyone commits to a build.
Included
- Review of one recurring business process
- Fit or no-fit conclusion
- Simple recommended direction and likely tools
- Starting cost range when the project fits
Not included
- Workflow construction or testing
- Account connections or credentials
- Detailed technical specification
- Unlimited consultation or revisions
Safety: No password, API key, payment detail, or sensitive customer file is needed for the first audit.
Clear commercial boundary
Start small. Prove the workflow.
One-time 30-day pilot fee from4,900 MAD
Paid once to Mezz AI—not monthly. Covers one lead source, one communication channel, one owner, up to 150 leads, and agreed acceptance tests. 60% before implementation and 40% before production activation.
Describe your bottleneckTOOLS + OWNERSHIP
Third-party software is separate and client-paid
- ↗n8n Cloud or assessed client-owned hosting
- ↗WhatsApp, email, CRM, calendar, storage, or later AI usage
- ↗No AI API is required for the first Lead Follow-up version
The client pays third-party providers directly wherever possible. Their monthly or usage-based charges are not included in the pilot fee. Ongoing Mezz AI support after the 30-day pilot is optional and quoted separately if requested. The written proposal confirms every estimate before purchase. The pilot guarantees agreed system behavior—not revenue.
Honest proof labels
Know exactly what you are looking at.
A working demonstration using fictional information.
A functioning automation, not presented as a client result.
A measured result published only with written client permission.
A proposed flow that has not been deployed.
MMEZZ AI
MOROCCO
MOROCCO
About Mezz
Process first. AI only where it earns its place.
Mezz AI is an independent automation studio based in Morocco. I help teams reduce repetitive digital work without hiding trade-offs behind AI language.
I start with the process, its exceptions, and the human decisions. Then I build the smallest reliable workflow that can be tested, handed over, and improved. If clear rules are enough, I use clear rules.
Common questions
Before you request the audit.
01Is Mezz AI only for schools?+
No. Schools are one demonstration. The same lead and follow-up problem appears in agencies, professional services, appointment businesses, property teams, and many other operations.
02Do I need AI or n8n?+
No. Tools are selected after the process is understood. Many dependable automations use simple rules. AI is added only when it has a useful, reviewable role.
03What makes a good automation candidate?+
A repetitive digital process with a clear trigger, required inputs, a responsible owner, and an expected outcome. Rare work based mainly on human judgement may not be worth automating.
04Who owns the accounts and data?+
Client accounts should remain client-owned wherever possible. Access, responsibilities, data handling, and handover are agreed in writing before implementation.
05Can you guarantee revenue or savings?+
No. The project guarantees agreed acceptance tests for what the system must do. Revenue and savings also depend on traffic, the offer, data quality, staff actions, and third-party services.
Describe the bottleneck
One recurring problem is enough to start.
Tell me what triggers the process, what the team does today, and where it gets stuck. I’ll review it and reply within one business day.
Do not send passwords, API keys, payment information, student records, payroll files, or other sensitive customer data.