Public document

Partnership Proposal

partnership-proposal.md

Partnership Proposal

Watch the HyperFrames video

Status: evolving working proposal
Last updated: 2026-08-06

Purpose

This document is the shared partnership proposal model for Ed's industry-specific AI + iOS + SaaS partnerships. It is the common starting point that each partner-specific proposal builds on.

Partnership idea

We pair Ed's product-building, AI, iOS, SaaS, and automation execution with a partner's domain expertise, customer understanding, workflow knowledge, and market access.

The goal is to co-create a focused product for one industry or partner niche, validate it with real users, and grow it into a recurring-revenue vertical that can stand alone or become part of a broader portfolio. The partner represents their industry: they help shape the product, validate it with peers, and become the initial trusted channel for introducing the platform within that market.

Default partnership structure

What Ed brings

What the partner brings

Industry-author opportunity

The default long-term authority target is for each approved partner to become the named author of a practical book for their industry, provided the topic, partner interest, and market evidence support the project. The book can serve as an authority and trust asset—not merely a royalty experiment—by packaging the partner's real expertise into useful guidance for peers and prospective customers.

Ed and Sage can provide research, interviews, drafting, editing, production, and cover support. The partner must materially contribute and approve the complete manuscript, claims, author biography, cover, and publication. We will not publish generic AI output under a partner's name, invent experience, or promise Amazon sales.

The operating workflow is defined in the Industry Partner Author and Amazon Book Strategy, including the seven source prompts, stronger production prompts, market validation, rights and quality gates, KDP AI disclosure, and per-project commercial decisions.

Early validation approach

  1. Identify painful recurring workflows.
  2. Research market problems, industry dynamics, and existing tools.
  3. Pick a low-risk MVP wedge.
  4. Build a narrow prototype or concierge-style workflow.
  5. Test with real users and partner feedback.
  6. Onboard the first customers into a recurring monthly subscription workflow.
  7. Identify whether any customer should become a sub-partner because they can help expand the vertical.
  8. Convert learning into a SaaS/iOS roadmap aimed at building an industry vertical with meaningful annual recurring revenue.
  9. Where approved and strategically useful, develop a partner-authored industry book that strengthens authority, education, peer access, and consent-based demand generation.

Product principles

Commercial growth path

  1. Co-design the product with the primary partner as the industry representative.
  2. Validate the MVP with peers in that industry.
  3. Convert early users into recurring monthly subscribers.
  4. Promote select high-value customers into sub-partner roles only when they materially help distribution, credibility, or customer success.
  5. Grow the vertical toward at least $1,000,000 in annual recurring revenue.
  6. Once the vertical is mature enough, evaluate strategic sale options and split sale proceeds according to the agreed partner/sub-partner economics.

Open questions to resolve per partner

Partner-specific proposals

Each partner profile should include its own top-level partnership-proposal.md that references this shared model and adds the partner's industry-specific perspective, opportunity framing, risks, and next steps.

Change log

Source: Manually maintained by Sage with direction from Ed; updated 2026-08-06.