Partner field guide
AI partner delivery models.
Choose the delivery model around how you serve the client. Then make responsibilities explicit across discovery, implementation, and ongoing operation. Branding alone does not define who is responsible for the work.
Three ways to work with Vixure.
| Model | How it works | Confirm before starting |
|---|---|---|
| White-label | Vixure provides delivery capacity behind your brand under an agreed arrangement. | Client-facing communications, billing, support, ownership, and how the delivery team is represented. |
| Referral | You introduce a client who needs implementation support. | Introduction consent, relationship boundaries, client contact, and any referral terms. |
| Co-delivery | Your team and Vixure deliver together with visible responsibilities. | Who leads each workstream, approves decisions, and accepts the finished work. |
Before discovery: define the relationship.
Name the client contact and the person who can approve scope. Agree whether Vixure joins meetings, how introductions are handled, and who sends updates. For consultants, distinguish the advisory roadmap from the implementation engagement.
Clarify who prepares the client proposal, who invoices whom, and which decisions need approval. Any referral compensation or resale arrangement should be agreed before the introduction or sale.
Before the build: define the work.
- Scope: inputs, outputs, integrations, exclusions, milestones, and acceptance checks.
- Data access: approved systems, permission levels, model providers, retention requirements, and access removal.
- Decision ownership: who approves architecture, changes, and client-facing actions.
- Deliverables: what code, configuration, documentation, and training are included.
- Ownership and licensing: distinguish client materials, custom work, reusable components, and third-party services in the engagement terms.
Before launch: define the operating model.
Identify who monitors the workflow, receives alerts, reviews outputs, and handles incidents. Agree support hours, escalation contacts, recurring costs, and the boundary between maintenance and new development. Do not assume that a build fee includes indefinite support.
Plan handover and exit as well: account ownership, access transfer, documentation, and what happens when the client changes providers.
Make the first engagement easy to understand.
Use the opportunity worksheet to identify the business task and open decisions. Then choose the MSP or IT consultant partnership path that matches your role.
Bring one client opportunity. Start with a conversation.
Tell us what the client needs, what you already provide, and where you need delivery support. We will discuss fit and the next step. No commitment on the first call.
Book a partnership callAn anonymized outline is enough. Please keep confidential client information out of the booking form.