Automating lead qualification with Make.com and leadflow.ma in Morocco.

The problem: 70% of sales time burned on leads that will never convert

Across the 18 lead-ops setups Webotic audited in 2025-2026, the picture barely changes from one vertical to another. A Casablanca HR consultancy generates 240 leads a month through Meta Lead Ads and Google Search. Four reps process them by hand: no scoring, no enrichment, no automated routing. Measured over 90 days: 168 leads (70%) never answer, do not match the target profile, or decline a follow-up after the first call. The 72 actually sellable leads are processed with the same delay as the rest, averaging 3 h 48 min between form submission and first sales contact. Webotic's internal numbers confirm what InsideSales documented in 2017: the probability of reaching a lead drops 80% past 30 minutes, and the meeting-conversion rate falls 60% past 2 hours. Concretely, this consultancy loses 8 to 12 SQLs per month — 240,000 to 480,000 MAD of revenue missed every quarter on contracts averaging 30,000 MAD. The cause is never sales talent or creative quality. It is the absence of an automated qualification layer between the form and the CRM — a layer that filters, enriches and prioritises before a human is summoned. Make.com (formerly Integromat) paired with leadflow.ma delivers exactly that layer, at a cost that fits a Moroccan SME budget.

• 70% of sales time consumed by non-sellable leads — finding across 18 Webotic accounts 2025-2026.
• Median form → first contact delay: 3 h 48 min manual — versus the 5-min SLA standard on hot leads.
• Average Moroccan SME opportunity cost: 15,000 to 25,000 MAD/month of latent revenue.

The target architecture: webhook → Make → enrichment → scoring → CRM → Slack

The full pipeline sits on six stages, each one with a single instrumentable function. Stage 1, capture: the form (Meta Lead Ads, Google Ads Lead Form, Webflow, WordPress Gravity Forms, Typeform, custom HTML) emits an event via native webhook or via Make's Watch Leads module. Make opens a scenario per submission. Stage 2, normalisation: a Set Variable module cleans the email (lowercase, trim), validates the phone against the Moroccan E.164 format (+212 followed by 9 digits), extracts the professional domain and discards free domains if the use case is B2B. Stage 3, firmographic enrichment: an HTTP call to Clearbit Enrichment (on the professional domain), Apollo.io (on the email) or FullEnrich (which cascades several providers under one API) returns company size, sector, role, seniority, LinkedIn presence, technologies in use. Marginal cost per enriched lead: 0.05 to 0.18 USD depending on provider. Stage 4, BANT+ scoring through the leadflow.ma API: Make sends a POST with the enriched payload and receives back a JSON containing a 0-100 score, a tier (hot/warm/cold), and the explicit reasons that produced the score. Stage 5, CRM sync: a HubSpot Create or Update Contact, Pipedrive Create Deal or Zoho CRM Create Lead module pushes the entire enriched + scored payload into the record, with explicit mapping for every custom property. Stage 6, notification: a Slack Send Message module fires into #leads-hot when the score crosses 70, with an interactive block (name, score, reasons, CRM link, call-now button).

• Measured end-to-end latency: 14 to 22 seconds, dependent on external API latency (Clearbit, leadflow, HubSpot).
• Idempotency guaranteed by a unique event_id: a Meta retry never creates a duplicate in HubSpot.
• Observability: every stage logged inside Make plus a BigQuery mirror for quarterly audit.

Configuring Make.com in 6 modules — the minimum that ships

