Design Partner Program
Build a knowledge application around the way your team works. Bring an idea, prototype, existing product, or data; we'll connect your expertise, agents, people, and systems around a useful outcome.

You bring the people who know the work and its existing artifacts: research, requirements, records, policies, and decisions. Together we establish what the terms mean, how the concepts relate, and who owns the work. That foundation lets us agree meaningful intents and a practical first proof, using only the integrations it needs.
Agreed business intent and acceptance scenarios
Reviewed vocabulary, ontology, and sources
Permitted tools and actions
Evidence people can review
Operation and support requirements
Stakeholders, decision owners, and approvals

Aim for production readiness by proving one useful path first. Build on the knowledge and software you already have, then expand from evidence.
Review SME knowledge and work artifacts. Agree terminology, concepts, relationships, sources, and owners before accepting intents.
Name the actors, triggers, desired outcomes, constraints, and human decisions. Capture scenarios that show what success means.
Connect knowledge, behavior, and the experience through IKE’s Application Development Kit. Map integration meaning and access for the first workflow.
Review working software with its users. Verify evidence, ownership, permitted actions, customer boundaries, and operation against the agreed scenarios.
Retain decisions and rationale in the right customer or project context. Review improvements before reusing them in the shared method or application.
Self-service Hosted OpenClaw, assisted onboarding, and Design Partner engagement stay separate.
Start the 7-day IKE Professional trial when a managed OpenClaw agent is the shortest path. Payment method required.
Setup help for serious users who know the agent they want but need a working path.
Work with us to turn your expertise into a purpose-built application, with the systems and review steps your work needs.
Tell us what you want to accomplish, where the expertise lives, and who needs to use the result. We'll scope the application together.
A Design Partnership to build an application around a team's expertise, business outcome, existing systems, and required human review.
Site-wide definitions, relationships, and availability: /llms.txt.
Agent application (ike.product.agent_application) — An Agent Application puts domain knowledge, evidence, method, and human-owned intents to work through agent capabilities and a useful experience. Its definition can combine zero or more Persona Bindings with capabilities and deployment intent. Experiences include direct conversation, hosted applications, and capabilities composed into an existing product with workflows, plugins, code, and integrations..
Persona (ike.entity.persona) — Reusable operating instructions for agents and Agent Applications in IKE: role, behavior, tone, boundaries, default Collections, and default Skills..
Collection (ike.entity.collection) — Named set of documents and other knowledge that can be assigned to a Persona in IKE..
Skill (ike.entity.skill) — Reusable capability or instruction package available to an agent under explicit operating boundaries..
Tool (ike.entity.tool) — Executable capability available to an agent when it is configured in IKE..
Permission (ike.entity.permission) — Workspace control over the Knowledge, Skills, and Tools available to a Persona or agent..
We agree one business outcome, the expertise and systems it needs, what agents may do, and where people must decide. Together, we scope the application, build the first working path, and review it against the agreed outcome. Delivery scope and terms are agreed separately.
Teams with domain expertise and a real knowledge-work problem, ready to define a useful first application and review it with the people who will use it.