Lead magnet prototype · #8 Your Ledger · capture conductor Captures email (sign-in link) or WhatsApp (one tap via the Bridge) · runs every other ask
All lead magnets
Prototype controls · device, browser, consent, visits, WhatsApp simulations
This visit Visit 1
Simulate
Your ledger · free, nothing gated

Everything you work out here, kept in one ledger.

Sites you check, keywords you price and plans you build collect here as you go. Save the ledger once and it opens on any device. We keep only what you typed, and you can clear it in one tap.

  • Use any tool on the siteSnapshots, price tags, plans and quotes land here, dated, with the numbers you saw.
  • Save it onceA sign-in link by email, or one WhatsApp message you send yourself. No password.
  • Come back when it suits youNo pop-up walls. Nothing more is asked on the visit you save. Later visits get one short question at most, and Skip always works.

Your ledger 0 items

Demo data

On the live site

One conductor decides which ask, if any, appears

Every magnet registers its asks with the conductor. Try the moments that matter on three page types. The log shows what was eligible, what won and why the rest stayed hidden. It reads your ledger above, so save it and watch the asks change.

Orchestration

How this fires

Your Ledger is two things. For the visitor, a saved workspace. For the site, the conductor: the only code allowed to show an ask, so ten magnets never stack into pop-up noise.

Who
s14 returning researcher (primary): keep and sync the ledger. s20 existing client: client mode, at most one ask a month. s21 known lead back from a follow-up: only the missing channel, with a reason. Fallback for s15 abandoners through the Bridge and message-me-first. It decides every ask for all 25 scenarios.
Where and when
Sitewide. The ledger tab sits top right on desktop and as a header icon on phones, only when items exist. From visit 2 with items: the tab plus one inline save ask. Desktop exit intent with a non-empty ledger shows “Keep your ledger?”. The Bridge sits inside every “send me this”; message-me-first follows an unsent tap, once per visit.
Channel
Email sign-in link (first on desktop) or one WhatsApp message the visitor sends (first on phones). Google or Apple sign-in only outside in-app browsers. Message-me-first is a message we start, so it carries its own unticked opt-in that names WhatsApp and the purpose.
What happens next
Sign-in link or WhatsApp reply within seconds. Interruptive asks stop for 30 days. From the next visit, one profiling question per visit at most, one every 7 days, and each answer changes the page. A Hot score (70+) brings a 20-minute call offer from the same strategist. Phase 2: return-visit changes and weekly alerts.
Journey simulator

Follow any visitor across visits

Pick one of the 25 scenarios and step through what the conductor does at each moment: the page, the trigger, the magnet that fires or stays quiet and why, the channel, what we ask, what we deliver and what follows.

