Marketing Optimization · Find

Conversion loop.

Reads what visitors do and asks the ones who leave why, so a page gets changed against a reason rather than against a hunch.

Experiential lensThe reason, not the rate modeled targets · not client results
.crft/Conversion loop
The reason, not the rate

what it is built to move

to the Scan's evidence — before any scope

4–10 wks

to a system in production, not a pilot

modeled targets · not client results · timings are CRFT's standard engagement

The work, today.

The dashboard says the page converts at 2.1%. It has said that for a year. Nobody can say what the other 97.9% wanted, so changes get made from whoever's opinion carried the meeting, shipped as an A/B test, and declared inconclusive six weeks later.

Where the Scan startsWith your analytics, your last round of page changes and what your sales team hears on first calls.

What the system is.

Four lines, the same four on every system we build. Where they fall is what makes this one different from the last one.

Session behavior — where attention goes, where it stops
Exit and abandonment points, by segment and by source
Short prompts to people who are leaving, asked in the moment
What sales hears on the first call that the page should have answered
01

What it reads

The signals it works from. Typically connects to Analytics, Session capture, Survey or feedback, CMS and CRM.

01Which drop-off points are worth asking about at all
02What to ask, and who to ask, without taxing every visitor
03Which stated reasons recur, versus one loud response
04Which fix is a page change and which is a product or pricing problem
02

What it decides

The calls it makes on its own, unattended, every time it runs.

A ranked list of drop-off reasons, in visitors' own words
The evidence behind each, quotable and traceable to a session
A change proposal per reason, with what it should move and by when
03

What it writes back

Into the tools the work already lives in.

04

Where the human stays

Marketing decides what to change and what to say. The system is not allowed to edit a live page — the line is there because copy is a brand decision, and because a system that both proposes changes and measures them grades its own work.

How we set it up.

The same four legs as every CRFT engagement — written for this system rather than in general.

  1. 01
    Scan48 hrs · evidence before scope

    We read the last year of page changes against what actually moved. Most teams find the changes and the movements are uncorrelated, which is the finding rather than the failure.

  2. 02
    Scope1 week · the report is the scope

    Scope is set by how many funnels and how much traffic. Below a few thousand sessions a month the asking carries the system and the behavioral half is noise.

  3. 03
    Build4–10 wks · production, not a pilot

    The asking ships first and runs for a month before anything is automated. The prompt has to earn a response without annoying the people who were going to convert.

  4. 04
    Compoundongoing · it reports, then improves

    Every change and its result teaches it which stated reasons actually predicted a fix. The reason list gets sharper about your buyer specifically, which no benchmark can be.

What we hold it to

Whether changes made against a stated reason outperform changes made against a hypothesis — and whether anyone can now say why the page loses people.

Get CRFT

Build the intelligence your company compounds on.

Five inputs, a published price, a report in 48 hours. Decide with numbers — then own what gets built.

Or just send us a note
What kind of system? Pick any that apply