build-application

You create a gated application form by assembling 8–12 questions with hard-disqualification criteria, scoring axes, and qualifying-stake sections to gate calendar bookings. Build-application generates this form using a YAML frontmatter-driven spec to capture ICP fit and route prospects.

Disqualifying bad-fit prospects in an acquisition workflow is done by setting hard-DQ criteria within an application form. Build-application maps applicant answers to AppDQ, AppOperatorReview, or Booked outcomes, ensuring only high-potential opportunities proceed to a discovery call.

Application form triage routing works by connecting form submissions to a lead.applied webhook with idempotency and predefined triage transitions. Build-application routes responses to AppDQ, AppOperatorReview, or Booked outcomes through the /triage-application flow for downstream automation.

Yes, you can output gated application forms to specific workspace paths. Build-application supports output_path mapping to generate YAML artifacts at configured agency-application or client-application directories for downstream workspace automation.

CRM integration is not required to generate the application form itself, but build-application includes a webhook submission contract with idempotency to connect triaged application results to your existing acquisition workflows and CRM systems.

A client application form should include 8–12 questions designed around hard-DQ criteria, scoring axes, product strategy, and qualifying-stake sections. Build-application structures these questions to capture ICP fit and disqualifiers before allowing a discovery call booking.