System integrator partnerships with explicit delivery boundaries.

This route is for system integrators with an identifiable customer or market need that may fit a Logic Unit industry platform or product-engineering capability. A partner should be able to own customer discovery, enterprise coordination and the implementation responsibilities it proposes.

The route is not an automatic reseller, certification or referral programme. Product fit, territory, customer ownership, enablement and commercial terms are evaluated for each opportunity.

• Opportunity-specific discovery and solution design.
• Implementation or rollout of a suitable Logic Unit platform.
• Integration with enterprise ERP, identity, payment, data or operational systems.
• Regional deployment and customer change support where responsibilities are agreed.
• Joint product engineering for a requirement that does not fit an existing platform.

Candidate opportunities should identify the target workflow, required product, users, sites, source systems, data sensitivity, transaction volumes, deployment constraints and customer decision process.

APIs, webhooks, sandboxes, identity options, data models and deployment patterns differ by platform and release. Logic Unit confirms what is currently supported only during the opportunity's technical review; unsupported gaps are labelled as configuration, integration, product change, custom work or no fit.

Integrator: customer relationship, discovery evidence, enterprise architecture coordination, proposed implementation scope and first-line responsibilities it accepts.

Logic Unit: product truth, supported technical interfaces, agreed product or engineering deliverables, defect boundaries and product-level documentation within scope.

Customer: business ownership, lawful data access, enterprise approvals, user acceptance, source-system participation and risk decisions.

Shared: solution design, dependency record, acceptance scenarios, cutover readiness, escalation and handover.

1. Qualification: confirm buyer, problem, authority, platform fit and commercial path.
2. Architecture: define systems of record, interfaces, identity, data flows, error handling and ownership.
3. Proof: test the highest-risk workflow or integration with controlled data where needed.
4. Delivery: agree configuration, migration, testing, training, cutover and support responsibilities.
5. Acceptance: reconcile data and transactions, close critical defects and transfer operational knowledge.

Enablement may include product walkthroughs, available technical documentation, a controlled test environment, solution reviews and escalation contacts when those resources exist for the selected platform and are included in the agreement.

No integrator should promise an API, certification, service level, compliance status or product feature before Logic Unit confirms it for the proposed solution.

• Identify who contracts, invoices and supports each component.
• Agree opportunity ownership, confidentiality and any account restrictions before joint selling.
• Separate platform, implementation, integration, third-party and ongoing support costs.
• Define intellectual property, data ownership, publicity and exit rights.
• Do not imply exclusivity, certification or customer authorization unless it is documented.

Begin with the customer or market problem, industry, geography, expected scope, systems involved, decision timeline, partner role and known constraints. Do not send production credentials or unnecessary personal data.

For a broader supplier assessment, use the technology partner selection guide before proposing the delivery model.