---
title: "Hardware Partner Workbook"
canonical_url: "https://flowfuse.com/handbook/sales/partnerships/hardware-partners/workbook/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

## Hardware Partner Workbook

The **Hardware Partner Workbook** is the single document that runs a
[hardware partnership](https://flowfuse.com/handbook/sales/partnerships/hardware-partners/) — copy the
[FlowFuse Hardware Partner Workbook template](https://docs.google.com/spreadsheets/d/1c2UXyzkADJCwOjG9Rrz8B01watDYBkg7eKa2BYhxcdI/edit)
per partner. It is a first-class asset of the engagement, alongside the
[Partner Stages](https://docs.google.com/spreadsheets/d/1X3Z9kX4_42Gx5WMzHVnhij61xJGXyOCopnUNFsmqf8s/edit).
Like the PoV workbook, it is the through-line across the whole partnership: each
[stage](https://flowfuse.com/handbook/sales/partnerships/hardware-partners/#the-partnership-process) produces or executes a portion of it.
Completed workbooks live in the partner
[Drive folder](https://drive.google.com/drive/folders/1GUEMDoDmX9hrgsxFVJ-PcyrILHgSm4km)
and are shared *with the partner*.

## How the stages feed the workbook

<table>
<thead>
  <tr>
    <th>
      Stage
    </th>
    
    <th>
      Portion of the workbook
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Qualify & Fit
      </strong>
    </td>
    
    <td>
      <strong>
        Overview
      </strong>
      
       (partner, team, economic buyer) + <strong>
        Fit & Use Case
      </strong>
      
       (thesis, value exchange, forcing function, success criteria)
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Feasibility & Certification
      </strong>
      
       <em>
        (the gate)
      </em>
    </td>
    
    <td>
      <strong>
        Certification
      </strong>
      
       — device + reference architecture, the access-provisioned gate, integrator roles, cert checklist, blockers
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Joint Offer & Commercial
      </strong>
    </td>
    
    <td>
      <strong>
        Overview → Joint Offer + Commercial Model
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Legal
      </strong>
    </td>
    
    <td>
      Overview commercial / legal status
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        GTM Launch
      </strong>
    </td>
    
    <td>
      <strong>
        Plan → post-launch
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      <em>
        Throughout
      </em>
    </td>
    
    <td>
      <strong>
        Plan
      </strong>
      
       (gates + schedule), <strong>
        Timeline
      </strong>
      
       (execution Gantt), <strong>
        Questions
      </strong>
    </td>
  </tr>
</tbody>
</table>

## The tabs

<table>
<thead>
  <tr>
    <th>
      Tab
    </th>
    
    <th>
      What it's for
    </th>
    
    <th>
      Why it matters
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Overview
      </strong>
    </td>
    
    <td>
      The partner, the team (Partner Lead · Solutions Engineer · Marketing · Technical Contact, mirrored FlowFuse ↔ partner), the joint offer + commercial model, and key links.
    </td>
    
    <td>
      One place for who's involved and what the deal looks like.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Fit & Use Case
      </strong>
    </td>
    
    <td>
      The "better together" thesis, the value exchange, the <strong>
        forcing function
      </strong>
      
      , and partnership success criteria.
    </td>
    
    <td>
      Anchors the partnership to real value and a named customer — not just a cool integration.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Certification
      </strong>
    </td>
    
    <td>
      The device + reference architecture, the <strong>
        access-provisioned gate
      </strong>
      
      , integrator roles, the cert checklist, and known blockers.
    </td>
    
    <td>
      The technical gate — the roadblock that sinks partnerships when it's skipped.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Plan
      </strong>
    </td>
    
    <td>
      Pre-partnership gates, the stage schedule, and post-launch.
    </td>
    
    <td>
      Turns "let's try it" into gated, owned, dated work.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Timeline
      </strong>
    </td>
    
    <td>
      An execution Gantt that begins at <strong>
        technical confirmed
      </strong>
      
      .
    </td>
    
    <td>
      You can't schedule a partnership until the technical is proven.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Questions
      </strong>
    </td>
    
    <td>
      Async Q&A — technical / commercial / legal.
    </td>
    
    <td>
      Keeps blockers visible instead of buried in email threads.
    </td>
  </tr>
</tbody>
</table>

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
