build-applicationlisted

# /build-application — Application Form (the Calendar Gate) > **Purpose.** Build the application form that gates every discovery call. Output is the form spec: 8-12 questions, hard-DQ logic, scoring rubric, skip-logic, conversational copy, and the submission webhook handler that hands off to `/triage-application`. Per `INVARIANTS.md` N-12, no calendar booking happens without the application — every booking path funnels here. Per A-13, hard-DQ trips do **not** auto-archive; they route to operator review by default. > > **Bar.** A B2B founder fills this form in 4-7 minutes; the operator (or workspace on operator's behalf) makes a Booked / AppDQ / AppOperatorReview decision in <90 seconds without re-reading the prospect's DMs. > > **The load-bearing role.** This form is what stops the calendar from filling with $0 prospects. It is the highest-leverage quality control mechanism in the acquisition FSM — every other lever (DM sequence, qualification thread, calendar gate) is upstream signal collection; this is where the workspace converts signal into a binding routing decision. Skip it and close rate collapses, operator hours torch. ## When to invoke - New operator onboarding — build `agency-application` once `ideal_customer_profile.agency_icp` ≥ 70 and `product_strategy.service_tier` ≥ 70 - New retainer offer launched or repriced ≥ 20% — qs question and decline-down routing depend on price band - Application completion rate < 30% — friction audit; redesign Step 6 - Triage-to-Bo