Sales handbook: Partnerships — hardware vs channel partners - #5618
Open
dgatti0213 wants to merge 1 commit into
Open
Sales handbook: Partnerships — hardware vs channel partners#5618dgatti0213 wants to merge 1 commit into
dgatti0213 wants to merge 1 commit into
Conversation
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
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). |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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.
The old single
partnerships.mdbecomes the folder; inbound links in the Commercial Org index are updated, and.navigation.ymlsets 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.