Skip to content

Sales handbook: Partnerships — hardware vs channel partners - #5618

Open
dgatti0213 wants to merge 1 commit into
mainfrom
handbook/partnerships
Open

Sales handbook: Partnerships — hardware vs channel partners#5618
dgatti0213 wants to merge 1 commit into
mainfrom
handbook/partnerships

Conversation

@dgatti0213

@dgatti0213 dgatti0213 commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

What this does

Reworks the Partnerships section of the Commercial Organization handbook into a folder that separates the two partner motions and documents the hardware partnership process end to end.

  • Partnerships (overview) — intro + a Partner-types table routing to each motion.
  • Hardware Partners — the technical, gated motion: five stages (each with intent/goal + the workbook portion it produces), the "prove the technical first" gate, good/bad lessons, and device certification.
  • Channel Partners — the commercial motion: reseller agreement + deal registration, system integrators, referral partner fees (existing content preserved and regrouped).
  • Partner Workbook — first-class asset: how the stages feed the workbook, the tab breakdown, and the template link.

The old single partnerships.md becomes the folder; inbound links in the Commercial Org index are updated, and .navigation.yml sets the section order + handshake icon.

Derived from the HMS / IFM / Victron partnership calls, with the "prove the technical first" gate as the core principle.

Review

@MichaelBDavis — flagging you for review before merge to main.

Rework the Partnerships section (Commercial Organization) into a folder
that distinguishes the two partner motions and documents the hardware
partnership process end-to-end.

- Partnerships (overview) — intro + a Partner-types table routing to each
- Hardware Partners — the technical, gated motion: five stages (each with
  intent/goal + the workbook portion it produces), "prove the technical
  first" gate, good/bad lessons, and device certification
- Channel Partners — the commercial motion: reseller agreement + deal
  registration, system integrators, referral partner fees (existing
  content, preserved and regrouped)
- Partner Workbook — first-class asset: how the stages feed the workbook,
  the tab breakdown, and the template link

Links the Partner Stages doc (entrance/exit criteria) and the Partner
Workbook template. Old single partnerships.md becomes the folder; inbound
links in the Commercial Org index updated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CVTs4TWBz2sVJ3k55ZHUg8
@dgatti0213

Copy link
Copy Markdown
Contributor Author

Deploy preview (once the Netlify check finishes): https://deploy-preview-5618--flowforge-website.netlify.app/handbook/sales/partnerships/

Start on the Partnerships overview, then Hardware Partners (the staged/gated process) and Channel Partners (reseller / SI / referral).

@dgatti0213 dgatti0213 self-assigned this Aug 17, 2026
@netlify

netlify Bot commented Aug 17, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit fb1aa13
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a830a94627faf000822a334
😎 Deploy Preview https://deploy-preview-5618--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 65 (🟢 up 17 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 85 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant