# Partner Model — Synthesis

Оптимизированный вывод по исследованию **DR-SV-29 — Partner Model**.

Дата интеграции: 2026-07-03  
Raw result: не сохранен в репозитории, исходный файл был передан пользователем как `deep-research-report (3).md`  
Статус: Integrated

---

## 1. Главный Вывод

Partner model для Specus Village — это не supplier list, а sequenced partnership stack.

Рабочая формула:

```text
control -> design -> delivery -> utilities -> operations -> legitimacy -> capital
```

По-русски:

```text
контроль участка -> проектирование -> доставка -> инфраструктура -> операции -> легитимность -> капитал
```

Главное правило:

```text
clarity of roles, phased commitments, and early coordination matter more than vision language
```

Specus должен просить серьезные commitments только после того, как может показать:

- planning proof;
- delivery proof;
- operating proof;
- resilience proof.

---

## 2. Sequenced Partnership Stack

### Tier A — Control And Permissions

Первый слой:

- land owners;
- municipalities;
- legal / tax advisers;
- architects / masterplanners.

Зачем:

- site control;
- planning route;
- legal vehicle;
- policy fit;
- first physical concept.

Без этого все остальные разговоры остаются speculative.

### Tier B — Design, Delivery And Core Infrastructure

Второй слой:

- modular manufacturers;
- local builders / installers;
- energy partners;
- water / wastewater partners;
- internet providers.

Зачем:

- costed delivery;
- factory / site interface;
- utility feasibility;
- O&M boundaries;
- realistic phase plan.

### Tier C — Operations, Activation And Legitimacy

Третий слой:

- hospitality operators;
- food / agriculture partners;
- emergency / shelter specialists;
- local community connectors.

Зачем:

- usable place;
- local value;
- resilience logic;
- operations credibility;
- public legitimacy.

### Tier D — Capital

Четвертый слой:

- investors;
- lenders;
- impact capital;
- project finance partners.

Зачем:

- capital should enter after site logic, technical partners and public-benefit alignment are credible.

Investor outreach before proof increases trust risk.

---

## 3. First Five Partner Offers

### 1. Village Land Uplift Partnership

Target: land owners.

Offer:

- conditional site control;
- phased takedowns;
- transparent value sharing;
- governance rights;
- stewardship logic.

Message:

```text
A staged route to land uplift and stewardship, without forcing a premature sale.
```

### 2. Municipal Benefit And Predictability Pack

Target: municipalities.

Offer:

- draft MOU;
- phased approvals;
- public benefits;
- infrastructure responsibilities;
- community engagement;
- local procurement logic.

Message:

```text
A predictable phased project that helps the municipality say yes with confidence.
```

### 3. Founding Modular Platform Agreement

Target: modular manufacturer + local builder / installer.

Offer:

- early design-assist;
- preferred-supplier framework;
- pipeline visibility;
- local installation package;
- interface matrix.

Message:

```text
Visible phase pipeline plus early design authority and a flagship reference project.
```

### 4. Operator-Lite Hospitality Term Sheet

Target: hospitality operators.

Offer:

- short initial term;
- owner approval rights;
- performance tests;
- white-label or third-party management;
- clear FF&E and service standards.

Message:

```text
A flexible experiential asset that suits third-party or white-label operation better than rigid phase-one branding.
```

### 5. Community Stewardship Charter

Target: community connectors + food / agriculture partners.

Offer:

- paid co-design participation;
- local sourcing commitments;
- programme opportunities;
- governance seats;
- visible local benefit commitments.

Message:

```text
A formal early role with paid influence and visible local benefit commitments.
```

---

## 4. Recommended Outreach Sequence

1. Legal / tax advisers + priority municipality + target land owner.
2. Architect / masterplanner.
3. Modular manufacturer + local builder / installer.
4. Energy + water / wastewater + internet partners.
5. Community connectors + food / agriculture partners.
6. Hospitality operator.
7. Investors.

Principle:

```text
who makes the next conversation easier?
```

Not all important partners should be contacted first. Investors are important, but stronger after partner LOIs, site logic and phase-one proof.

---

## 5. Partner Deck Logic

Partner deck должен быть modular:

- core deck for everyone;
- partner-specific appendix for each partner type.

Core deck sections:

- project thesis;
- site and place logic;
- village system architecture;
- phasing and critical path;
- demand and revenue model;
- delivery model;
- governance and contracts;
- resilience and compliance;
- public and community benefits;
- partner-specific appendix.

Каждый appendix должен отвечать:

- what role this partner plays;
- what Specus asks for now;
- what Specus is not asking yet;
- what risk is bounded;
- what upside exists;
- next step.

---

## 6. Objection Library

Повторяющиеся objections:

- project is too bespoke;
- schedule is not credible;
- modular financing is awkward;
- who owns interface risk;
- utilities and resilience are uncertain;
- hospitality operator will control the asset;
- community will oppose this;
- legal structure is too complicated;
- too early for investment;
- emergency readiness is nice to have, not commercial.

Specus response style:

- show pattern-book and product families;
- split timeline into entitlement / infrastructure / manufacturing / install;
- show interface matrix;
- treat utilities as anchor partnerships;
- use operator-lite term sheet;
- move from consultation to co-creation;
- keep phase one legally lean;
- raise capital against stage-gated proof;
- show readiness as asset protection and municipal confidence.

---

## 7. Proof Stack

Before asking for serious commitments, Specus should assemble:

### Planning Proof

- site control path;
- policy fit;
- municipal route;
- community support;
- public benefit case.

### Delivery Proof

- phase plan;
- modular / site interface matrix;
- local install capability;
- transport assumptions;
- code path.

### Operating Proof

- service standards;
- hospitality scope;
- owner approval rights;
- maintenance process;
- governance model.

### Resilience Proof

- energy logic;
- water / wastewater logic;
- internet logic;
- emergency readiness;
- O&M responsibilities.

---

## 8. Решения Для Specus Village

1. Treat Specus as value-adding orchestrator, not just seller or developer.
2. Start with land / municipality / legal / masterplanning, not investors.
3. Build partner commitments in phases.
4. Create a responsibility / interface matrix before delivery promises.
5. Use municipal and community legitimacy as bankability layer.
6. Treat utilities as anchor partnerships, not commodity procurement.
7. Approach investors after site logic, technical feasibility and partner proof.
8. Build modular partner deck with appendices by partner type.
9. Use first five partner offers as outreach packages.
10. Create objection-handling library before partner calls.

---

## 9. Статус Следующего Research

После этого синтеза DR-SV-30 был выполнен и интегрирован:

```text
DR-SV-30 — Village Operating Model — Integrated
```

См.:

- `2026-07-03_Village_Operating_Model_Synthesis.md`
- `04_OPERATIONS/Village_Operating_Model.md`

Следующий рекомендуемый запуск:

```text
DR-SV-31 — Location Selection Framework
```