Open a blank scenario in Make. Module 1 — Custom Webhook: Make generates a unique URL to paste into the form (or use the native Facebook Lead Ads connector, which provisions the webhook automatically on the Business Manager page). Test with a sample payload — Make detects the fields and exposes the variables. Module 2 — Tools Set Multiple Variables: create 4 variables (email_clean = lower(trim(email)), phone_e164 = parsePhone(phone, 'MA'), domain = split(email, '@')[2], is_pro_domain = !in(domain, ['gmail.com','outlook.com','hotmail.com','yahoo.fr'])). Module 3 — HTTP Make a Request to Clearbit: URL https://person.clearbit.com/v2/combined/find, header Authorization: Bearer sk_xxx, query email={{email_clean}}. Parse the JSON response into company.size, person.role, person.seniority. If Clearbit returns 404, automatic fallback to Apollo through a router with a condition. Module 4 — HTTP to leadflow.ma: POST https://api.leadflow.ma/v2/score with body {email, phone, domain, company_size, role, seniority, source, utm_source, utm_campaign}. The response contains {score, tier, reasons[]}. Module 5 — HubSpot Create or Update Contact: map email → email, phone_e164 → phone, score → custom property lead_score, tier → lifecyclestage. Module 6 — Router: branch A when tier == 'hot' fires Slack Send Message to #leads-hot with a formatted block; branch B when tier == 'warm' enrols the contact in a 14-day HubSpot nurturing sequence; branch C when tier == 'cold' tags the contact for Meta Custom Audience retargeting and stops. Activate the scenario, set frequency to Immediately, and the pipeline is live.

• Setup time for a competent Make operator: 3 to 5 hours, including end-to-end testing.
• Monthly cost of the minimum stack: Make Core 350 MAD + HubSpot Starter 540 MAD = 890 MAD.
• Volume covered by Make Core: 10,000 operations/month ≈ 1,500 fully scored enriched leads.

BANT+ scoring: 7 dimensions, 100 points, explicit reasons

A numeric score with no explicit reasons is just a number that nobody trusts. The leadflow.ma scoring used by Webotic with Moroccan clients weights 7 dimensions and returns, for every lead, not just the number but the list of factors that produced it — that is what makes the score actually usable by a sales rep. Budget (15 points): declared via the form or inferred from Clearbit revenue data. Authority (15 points): Clearbit or Apollo seniority (C-level, VP, Director = 15; Manager = 10; IC = 5; Student = 0). Need (10 points): a 'main problem' field filled with at least 8 words, or coherence between the offer and the targeted sector. Timing (10 points): declared on the purchase horizon, or inferred from visited pages (pricing page = 8; contact page = 10; blog post = 3). Firmographic fit (20 points): company size inside the target range (5 to 50 employees for B2B SaaS SMB = 20 points), sector inside the target list, geography (Morocco = 15; MENA = 12; rest = 8). Digital engagement (15 points): more than 3 page views (5 pts), return to the site within 14 days (5 pts), prior email opened (5 pts). Source channel quality (15 points): Google Search Brand (15) > LinkedIn Ads (13) > Google Search Generic (11) > Meta Lead Ads retargeting (10) > Meta Lead Ads cold (7) > TikTok Lead Gen (5). Operating thresholds: 70-100 = hot, immediate Slack alert and 5-minute callback SLA; 40-69 = warm, 14-day nurture then re-score; 0-39 = cold, Meta retargeting plus archive. Weights are adjustable per client inside the leadflow.ma dashboard — what matters for a law firm (Authority + Fit) differs from what matters for a B2C fashion e-commerce shop (Engagement + Timing).

Make.com vs Zapier vs n8n: the 2026 verdict for a Moroccan SME

The no-code/low-code automation market splits across three vendors with distinct positioning. Make.com (formerly Integromat, acquired by Celonis in 2020): Core plan at 350 MAD/month for 10,000 operations, 2,100 connectors, visual scenarios with routing, iterators, aggregators and granular error handling. The right pick for lead-ops workflows with multi-branch enrichment and scoring — our default on the 18 Webotic accounts. Zapier: Starter at 200 MAD/month for 750 tasks, 8,000+ connectors, an ultra-simple linear interface. Excellent for basic 2-3 step automations (Lead → CRM → Slack) but expensive and constraining beyond 5,000 tasks/month — at real Moroccan SME lead-ops volume, Zapier ends up 2 to 3 times more expensive than Make for the same scenarios. n8n: self-hosted free or cloud 200 MAD/month, code-first, ideal if you have a DevOps engineer available to handle hosting and updates. The 3 Webotic accounts on n8n all have an internal data or DevOps team. The plain rule for a Moroccan decision-maker: if you are shipping your first lead-ops pipeline with no dedicated technical team, pick Make. If Zapier is already in place running under 1,000 tasks/month and everything works, do not migrate. If you have a technical team and an infrastructure budget, n8n is defensible.

