Qualify demand
Capture company, volume, model needs, and support expectations before quoting.
The enterprise layer is where custom limits, higher-value support, and team needs can be handled without cluttering the first retail purchase experience.
Higher-value accounts need a different intake path.
Capture company, volume, model needs, and support expectations before quoting.
Separate enterprise limits from retail defaults so teams can scale safely.
Route qualified accounts into support-assisted setup and commercial follow-up.
Collect company details, use case, team size, and support expectations before pricing negotiation starts.
Separate logic for quota, rate limits, or dedicated commercial handling without contaminating retail defaults.
The AI consultation system can become the intake layer here once the dedicated OpenMagic brand route is configured.
Collect enough to qualify demand without turning the intake into procurement theatre.
Company name, team size, region, and whether the request is for internal use, client work, or product integration.
Main model interests, rough daily volume, expected peaks, and whether coding tools are part of the workflow.
Invoice requirements, contract expectations, dedicated support needs, and whether monthly settlement is required.
The final submit can route into the future AI support flow first while the dedicated enterprise CRM path is still being assembled.
This is now wired to the business database through the dedicated enterprise submit endpoint.