Skip to content

EXP-SPARK-PROOF · 21 DAYS + FIELD TEST

How Spark Proof works

Three weeks to build. Two to four weeks in the field. Each week ends with a client check-in, so the client sees progress and decisions are made fast.

  1. Phase 1 · Build (3 weeks)

    01WEEK 1

    Sharpen

    Kick-off workshop, define target customer and core problem, agree what success looks like (e.g. 100 sign-ups or 5% price clicks), agree the test audience and channel, and set the minimum data needed before we make a call, name and lightweight brand.

    Lead
    Director of Strategy + Lead Designer
    Deliverables
    Idea brief, success targets, test plan, data threshold, name, logo, colours and tone.
  2. 02WEEK 2

    Build

    Launch landing page goes live and early testing starts, so tracking learns while we build. Working prototype of the core journey in Lovable, analytics and tracking set up.

    Lead
    Tech Lead + Developer
    Deliverables
    Live landing page, prototype in progress.
  3. 03WEEK 3

    Go live

    Full prototype live and in front of the test audience, whether through paid social and search, a closed group, existing customers or internal data. Interview recruitment opens from real sign-ups.

    Lead
    Tech Lead + Performance lead
    Deliverables
    Live prototype and full test running.

  4. Phase 2 · Field test (2–4 weeks)

    04WEEKS 4–7

    Field test

    The test runs and is optimised for 2–4 weeks, depending on the audience and how quickly the numbers settle. 5 recorded user interviews with people who signed up. Weekly data snapshots, and an early-signal check-in at the end of week 4.

    Lead
    Performance lead
    Deliverables
    Weekly snapshots, evidence report and readout session.

    ↔ Length flexes to the data

Lab note · Why the field test flexes

Audiences need time to respond and sign-ups arrive gradually. We agree a minimum data threshold in week 1 and run the readout when it's reached, not on a fixed date.

We don't call it until the data is in.

EVIDENCE REPORT · SL-XXXXPAGE 1 / 1

The evidence report includes

  1. F.01Results against the success targets agreed in week 1.
  2. F.02Audience performance: reach, engagement, conversion and cost per sign-up (where paid media is used).
  3. F.03On-site behaviour: sign-ups, price-point clicks, drop-off points.
  4. F.04Interview findings: what people understood, wanted and would pay.
  5. F.05A clear recommendation: go, pivot or stop, with next steps and a rough cost to build.
FIG. 3 — Readout
FIG. 4 — Weekly snapshot
Sign-upsIllustrative
W2W3W4W5W6
§Rules

Lab protocol.

PROTOCOL 01

Fixed scope

One core user journey, one landing page, one audience. Extra features go on a change request or into Spark Launch.

PROTOCOL 02

A prototype, not a finished product

It is built to learn, not to scale. Production work (security review, scaling, complex integrations) belongs in Spark Launch.

PROTOCOL 03

Field test

Runs for 2–4 weeks after the build, until the minimum data threshold agreed in week 1 is reached.

PROTOCOL 04

Test audience

Agreed in week 1. Paid media, a closed group, existing customers or internal datasets, whichever gives the most honest signal.

PROTOCOL 05

Payment

50% on booking, 50% at the start of week 3. Any media spend paid up front, at cost, to the client's own ad accounts where possible.

PROTOCOL 06

Ownership

The client owns the brand, prototype code and data on final payment. Each client gets a separate Lovable workspace.

PROTOCOL 07

Compliance

UK GDPR consent on any sign-up forms; clear wording that the product is in testing.

NEXT EXPERIMENT · SLOT OPEN

Got an idea worth testing?

Book a Spark