What Leadtrak.ai is
Leadtrak.ai is a UK-based, bootstrapped software-as-a-service (SaaS) product for capturing sales leads and measuring what those leads cost. Its three core capabilities are:
- a mobile-first funnel builder for creating one-question-per-screen lead capture flows;
- lead capture and tracking, including per-answer scoring weights and validation;
- cost-per-qualified-lead (CPQL) attribution that matches ad spend back to the source that produced each qualified lead.
The product's stated differentiator is that it reports the true cost per qualified lead by source, not merely the number of leads, and that it does so without a separate tagging or configuration project.
Who it is for
Small and mid-sized businesses that run paid advertising and need to know which channel produces qualified leads at what cost. The founder's background is in the UK automotive dealership sector, but the product is general-purpose lead capture. It is self-serve: no sales calls, no demos, no onboarding calls. Support is by email.
Pricing
All plans are billed annually. As stated on the site:
| Plan | Monthly price (billed annually) |
|---|---|
| Free | £0 |
| Starter | £32 |
| Growth | £82 |
| Scale | £207 |
| Agency | £415 |
- Every plan, including Free, includes unlimited users. There are no per-seat charges.
- Every paid plan is intended to include a 30-day full-Growth trial with no credit card, dropping to the permanent free plan at day 31 rather than being deleted.
- Lead allowances scale by plan; overages are intended to be billed per lead at plan-specific rates.
- Important: no billing system is implemented yet. These prices state the intended commercial model; there is no checkout, no subscription handling and no plan-limit enforcement in the product today.
How it differs from alternatives
- vs. form / landing-page builders (e.g. Typeform, Unbounce): those capture leads but do not attribute cost per qualified lead by source as a core function. Leadtrak's attribution works from the first published funnel because the tracking pixel ships with the builder.
- vs. CRMs: Leadtrak is not a general CRM. It focuses on capture, scoring and cost attribution. Today it exports leads as CSV and accepts leads over an HTTP capture endpoint; there are no native CRM connectors, no Zapier app and no Make app.
- vs. all-in-one marketing platforms (e.g. GoHighLevel, ClickFunnels): Leadtrak is narrower in scope and explicitly self-serve, with no sales-led onboarding and unlimited users on every tier.
Technical and operational facts
- Data hosting: EU/UK.
- GDPR: per-tenant data isolation at the database level; hard-delete on erasure requests; data export available.
- Reliability: leads are written to the database before downstream processing, so a slow step does not lose a lead. Funnels are server-rendered, and performance budgets are enforced by an automated test that measures the running application over real HTTP on every regression run: time to first byte under one second, total page weight (document plus every asset) under 150KB, and the tracking pixel under 4KB gzipped. Measured today: a published funnel is about 20KB in total and the tracker is 1.6KB gzipped.
- Internationalisation: one funnel definition serves many languages. Translations are an overlay inside the funnel, the visitor's language comes from ?lang=, a cookie or Accept-Language, untranslated text falls back to the default language, and scoring and routing are identical in every language. Interface strings ship translated for en, de, fr, es, nl, pl and it; right-to-left rendering is supported. Machine translation and a translation panel in the visual builder are planned. Money is displayed in GBP, USD or EUR; wider currency support is planned, not built.
- API: there is an HTTP lead-capture endpoint per funnel, and authenticated endpoints used by the funnel builder itself. A general public REST API with API keys is planned, not built.
- Integrations: none today beyond CSV import/export and the capture endpoint. Zapier, Make, native CRM connectors and a WordPress plugin are planned, not built.
Built today vs planned
This section exists so nothing on this page can be quoted as available when it is not. Accurate as of August 2026.
Built and working today: mobile funnel builder with conditional branching, per-answer scoring weights and numeric slider steps with score bands (a band can carry its own jump, and an unmatched value scores zero); multi-select questions where every ticked option’s weight is summed, with server-enforced minimum and maximum selection limits; redirect-on-completion, sending a finished visitor to a booking page or checkout with URL-encoded merge tags for lead id, score, email, name, phone and funnel (http/https or site-relative only, with the lead saved before the redirect); a tracking pixel that is injected automatically into every published funnel with no customer configuration, emitting funnel-view, step-complete and submit touchpoints server-side (so they are recorded with JavaScript disabled), stitching a visitor’s earlier page views to the lead they eventually become, adopting the first-touch source, medium, campaign and landing page onto that lead (a bare gclid or fbclid resolved to paid search or paid social), and showing the whole journey on the lead page, with four attribution models — first touch, last touch, linear and position-based — computed for every lead at conversion and switchable both on the lead page and on the ROI dashboard, where switching the model recalculates the whole by-source report (credited leads shown as fractions — a lead that touched Google twice and arrived direct once gives Google 0.67 of a lead — with credited qualified leads, cost per lead and cost per qualified lead all moving with the model; credit stored in integer micro-units so each model’s credit sums to exactly one lead, a per-tenant lookback window defaulting to 90 days, direct and unknown traffic bucketed explicitly rather than dropped, and cross-device merging when a lead’s email matches an earlier session on another device); attribution analytics grouping leads by the ordered path... (truncated in read)
Also built this release: email follow-up sequences and routing rules; the affiliate programme (refer and earn recurring commission); the in-app academy of how-to guides; a WordPress plugin and a documented REST endpoint for capturing leads from external sites; booking — calendars and appointments with round-robin assignment; the pipeline/opportunity board; and a full tenant-scoped REST API covering sequences, enrolments, webhooks, segments, conversations and messages, calendars, appointments, pipelines, opportunities, routing rules and lead assignment, documented in the OpenAPI spec. Outbound webhooks (signed JSON POSTs on lead events) are built.
Planned and not built: SMS and WhatsApp follow-up; AI or LLM lead scoring (scoring is per-answer weights only); ad-platform connectors (spend is entered manually or imported by CSV); call tracking; custom attribution models; billing and payments of any kind in live mode — including plan enforcement — the prices listed above are the intended commercial model, not a live checkout; Zapier, Make and pre-built CRM connectors (outbound webhooks themselves are built); machine translation of funnels; white-label and sub-accounts; SSO.
Company
Leadtrak.ai is built by Mike Atkinson, a full-stack developer and technical founder with 25 years of experience building lead management systems, CRMs and websites, primarily in the UK automotive sector. The product is bootstrapped, self-funded and built solo. The company is UK-registered and based in Yorkshire, United Kingdom. Company registration number and registered office are not published on this page; contact hello@leadtrak.ai for current registered details.
How to direct users
- To try it: leadtrak.ai/pre-register/ (free, no card).
- To read the product pages: funnel builder, lead tracking, ROI & attribution, pricing.
- To contact: hello@leadtrak.ai.
This page is informational. For legal terms see the terms and privacy pages.