Skip to content

Our technology

The service runs on a platform we built for one job: proving what happened.

This is the same software your enquiries are recorded in and the same dashboard you log in to. Here is what it does today — and, just as plainly, what it does not do yet.

Audit trail

Entries cannot be edited
  1. Source capturedSystemCampaign and click reference stored with the enquiry
  2. Consent recordedSystemThe wording shown and the time it was accepted
  3. Checks runSystemFormat validation and duplicate search
  4. Contact attempt loggedPersonChannel, outcome and a note
  5. Qualification decisionPersonEach criterion answered, with the evidence
  6. Outcome reportedClientAppointment and sale result from your team
Illustration of the product interface · invented example values

System

What comes in, what happens to it, what comes out.

System diagram: enquiries, API leads and ad spend come in; the platform runs automatic checks, records human qualification and keeps an audit log on each lead record; the dashboard, CSV export and transactional email come out.

What comes in

  • Enquiry formSource, consent wording and click identifiers captured first-party
  • Inbound lead APIPer-client API keys
  • Ad spendManual entry or CSV import

The lead record

Platform
  1. Automatic checksDuplicates, format, consent on record
  2. Human qualificationVersioned criteria, written evidence
  3. Timeline and audit logEvery attempt, decision and change

Each client's data is isolated in the application.

What comes out

  • Client dashboardCalculated from lead records
  • CSV exportYour data, at any time
  • Transactional emailAcknowledgements, alerts, reminders

Capabilities

What the platform does today.

  • First-party source attribution

    Campaign parameters, landing page, referrer and advertising click identifiers are captured in the visitor's own browser session and stored on the lead record when — and only when — they submit an enquiry.

    • utm_source · utm_medium · utm_campaign · utm_content · utm_term
    • gclid · gbraid · wbraid · fbclid · msclkid
    • Landing page, referrer, first touch and last touch
  • A complete record for every lead

    Unique reference, timestamp, contact details, consent wording and version, validation status, qualification status, contact attempts, owner, follow-up history and sales outcome.

    • Activity timeline that cannot be silently edited
    • Audit log of material changes
    • Erasure workflow that keeps anonymous totals intact
  • Qualification by people, recorded by software

    The system suggests results only where facts are on record — consent, validation, duplicates, geography, budget. A person makes each decision and writes the evidence. There is no opaque score.

    • Client-specific, versioned criteria
    • Decision history kept, never overwritten
    • Dispute and review workflow
  • Duplicate and validity checks

    The same email address or phone number inside an agreed window is flagged as a duplicate automatically and excluded from counts. A person can reverse it. Format problems raise a review flag, not a verdict.

    • Normalised email and international phone matching
    • Configurable duplicate window per client
    • Unresponsive requires logged attempts
  • Client data separation

    Each client's data is isolated in the application: every query is restricted on the server to the clients a signed-in user belongs to. Client users see only their own records.

    • Role-based access: administrator, team member, client viewer
    • Server-side checks on every read and write
    • Per-client API keys for inbound leads
  • Reporting on verified outcomes

    The dashboard is calculated from lead records, not from advertising platform conversions. Each figure can be traced back to the enquiries behind it.

    • Spend by manual entry or CSV import today
    • Cost per qualified opportunity and per acquisition
    • Simulated demo data is always labelled

Event model

What a browser says, and what a person confirmed.

Each event carries a unique key, so the same event cannot be counted twice — whether a page is reloaded or a status is changed back and forth.

Recorded by

Browser · with consent

page_view
A page was displayed in the visitor's browser.
cta_click
A call-to-action button or link was clicked.
form_start
The visitor began filling in an enquiry form.
form_submit
The browser reported a successful form submission.

Recorded by

Verified in CRM

enquiry_received
The server stored a new enquiry.
qualified_lead
A reviewer recorded a QUALIFIED decision against the approved criteria.
appointment_booked
Staff recorded a scheduled appointment.
appointment_attended
Staff recorded that the appointment took place.
sale_confirmed
A sale was recorded as confirmed by the client.

Integrations

What connects today, and what is planned.

We would rather show an honest roadmap than a wall of logos. Anything marked planned is not built yet.

Connects today

  • Inbound lead API

    Available

    Any system that can send an HTTPS POST can create leads: Make.com, n8n, Zapier, a Google Sheets script, or a client's own website form. Each client has its own keys.

  • Ad spend CSV import

    Available

    Upload daily spend exported from Google Ads, Meta Ads or any platform. Re-importing a day replaces it.

  • Lead CSV export

    Available

    Download leads (filtered) as CSV for Google Sheets, Excel or another CRM.

  • Email (SMTP)

    Available

    Transactional emails only: enquiry acknowledgements, internal alerts and follow-up reminders.

  • Google Analytics 4 (browser)

    Available

    Browser events can be sent to Google Analytics 4, only for visitors who accept analytics.

  • Appointment booking link

    Available

    Enquiries can hand over to an external scheduling page. No availability is shown unless one is connected.

Planned · not built yet

  • Google Ads spend sync

    Planned

    Automatic daily spend from the Google Ads API. Until then, use CSV import or manual entry.

  • Meta Ads spend sync

    Planned

    Automatic daily spend from the Meta Marketing API. Until then, use CSV import or manual entry.

  • Meta Lead Ads

    Planned

    Native connector is not built. Leads can be bridged today with Make.com or n8n into the inbound lead API.

  • Google Ads lead forms

    Planned

    Native webhook receiver is not built. Leads can be bridged today with Make.com or n8n into the inbound lead API.

  • WhatsApp Business API

    Planned

    Not built. No WhatsApp messages are sent by this system. WhatsApp conversations can be logged manually as contact attempts.

  • Zoho CRM

    Planned

    Not built. Use CSV export, or the inbound lead API from a Zoho Flow / Make.com scenario.

  • Outbound webhooks (Make.com / n8n / Google Sheets)

    Planned

    Pushing lead events to other tools is not built. Use CSV export for now.

  • GA4 server-side verified events

    Planned

    Sending verified CRM events (qualified, attended, sale) to GA4 from the server is not built. They are recorded in the first-party event log.

Security and privacy

Built with care. Described without exaggeration.

  • Passwords are stored only as salted hashes, and sessions as hashed tokens in secure, HTTP-only cookies.
  • Access is role-based and checked on the server for every request.
  • All input is validated on the server; public forms are rate-limited and spam-protected.
  • Material changes to records are written to an audit log.
  • Consent wording and time are stored with each enquiry, and personal data can be erased on request.

What we do not claim

We do not advertise certifications or compliance badges we have not earned. The platform is designed around consent records, access control and deletion workflows; whether a specific use meets the law that applies to your business is something to confirm with your own legal adviser.

See whether a measured pilot fits your business.

A 30-minute consultation: your offer, your numbers, how enquiries are handled today, and whether we are the right fit. If we are not, we will say so.