Does a manufacturer plus consultancy joint venture make sense for EMvelope? An honest assessment, three deal structures, the sequencing that protects the IP, and the register that binds the document family together.
| Rev | Date | Description | Status |
|---|---|---|---|
| 1.1 | 2026-07-06 | Candidate-company names generalised to partner archetypes; documents 005-007 issued and added to register and navigation | Current |
| 1.0 | 2026-07-06 | First issue: partner-fit analysis, three deal structures with recommendation, conflict and deal-killer register, 90-day pitch sequence, document register and folder conventions | Superseded by 1.1 |
A global insulated-panel manufacturer and a global data-centre delivery consultancy are close to the ideal complement for what AVE holds: the two of them own manufacturing scale and hyperscaler access respectively, and neither owns the thing AVE owns, which is the verification method, the service model and the software layer. But this only works if three conditions are met before the first meeting is booked.
Condition 1: file before you pitch. The EMprint priority application (CS-002 §02) must be filed before any technical disclosure to either party. An NDA is necessary but not sufficient: NDAs leak, are hard to enforce against ideas absorbed in good faith, and do not restore lost patent novelty in every scenario. The teaser deck can travel early because it describes the problem and the market; the method travels only after filing.
Condition 2: resolve the consultancy-independence question openly. A cost and project-management consultancy earns its position through independence from products it might help clients procure. Equity in a façade product it could later be specifying is a genuine conflict, and pretending otherwise would poison the relationship. §04 sets out the workable shapes: a market-development agreement, an arm's-length venture vehicle, or paid launch-delivery partnership with disclosure and recusal protocols. Raise it in the first meeting; let them choose their shape.
Condition 3: AVE keeps the service and the dataset. The recurring-revenue engine (Pillar 2) and the correlation dataset are the compounding assets. Whatever structure emerges, panels can belong to the JV; EMprint services, the monitoring software and the aggregated learning stay with AVE, licensed into the venture, never assigned. A structure that pools everything hands the smallest partner's crown jewels to the largest partner's balance sheet.
Brings the concept and document family, the EMprint method and filings, the service and SLA architecture (docs 02 and 03), and the software layer: digital twin, dashboards, monitoring integration. The natural builder of X-SENSE and the Continuum ops platform.
Brings insulated-panel lines the RD-001 concept was designed around, fire and product certification muscle, global logistics, data-centre envelope track record, and the balance sheet for the §RD-001 test programme.
Brings hyperscaler and colo relationships, cost-benchmark credibility, programme-delivery presence on live data-centre projects worldwide, and early sight of where EM requirements are appearing in briefs.
The complementarity test is that no party can execute the whole play alone: AVE lacks factories and channel; a manufacturer lacks the verification method, the service architecture and the software; a consultancy manufactures nothing and holds no product IP. Interlocking dependency is what makes a venture stable, and this one interlocks cleanly if the asset boundaries of §01 Condition 3 are respected.
| Structure | Shape | Strengths | Weaknesses |
|---|---|---|---|
| S1 · Three-way NewCo JV | NewCo holds product rights via licence-in from AVE; manufacturing agreement with Party B; services agreement with Party C. Indicative equity: AVE 30-40% (IP contribution), manufacturer 45-55% (capital, plant), consultancy 0-15% via an arm's-length vehicle if at all. | Full alignment; single brand; shared risk on the test programme. | Three-way governance is slow; consultancy equity strains independence; valuation of AVE's IP contribution is contested at the moment of least leverage. |
| S2 · Licence + service split | Exclusive product licence to the manufacturer (fields and territories staged, minimum royalties, milestone-based reversion). AVE retains and operates the entire Pillar 2 service business; consultancy engaged under a market-development agreement. | Each party keeps what it is best at; AVE keeps the compounding assets; fastest to sign; cleanest for independence. | Weaker capital injection into AVE; manufacturer may push to bundle services; requires disciplined brand co-existence. |
| S3 · Staged development agreement | Funded feasibility to the RD-001 M12 gate (manufacturer funds coupon-to-assembly testing; AVE contributes method and design), with pre-agreed option terms that convert into S1 or S2 on gate success. | Smallest cheques, biggest learning; prices the IP on evidence rather than argument; easy first yes. | Option terms must be negotiated hard now, when they look theoretical; risk of drift without milestone discipline. |
| Risk | Assessment & handling | Severity |
|---|---|---|
| Manufacturer absorbs the idea and goes alone | The largest single risk. A panel giant has R&D teams who will see the concept's outline in one meeting. Handling: priority filing first (Condition 1); the correlation dataset never leaves AVE; the pitch emphasises that the moat is the method, service book and software, which are slower to replicate than a gasketed joint; staged disclosure (teaser, then filed-method deep-dive, then data room). | High |
| Consultancy independence conflict | Equity in a product it may later specify compromises the advisory brand and could breach client agreements. Handling: default to fee-based market development with disclosure and tender-recusal protocols; equity only via a genuinely arm's-length vehicle, publicly disclosed. This is raised by us, early, as a mark of seriousness. | High |
| Competition law | Exclusivity with a major panel manufacturer, plus genuine-parts and certified-installer conditions from doc 02/03, needs clearance in each launch market. Handling: competition counsel opinion before term sheet; staged territorial exclusivity; objective-justification wording already drafted into the SLAs. | High |
| IP valuation asymmetry | AVE contributes paper against others' plant and channel. Handling: earn-in mechanics tied to RD-001 gates (M6 coupon, M12 assembly, M18 weathering); royalty floors; anti-dilution on the service carve-out. | Medium |
| Three-way governance drag | Vetoes multiply; velocity dies. Handling: the S3-then-S2 path keeps day-to-day control bilateral; the consultancy relationship is contractual, not board-level. | Medium |
| Brand and claims discipline | A sales force excited by "EMP" language creates the exact liability RD-001 §02 forbids. Handling: the phenomena table becomes a schedule of every agreement; marketing sign-off sits with a named technical authority. | Medium |
| Archetype discipline | This family deliberately names no candidate companies: partner archetypes only. It may not be the obvious two. Maintain a longlist of at least three credible manufacturers and two consultancies, verify current corporate facts about any candidate before first contact, and let legal clear each named approach individually. | Housekeeping |
| Audience | Lead documents | Withhold until |
|---|---|---|
| Manufacturer executive | Doc 01 §15 board note; doc 02 §01 three-pillar page; this doc §03 | Full RD-001 build-up and CS-002 claim architecture: post-filing, under NDA |
| Manufacturer technical | Doc 01 §02 phenomena table and §10-§11 test programme | Joint geometry detail and EMprint procedure: post-filing |
| Consultancy leadership | Doc 01 §15; this doc §02 and §04 (independence options led by us) | Rate cards and tier pricing (doc 02 §04): term-sheet stage |
| Both, at diligence | Docs 02 and 03 in full; RD-001 in full; data-room protocols | Correlation dataset: never; it is inspected on AVE systems only |
Drop all four files into one folder and every cross-link works: the family navigation bar at the top of each document, and the cards below, use relative links to stable filenames.
This document. Partner-fit verdict, deal structures, pitch sequencing, and the register you are reading.
The technical foundation: Concepts A and B, physics honesty table, 20 design deliverables, test programme, board note.
The commercial engine: EMprint patent and trade-secret strategy, service tiers, rate card, Tier 2 SLA skeleton, EAD plan.
The flagship contract: 19 clauses, severity matrix, availability regime, cybersecurity terms, worked credits.
Interactive model: tier fees, billable overage, consumables and portfolio recurring revenue, with credit-exposure caps.
The control schedule behind Continuum clause 5: architecture, patching, incident response, insurance limits, audit rights.
The pre-filing-safe external deck: problem, market and category gap only. Contains no protectable method detail.
| Convention | Rule |
|---|---|
| Stable filenames | Filenames carry the family number and document code but never the revision, so links between documents survive every version bump. The revision lives in three places inside each file: the eyebrow, the revision table, and the footer. |
| Revision tables | The revision table at the top of each document is the single source of truth for what changed and when. Superseded rows are retained, never deleted. |
| Numbering | 00 hub, 01 technical, 02 commercial, 03 contracts. File 04 is intentionally unused so that file numbers track document codes from 005 onward (this hub carries code 004 at position 00). Issued: 005 pricing calculator, 006 Schedule F, 007 teaser. Next reserved: 008. |
| Circulation classes | 00, 02 and 05 are internal-only until legal review. 07 is the only pre-filing external document. 03 and 06 travel at diligence stage only. 01 §15 may be excerpted for executive audiences. |
| Idea | Sketch |
|---|---|
| Irish innovation funding first | Before giving equity away, price the alternative: Enterprise Ireland and EU innovation instruments routinely fund exactly this profile of deep-tech feasibility work. A grant-funded M0-M6 coupon programme raises AVE's leverage in every subsequent negotiation, because the first gate arrives already paid for. Verify current programme terms before relying on this. |
| Fourth corner: an insurer | Docs 02 and 03 already sketch insurer value. Bringing a specialty insurer into the S3 stage as a design partner (not equity) creates demand-side pull the manufacturer cannot ignore and validates the SLA economics independently. |
| Pilot-host as kingmaker | A hyperscaler or colo willing to host the M18-M24 pilot is worth more than either corporate partner's logo. Consider offering the pilot host most-favoured pricing on the first commercial deployment in exchange for measurement access and a case study. |
| Two-track manufacturer talks | Quiet parallel conversations with a second panel maker (there are several credible ones in Europe) is standard practice and transforms the S3 negotiation. Exclusivity is something they buy, not something we assume. |
| Reverse-pitch the consultancy | Instead of asking the consultancy to join a venture, invite them to co-author the market white paper (doc 02 §06 demand-creation play). It monetises their independence rather than threatening it, and makes them the category's evangelist at zero equity cost. |