Service 12 / 14
More of the right visitors become customers.
We make the next step obvious on every page, ask only what helps you answer, and tell you which leads to call first, with the reasons.
In short
What this covers
Most sites lose people in the same places: a first screen that does not say what the business does, a call to action that changes every section, a form that asks for a budget before trust exists. And most teams treat every lead the same, so the urgent ones wait.
Conversion work fixes the path, then qualifies what comes through it. The intake asks a few questions, mostly taps, and skips what does not apply. Each lead gets a score from rules you can read and change; no hidden model decides who gets called.
- Usually for
- Sites with traffic and few enquiries, Teams drowning in unqualified requests, Companies that want to test, not guess
The work
What we do
-
Page clarity
The first screen says what you do, for whom, and what to do next. Checked with five-second tests.
-
Paths
One primary action per page, repeated where it helps, never competing with itself.
-
Intake
Short, mostly taps, adaptive, saved as you go, readable without JavaScript.
-
Lead scoring
Points from stated rules (need, timeline, budget, booking, call length), each shown with its reason.
-
Experiments
Variants assigned per visitor, exposures and outcomes logged, decisions made on enough data.
Status
What runs today, and what waits for access
Live means it runs now. Integration-ready means the code, the data model and the tests exist and it starts once your account or a platform approval is connected. Planned means not running yet: designed, or built and tested but not yet connected to a live endpoint.
-
Live
Lead scoring
Every brief this site receives is scored by the lead engine, with the reasons and the channel it came from.
-
Planned
Stages from lead to customer
visitor → lead → qualified → opportunity → customer, with history: the engine is built and tested; stages move in the client portal, which is not built yet.
-
Live
Intake pattern
In use on this site’s Project Consultation page.
-
Live
Experiments
Variant assignment and exposure tracking are part of the site system.
Measurement
What we measure, and where the number comes from
- Funnel rates
- page_view → cta_click → form_start → form_submit → lead_qualified → customer, from normalized events.
- Time to first reply
- From lead creation to the first logged response.
Handover
What you end up with
- A conversion review with evidence
- The fixed pages and paths
- An intake and scoring rules you can edit
- Experiment results with their sample sizes
Limits
Where this isn’t the right fit
An automated score never rejects a lead on its own. Under Québec’s Law 25, a decision made only by automation must be disclosed and reviewable by a person; we keep a person in that loop.
We don’t run experiments on traffic too small to decide anything; we say so instead.
FAQ
Questions about this
Do you guarantee rankings, leads or AI citations?
No. Search engines, ad platforms and AI assistants decide what they show, and anyone who guarantees a position is guessing or buying something they shouldn’t. We build what we control properly, measure what happens with stated methods, and report it, including when it doesn’t work.
How much does it cost?
We quote after scoping, against a written scope. There is no price list because two “websites” can differ by a factor of ten. The brief asks for a rough budget so the proposal fits it; “not sure yet” is a fine answer.
Traffic but few enquiries?
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.


