Back to landing page

Qualification path

Start the bounded qualification flow.

Qualification is the first structured step into the async-first path. This form routes to the runtime API and supports bounded evaluation only. It does not promise a pilot, a call, or an assessment offer.

Default path: async-first. No call required for basic qualification.

First paid step remains the Paid Pre-Pilot Assessment if the bounded evaluation supports it.

The runtime API is the source of truth for validation, scoring, and route decision.

Contact and company

Full name of the operator or buyer contact submitting this qualification.

Use a work email address.

Role of the submitting contact.

Legal or operating company name.

Primary company domain or website.

Current employee band.

High-level company sector.

Primary operating geography.

Current pressure and bounded fit

Describe the buyer-facing readiness or security friction clearly.

Primary active trigger for evaluation.

Current repo or environment readiness for bounded assessment.

Bounded context about repos, CI, evidence posture, or current stack. This is sent as optional runtime notes.

Declared scope category for the first bounded step.

Primary declared data or policy sensitivity indicator.

Stated urgency for decision and action.

Current readiness to buy the first paid unit.

Commercial motion compatibility
Is there an accountable internal owner for this work?
Is there a buyer or budget authority involved?
Does your team accept an async-first process?
Does your team accept the paid pre-pilot assessment as the first paid step?
If qualified, would you only consider a bounded pilot after assessment evidence?
Do you require live calls before proceeding?
Do you expect custom consulting before any paid first step?
Consent and submission

Submission path

Qualification is the first bounded step. The runtime API determines whether the next outcome is reject, nurture, risk review, or the paid assessment offer.