Scripted sessions · demo data
Multi-visit journeys
    The ruleset

    Orchestration rules every magnet follows

    One trigger registry. Magnet blocks that are page content always render and don’t count as asks: a tool inside a blog post, the approval sheet on pricing. Everything that covers, displaces or interrupts goes through these rules.

    Rule 1 · Priority

    When several asks are eligible, the highest wins

    The others are suppressed for the rest of the visit. Ties go to the higher fit score × capture likelihood.

    1. Recover what they started. We Finished It’s step-2 resume, or message-me-first after an unsent WhatsApp tap, only after the 20-second ref check.
    2. Deliver what they already made. Save this result, send the rest, issue the quote they configured, keep your ledger.
    3. The magnet routed to this page and referrer. The routing primary for the scenario.
    4. The routing fallback.
    5. The Price Guide exit modal. Only when the ledger is empty and no other magnet has been used.
    Rule 2 · Caps and timing

    One interruptive ask per visit, at most

    Interruptive means it covers or displaces content: a modal, bottom sheet, exit intent or an auto-opened panel.

    Interruptive asks
    1 per visitA visit ends after 30 minutes of inactivity
    Never before
    30 s on site, and 40% scroll or a delivered result
    Never within
    5 s of typing in a form
    Never on
    /contact/, /thank-you/, legal pages, the client dashboard
    On phones
    Bottom sheet under 50% of the viewport, close button of equal weight. No exit intent.
    Inline cards
    1 per page view, 2 per visit
    Exit intent
    Desktop and fine pointer only. Arms after 8 s and 40% scroll, fires once per visit.
    Messages we start
    1 a day and 3 a week per contact, Mon–Fri 9:00–19:00 GSTDeliverables the visitor asked for don’t count; marketing does
    Rule 3 · Suppression

    Once we have a channel, we stop asking

    Tools keep working. “Where should we send it?” becomes one tap: “Send to +971 50 ••• 4213?”

    After capture
    No interruptive asks for 30 days, apart from delivery confirmations. Known contacts never see the exit modal.
    After a dismissal
    Closing an interruptive ask turns them all off on that device for 7 days. Closing the same magnet twice turns it off for 30 days.
    Promises
    Hold my audit’s single message and We Finished It’s one abandonment message are CRM rules a strategist can’t override.
    Clients
    No acquisition asks. Client-mode asks only, at most one a month.
    Non-buyers
    Partners, publishers, writers and journalists, once identified, see no buyer magnets. Agency and seller domains get automated outputs only.
    Referred visitors
    Nothing beyond their partner fast lane.
    Rule 4 · Progressive profiling

    After the first capture, one question per visit

    Starting the visit after the save, at most one every 7 days, in this order. Nothing more is asked on the visit someone saves. Each answer visibly changes the page. Never ask what the CRM already holds, and never ask budget before value has been delivered.

    1. The missing second channel, with a concrete reason: “Get rival alerts on WhatsApp the moment they happen instead of monthly email.”
    2. Industry. An inferred guess is shown as an editable assumption, never stored silently.
    3. Market and language.
    4. AED budget band, including “Not budgeted yet”, which leads to Hold my audit.
    5. Timeline.
    6. Role and approver.
    Rule 5 · Consent (PDPL)

    One purpose per box, nothing pre-ticked

    Federal Decree-Law 45/2021. If the operating entity is licensed in DIFC or ADGM, those regimes apply instead, so counsel confirms the final wording.

    Email · unticked, required“Email my ledger sign-in link to this address. LinkBuildingService.ae uses it only for this ledger and questions about it.” Below it: “If you don’t become a client, we delete your details after 24 months. How we handle your data.”

    WhatsApp the visitor starts · no boxFirst reply: “Thanks. We use your number only to reply to this request. Reply STOP to end.”

    WhatsApp we start · unticked box“Send me my ledger link on WhatsApp from LinkBuildingService.ae. I can reply STOP at any time.”

    Marketing · a further, separate box“Also send me occasional updates from LinkBuildingService.ae on WhatsApp (about one a month). I can reply STOP at any time.”

    Email
    One-off deliverables single opt-in. Recurring email double opt-in. Issued documents need a verified business email.
    Calls
    Only on request or at a booked time, Mon–Fri 9:00–18:00 GST, from a licensed UAE line, company named, recording notice, one call (Cabinet Resolution 56/2024).
    Identity
    Anonymous ID only after analytics consent, session-only if declined. Merges only on a verified email or an inbound WhatsApp message. No reverse-IP company reveal.
    Retention
    Tool runs and uploads 30 days. Unconverted leads 24 months, then deleted. DELETE on WhatsApp or by email erases.
    Rule 6 · Lead scoring

    Fit up to 50, intent up to 50, recalculated on every event

    Agency, seller, publisher, journalist and client contacts are routed by type and never scored for sales.

    Lead score points
    Fit
    Business-domain email or verified UAE/GCC company+10
    Target sector · UAE/GCC market+5 · +5
    Budget band AED 5–10k · 10–25k · 25k++10 · +15 · +20
    Start within 60 days · budget holder or approver named+5 · +5
    Intent
    Issued a VAT quote+20
    X-ray list worth AED 3,000+, or 20%+ dead delivered links+15
    Approved 5+ sheet rows · asked for a voice note or a cost · replied to an alert · approver link opened by a second person+10 each
    3+ visits in 14 days · pricing viewed twice+5 · +5
    Penalties
    Free-mail, no company−5
    Budget under AED 5,000 · no activity for 30 days−10 · −10
    Hot70+The rota strategist replies personally within 2 business hours, in the visitor’s channel.
    Warm40–69The automated deliverable plus one personal note.
    Nurtureunder 40The deliverable only, plus alerts if they opted in.
    Rule 7 · Routing

    Every hand-off carries the timeline and the deliverable

    So nobody has to ask “what’s your website?”. One strategist owns each contact for good.

    Senior or sector-trained
    Quotes over AED 25,000 a month, group portfolios, regulated sectors (DLD/RERA, DHA/DoH, VARA), manual actions
    Arabic sessions
    The Arabic strategist on shift. Otherwise the approved Arabic text template now and the voice note on the next shift.
    By type
    Agencies to the partner manager, competitors to the trade desk, publishers and writers to the supply roster, journalists to the PR lead, clients to their account manager
    Capacity
    The rota drives every human promise. Daily caps: 18 voice notes, 6 X-ray sign-offs, 10 plan confirmations per strategist. Fit score orders the queues.
    Rule 8 · Kill switches

    Every ask can be switched off on its own

    Turn one off and run the host pages above again: the decision log shows it skipped. Each magnet also has a cost ceiling, and the rules are reviewed every month.

      View the trigger registry as JSON (read-only)
      
                
      Behind the scenes

      What happens after the save

      The follow-up, the card the strategist receives and the numbers that tell us whether the conductor works. Previews follow your own ledger above.

      Demo data · sample ledger

      Follow-up sequence

      Only what the visitor asked for, in the channel they chose. Messages we start go out Mon–Fri 9:00–19:00 GST, never more than one a day.

      Email · sign-in link

      WhatsApp · the visitor sent it (Bridge)

      WhatsApp · message-me-first template

      Follow-up sequence by day and channel
      WhenChannelMessageRule
      Day 0 · secondsEmail or WhatsApp replySign-in link, or the WhatsApp reply with the purpose line, STOP and the ledger link.Deliverable asked for; outside the cap
      Day 0 · first replyWhatsApp buttonsA separate question: [Yes, one update a month] [No, just this]. Logged with a timestamp.Marketing needs its own yes
      Day 0 · within 1 minWhatsApp templateMessage-me-first only: the named strategist writes first with the visitor’s context and one easy question.Unticked opt-in naming WhatsApp and the purpose
      Next visitOn site, inlineOne profiling question, first the missing channel with a reason. Nothing is sent.One per visit, one per 7 days
      Score 70+Visitor’s channelRania offers 20 minutes, opening with the visitor’s own numbers. One follow-up at most.Hot routing, 2 business hours
      Phase 2 · weeklyEmail, double opt-in“Since 3 Nov, your site gained 4 referring domains and lost 1.” Quiet weeks send nothing.Needs the saved ledger and its own opt-in

      Sales hand-off

      What the strategist sees the moment a channel is received: the merged timeline, consent records, score and route. Built live from your ledger.

      KPIs to watch

      Targets are starting assumptions to test in the first 90 days. A capture counts only when a channel is received: a verified email or an inbound WhatsApp message. Taps are micro-conversions.

      Captures per 1,00021Sessions, sitewide, across all ten magnets
      Interruptive per visit0.3Average; the hard cap is 1. A guardrail, lower is better
      Ledger save rate18%Visitors with 1+ item who save by email or WhatsApp
      Bridge tap to send55%WhatsApp taps that become an inbound message with the ref
      Unsent taps recovered20%Message-me-first sheets that end in an opted-in number
      Two channels35%Contacts with both email and WhatsApp within 30 days
      Profiling answers45%Questions answered rather than skipped
      Dismissal rateunder 60%Interruptive asks closed with “No thanks”. Review the rule if it rises

      Guardrails: STOP rate under 3%, the WhatsApp number’s quality rating stays high (messages we start pause automatically at medium), and capture is never counted on a tap. Monthly rule review; A/B the save ask against no ask before full rollout.