Skip to content
FREN

No cookies, no trackers.

The method

No tool built on a hunch.

The signals decide whether an app gets built. Six agents pass the baton, from the first signal to the app online. Each leaves a dated trace and only hands over on evidence.

  1. 01Watcherreads the signals, every day
  2. 02Analystinvestigates and scores out of 21, every Monday
  3. 03Publisherputs the app’s page online
  4. 04Spreadershows the page to the people it concerns
  5. 05Judgecounts the sign-ups, every day
  6. 06Builderbuilds the app, step by step

01 · Watch

Five families of signals, never just one.

Every day, the Watcher reads what launches, what people ask for, use, pay for, and must comply with. A lead has to rise in at least two families, two weeks running.

  • 5 families
  • One reading a day
  1. 01The signal

    15/21E-invoicing, WooCommerce and PrestaShop

    What people useseen 4 Nov 2026

    Creating the invoice in the right format is common; sending it and tracking its status, much less so.

    What people pay forseen 4 Nov 2026

    On other shop platforms, merchants already pay for an e-invoicing app.

    What becomes mandatory1 Sept 2027 · impots.gouv.fr

    Issuing e-invoices becomes mandatory for French SMEs and micro-businesses.

    Seven criteria, 0 to 3week 46

    • demand3
    • payment2
    • reach2
    • feasibility2
    • edge2
    • AI resistance3
    • exit1

    15 out of 21test threshold: 14

    Every day, the Radar reads what people ask for, pay for, and must comply with.When the same problem shows up everywhere, it gets a score out of 21. Here: 15.

0:00

02 · Score and measure

Seven criteria, a score out of 21, a bar set in advance.

Every Monday, the Analyst investigates: who already pays, who complains, why now. Each lead is scored three times, independently. At 14 out of 21, the app’s page opens; before the first visitor, the release ranks are written down.

  • 7 criteria, 0 to 3
  • 3 independent scorings
  • Bar at 14
  1. 02The bar, then the page

    Ranks written before measuring7 days

    • First25 sign-ups or more
    • Next10 to 24 sign-ups
    • In its turnfewer than 10 sign-ups
    written 10 Nov 2026, before the first visitor
    facture-electronique.anotherframework.dev

    WooCommerce plugin and PrestaShop module: your e-invoices, compliant without a second thought.

    Every paid order creates its Factur-X invoice and sends it to your approved platform.

    Save my spot

    live

    Before the first line of code, the ranks are written down.Then the app’s page goes live, at its own address.

0:00

03 · Measure demand

One week, three ranks written in advance.

Those who need it reserve their place. Every day for seven days, the Judge counts the confirmed sign-ups, then ranks the app: first, next, or in its turn.

  • 7 days
  • Ranks written in advance
  1. 04The verdict
    The Judge · one week of measuring

    Every day, a count of confirmed sign-ups.

    1. D1
    2. D2
    3. D3
    4. D4
    5. D5
    6. D6
    7. D7
    In its turnfewer than 10Next10 to 24First25 or more

    On day seven, the app takes its rank.

    Sign-ups order an app, they never remove it: a less awaited app comes out in its turn.

    Every day, the Judge counts the sign-ups.On day seven, it ranks the app: first, next, or in its turn.

0:00

04 · Build

Built by agents, checked before each release.

A lead that is kept becomes a mission of its own. runward makes the agents ask for the team’s decisions, and a check that is not a model refuses what no longer has its proof.

  • Success criterion written at the start
  • Every important decision recorded
  1. 05runward
    Tests: passedin the team’s delivery chain
    Reading of the check

    runward-demo-renaming

    Refused by the check
    branch of the change · commit 97fce96 · check of 10 Nov, 15:52

    The check refuses this version, for the reasons that follow.

    • First-version measurements: a cited piece of evidence is refused by the check.runward/floor.md · line 22
    • Security assessment: a cited piece of evidence is refused by the check.runward/governance/threat-model.md · line 50

    Public repository runward-demo-renaming · public run no. 15

    The team’s record
    runward/floor.mdline 22
    −file:code/src/core/domain/guard.ts#guardFields
    +file:code/src/core/domain/guard.ts#applyFieldGuards
    runward/governance/threat-model.mdline 50
    +file:code/src/core/domain/guard.ts#applyFieldGuards

    runward-demo-renaming

    Nothing is blocking

    according to the team’s requirements · branch of the repair · commit 0b56196

    runward makes the agents ask for the team’s decisions.What no longer has its proof does not pass. Two lines fixed, and nothing is blocking.

0:00

05 · Publish

Put online, with its versions.

Dropyour puts it online from the conversation, with its versions. A server app can be delivered with a runward evidence file that its owner, client or auditor can re-verify without us.

  • This site runs on Dropyour
  1. 06Dropyour
    Your AI

    Put my clients, my schedule, my quotes and my invoices online, and link them.

    System · your tools
    Clientslive
    k3v9q2xa.dropyour.site
    Schedulelive
    m7t2h4wd.dropyour.site
    Quoteslive
    p9c4x6rb.dropyour.site
    Invoiceslive
    d2n8v5ys.dropyour.site

    Quote accepted: Invoices is notified.

    On Dropyour, our tools are live, and every change keeps a fallback version.

0:00

Questions

Three objections.

Why set leads aside so fast?

Because a lead whose signals fall back does not deserve your wait. Ten measured leads are better than one tool built on a hunch that you would not use.

Why not publish everything?

The method, the scores and the set-aside leads are public. The full investigations and the settings stay internal.

Is a score of 15 a promise?

No. It is a reason to move forward. Signals can fall back, and the score with them: we publish that too.

The proof is the apps.

The ones being measured, the ones running, and the ones we set aside.

See the apps