Which partnership track should we choose?
Choose based on your primary contribution: customer-specific delivery, resale, technical integration or audience referrals. If your business spans multiple tracks, describe that in your enquiry so responsibilities can be discussed together.
Can we deliver both pre-built and custom AI employees?
Use the workforce catalog to assess existing roles and the build-workforce page to explore custom scope. Discuss the configuration, integration and evaluation work needed for each customer before making a delivery commitment.
Are commissions, white-label access or certification automatic?
Do not assume these from the track name. Confirm eligibility, available program benefits and commercial terms directly with the partnership team before including them in a customer or business proposal.
Who supports the customer after launch?
Agree first-line support, platform escalation, incident ownership and change requests as part of the engagement. The customer should know which team owns each issue and what the agreed response commitments are.
What should we include in an enquiry?
Share your organization, primary track, customer or audience focus and one representative opportunity. For integrations, include the product and intended actions. Avoid sending credentials or confidential customer records.
How long does a deployment take?
Timing depends on the responsibility, available data, system access and acceptance tests. Scope these dependencies before agreeing a timeline; a demonstration is not the same as a production deployment.