​

Technology Partners

VH3 AI works with partners who want to build useful software around field service operations: product teams, integration builders, implementation specialists, automation consultants, and sector experts. The opportunity is simple. Field service businesses already hold the knowledge that makes their operation different: job history, engineer experience, customer risk, site context, service patterns, account relationships, and commercial signals. VH3 AI turns that operational record into a prepared intelligence layer. Partners build the products, workflows, portals, and connected services that put that intelligence to work. This page defines the partner paths we are opening as the programme launches.

​

Who technology partners are

Technology partners build on VH3 AI as a platform. They use the API, MCP server, agent starter kits, workflow tools, and UI components to create software that helps field service teams act on operational intelligence. Typical partners include:

• Software vendors building field-service, FM, compliance, asset, finance, CRM, workforce, or customer-experience products.
• Integration builders connecting VH3 AI to systems customers already use.
• Automation consultants creating workflows that route alerts, reports, cases, and operational actions.
• Implementation specialists helping customers configure the layer, train teams, and ship first workflows.
• Sector experts building repeatable solutions for housing, facilities management, fire and security, retail maintenance, compliance, or specialist service operations.

The best partners understand the work as well as the software. They know why a repeat visit matters, how a customer escalation forms, where dispatch loses time, and what evidence an account manager needs before a review.

​

What partners can build

Partners can build any surface that benefits from prepared field-service context:

• Embedded intelligence inside an existing software product.
• Customer and subcontractor portals with scoped job feeds, reports, and account views.
• Operational dashboards for dispatch, account management, engineering, finance, or leadership teams.
• Workflow automations that turn sentinels, reports, and cases into owned follow-through.
• Connectors between VH3 AI and FMS, CRM, finance, communication, BI, or document systems.
• AI-assisted tools that help teams search precedents, brief engineers, draft client updates, and investigate patterns.
• Sector-specific packages for repeat operational problems that appear across many customers.

The common thread is the same: partners build on top of one tenant-scoped operational model, keeping customer intelligence connected to the platform source of truth.

​

Partner paths

The programme separates partner type from partner level. Partner type describes what the partner does. Partner level describes how mature and verified the relationship is.

​

Partner levels

Partner levels indicate how far the relationship has progressed. Levels are granted by VH3 AI and may vary by partner type.

​

Commercial relationship models

Partner type and partner level describe the public relationship. The commercial model is agreed separately in writing. At launch, partner relationships may follow one or more of these models: Referral relationships are the simplest model. A valid introduction is normally a direct, warm introduction to a customer contact where VH3 AI has no active opportunity already in progress. Any referral payment, revenue share, or commercial entitlement depends on the written agreement in place and on the customer becoming a paying customer. Implementation, integration, and technology partnerships usually require a broader review: technical surface, customer scope, data handling, support responsibilities, commercial model, and badge use.

​

How partner agreements work

The public badge is only one part of the relationship. Before a partner is active, VH3 AI expects the written partner agreement or schedule to define:

• Parties and effective date. Who the agreement covers and when it starts.
• Scope and appointment. Which partner path applies, whether the relationship is referral, delivery, integration, technology, or strategic, and whether any territory or customer segment is agreed.
• Authority. Partners may present VH3 AI fairly. Authority to bind VH3 AI, negotiate on VH3 AI’s behalf, or make product, pricing, security, or roadmap commitments must be granted in writing.
• Opportunity registration. How introductions, leads, customer opportunities, or partner projects are submitted and accepted.
• Customer contracts. Customer pricing, commercial terms, and final acceptance remain at VH3 AI’s discretion unless a separate written arrangement says otherwise.
• Commercial schedule. Any commission, referral payment, implementation fee, revenue share, or other commercial model is documented separately and tied to the agreed scope.
• Conduct and compliance. Partners must comply with applicable law, avoid misleading claims, respect marketing rules, and protect VH3 AI’s reputation.
• Data protection. Personal data shared with VH3 AI must be collected lawfully, with a valid basis and appropriate notice to the data subject.
• Confidentiality. Pricing, customer data, product plans, commercial terms, and shared partner materials are treated as confidential where marked or reasonably understood as confidential.
• Intellectual property and brand. VH3 AI owns its platform, documentation, names, logos, and brand assets. Any badge or logo use requires approval.
• Suspension and removal. VH3 AI may suspend badge use, certification, programme access, or commercial participation if a partner breaches the agreement or creates customer, security, legal, or reputational risk.

This structure keeps the programme clear for customers and fair for partners. It also avoids confusion between a referral-only relationship and a partner that has been certified to build or deliver on the platform.

​

Technical foundations

Partners build against the same surfaces used by VH3 AI’s own products and agents:

• REST API for search, jobs, contacts, sentinels, reports, briefings, Connie, cases, teams, users, and authentication.
• MCP server for AI tools such as Cursor, Claude, and other MCP-compatible clients.
• Agent starter kits that give coding assistants the platform context they need.
• n8n node and workflow templates for operations-friendly automation.
• Native integrations for connected business systems.
• Field-service UI components for rendering operational intelligence consistently in React applications.

Good partner products use the fastest surface for the job. Discovery endpoints handle lookup, filters, feeds, and triggers. Synthesis tools handle narrative, investigation, and explanation. Cases and teams turn findings into owned work.

​

Certification and trust

Customers need to know that a partner-built integration or app handles operational data correctly. Certification focuses on safe, useful delivery and practical review. A certified partner implementation should show:

• Correct authentication pattern for the surface being built.
• Server-side handling of API keys, with no customer secrets exposed in browser or mobile code.
• Tenant isolation and scoped access patterns.
• Clear handling of user roles, teams, and customer visibility where relevant.
• Reliable use of fast discovery endpoints before slower synthesis steps.
• Evidence and citations preserved when presenting AI-generated answers.
• Sensible timeout, retry, and error handling.
• No exposure of internal IDs in customer-facing interfaces.
• Brand and badge usage that matches the approved partner status.

Certification is designed to protect the customer, the partner, and the platform. It also gives buyers confidence that a partner has built against VH3 AI in the right way.

​

Badge usage

VH3 AI partner badges identify an approved relationship. They should make the relationship clearer and sit alongside a plain explanation of what the partner actually does. Use the badge category to describe the partner path:

• Technology Partner
• Integration Partner
• Implementation Partner
• Strategic Partner

Use the partner level to describe maturity:

• Partner
• Certified Partner
• Premier Partner
• Elite Partner

Badge use requires approval from VH3 AI. Partners should use only the badge and level they have been granted, keep it visually unmodified, and remove or update it if the relationship changes.

​

Badge examples

The badge text should match the partner relationship exactly. Category badges describe the partner path. Level badges describe maturity.

​

Partner levels

​

Partner categories

​

Launch programme

The partner programme is opening in stages. Early partners will help shape the certification process, reference implementation patterns, badge rules, and repeatable solution packages. The first wave is focused on partners who can build or deliver one of three things:

• A real customer workflow on top of VH3 AI.
• A repeatable integration with a system field service teams already use.
• A product or portal that embeds VH3 AI intelligence into an existing customer surface.

We are especially interested in partners with field-service domain expertise. The strongest applications start with a clear operational problem and a specific customer workflow.

​

Become a partner

If you want to build with VH3 AI, start with the builder docs and then contact the team with the partner path you are interested in, the customer problem you want to solve, and the technical surface you expect to use.