byForja Tools · Call Cockpit

Call Cockpit

One screen during the 45-min call · decider at min 22-32 · score at hangup

Formula decider

Live · minute 22 to 32 · before the price, never after
1 · Profile (the editing cell decides)
2 · What do they need (Pilot only, locked when Artist is picked)
3 · Technical session needed? (who built the site · who holds domain and accesses · who fixes when it breaks — three no-idea = yes)
4 · Revenue signal (eligibility gates)
Pick the four answers.
Amounts are read live from Doctrine Pricing at quote time; this screen routes, it does not price. For the market multiplier and the actual quote, open the pricing calculator. Artist floor is Full: the menu disappears. A client who needs the session and refuses it does not get signed (AL rule, 11/08/2026).

CALL-SCORE

30 seconds, right after hanging up · copy the line into the prospect's CRM Notes
Local history (this browser only; CRM Notes stay the source of truth)
DateProspectDSFPORedo
Reading grid: filter or defect
  1. Selection operates on gates defined BEFORE the call. Someone who leaves because they fail a pre-set gate (stories/feed split refused, needs the session and refuses it, wants a discount, no financial surface) is the system working. Never a reason to self-question.
  2. Bad execution shows in the numbers AFTER. Someone who passes every gate and still leaves is on AL, and the five axes say where: which phase scores low, where in the call it cools.
  3. Thresholds (doctrine): 30-40% close on qualified prospects = the style is selecting. Under 15% = the execution is sabotaging. Selection cannot, by definition, reject 90% of people chosen by your own criteria: that is a leak, not a filter.
  4. One sentence: what makes the WRONG clients leave is the filter. What makes the RIGHT clients leave is a defect. You only know which one you are looking at by holding the numbers.
  5. Weekly ritual: one blocked slot, re-listen the best and worst call asking what could have been done better. Numbers over impressions. Any external explanation for a lost deal is probable attribution bias.
The anti-AL layer: five reflexes that save the relationship
  1. Client indecision is the default state of most humans, not stupidity. The bounded swipe exists precisely for that: it converts indecision into a 30-second binary choice. When it irritates, the system is doing its job.
  2. When a client reopens something validated, the answer is the contract (48h tacit validation, new billable request), never the irritation. The clause speaks so AL does not have to.
  3. "Il est con" is a signal about AL, not the client: it means AL just transposed his own operating mode onto someone who does not have it. Reframe: he does not have my system, that is exactly what he pays for.
  4. One thing goes wrong does not mean the relationship is over. The binary switch (all good, then dead) is the old pattern. Friction with a case (ticket, weekly call, month page comment) is friction absorbed; friction without a case becomes the switch. Give every friction a case.
  5. Never answer hot in writing. 24 hours or a call. The Frederique blow-up was an email chain.