Inspired by the handbook-first operating model: the partner should understand how to position products, qualify clients, request deployment, protect quality, and escalate technical questions before entering a live sales cycle.
IronHeart.AI enables partners to deploy AI-native operational systems for their clients. We do not position the company as a chatbot vendor. We sell infrastructure, execution, and deployable service capabilities.
A client is qualified when they have a real audience, workflow, device, event, expert, or service line that can benefit from AI-native infrastructure.
Partners should not promise custom behavior before submitting a deployment request. IronHeart.AI validates feasibility, edge/offline needs, languages, integrations, hardware, and safety requirements.
Use the sales kits as a baseline, then adapt to the client industry. Keep language calm and outcome-based. Avoid hype. Avoid claiming a robot or AI clone can do everything.
For API/runtime projects, reference Hidoba Research docs: Voice Calls SDK, Texting API, and Dialog Analysis API. For robotics projects, capture latency, environment, device controls, offline requirements, and integration endpoints.
Open technical docsThis MVP uses mock data. Before production, partner access should include role permissions, NDA state, pricing visibility, lead registration, deployment approval, and billing rules.