• Make Core 350 MAD/mo: 10,000 ops, 2,100 connectors, advanced routing — best price-quality for SMB lead-ops.
• Zapier Starter 200 MAD/mo: 750 tasks, ultra-simple — saturates fast at Moroccan B2B volume.
• n8n self-hosted free: code-first, infra to manage — only with an in-house technical team.
• Across 18 Webotic accounts: 12 Make, 3 Zapier (legacy), 3 n8n.

Real monthly stack, measured 90-day ROI

Here is the monthly cost breakdown observed on the Webotic reference pipeline — an HR consultancy, 4 sales reps, 1,000 leads a month. Make Core 350 MAD/month (10,000 ops cover everything). HubSpot Starter Sales + Marketing 540 MAD/month (1,000 contacts, scoring, sequences, reporting). Clearbit Enrichment 720 MAD/month for 1,000 lookups (higher-volume accounts move to FullEnrich at 540 MAD/month for 1,500 cascaded multi-provider lookups). leadflow.ma Pro API 490 MAD/month for 1,500 scorings. Slack Pro 90 MAD/user/month (4 reps + 1 ops = 450 MAD). Stack total: 2,550 MAD/month for a complete setup — 30,600 MAD per year. Against that cost, the gain measured across 12 Webotic accounts over 90 days is documented. Hours reclaimed: 18 per week per lead-ops engineer, 72 per month — equivalent to 0.45 FTE freed on a Moroccan loaded payroll cost of 15,000 to 22,000 MAD/month (net gain 6,750 to 9,900 MAD/month). MQL → SQL conversion: +35% on average, meaning 8 to 12 extra SQLs per month for this consultancy (additional revenue 60,000 to 120,000 MAD/month on contracts averaging 7,500 MAD). Sales cycle: −38%, mechanically freeing more sales hours for more pipeline. Net ROI inside 90 days: between 8x and 14x the stack investment depending on vertical. It is the fastest return we observe across every Webotic digital lever — well ahead of server-side tracking (8 months) and ABM (10 to 12 months).

Risks, edge cases and 5 mistakes to avoid

No lead-ops pipeline is plug-and-play, and most failures we have observed fall into 5 reproducible patterns. Mistake 1, over-trusting automated enrichment: Clearbit and Apollo deliver a 55 to 75% match rate on Moroccan emails, against 85-92% in US/EU markets. Always plan an Apollo fallback branch when Clearbit returns 404, then FullEnrich as last resort, then a degraded scoring path that weights only the source channel. Mistake 2, frozen scoring: a scoring system left untouched for 6 months always drifts — reps end up flagging 'hot leads' that close at 10% and 'cold' that close at 25%. Schedule a monthly scoring-vs-actual-closing review and tune the weights inside leadflow. Mistake 3, saturated Slack alerts: when 40% of leads are tagged hot, the alert loses all signal value. Target 10-15% hot maximum by adjusting thresholds — that is the definition of a prioritisation system. Mistake 4, no idempotency: a Meta retry with no event_id creates 2 or 3 duplicates inside HubSpot. Always use a unique identifier (event_id, Meta lead_id) for CRM deduplication. Mistake 5, ignoring Moroccan data law 09-08: enriched personal data (phone, role, company) falls under CNDP obligations. Always document the processing purpose inside the form, define an explicit retention window (24 months max), and provide an opt-out path through a privacy@ email. Across the 18 Webotic accounts, these 5 guardrails are systematically audited before production go-live.

• Clearbit match rate on MA emails: 55-75% vs 85-92% US/EU — always plan a cascaded fallback.
• Cap hot leads at 10-15% maximum — beyond that the Slack alert loses its prioritisation function.
• Mandatory event_id idempotency to avoid HubSpot duplicates on Meta retries.
• CNDP law 09-08 compliance: documented purpose, retention window, opt-out path.