Payload
v1 · Product Development OS

From requirement to the unit on your bench.

Payload ties every requirement to the exact component, file version, prototype, test and decision behind it. So when something breaks in the field, you can walk the trail back in one click — not one week.

Free forever · No credit card

byte · v1.0
used by hardware teams inosloberlinshenzhentaipeibrooklyn
Problem

Three places where the truth about your product gets lost.

01 · Which unit is this, really?
Inbox — 47 replies
  • RE: RE: FWD: final_v7_REAL.step
    Anna (Marketing)
    v7?
  • RE: bracket tolerance — is it 0.2 or 0.5?
    Jonas (Eng.)
    conflict
  • please confirm color pantone 7546 C
    Factory (SZ)
    waiting
  • CE declaration missing signature
    Legal
    blocker
  • RE: FWD: press kit images — which revision?
    Anna (Marketing)
    ?
  • final_v8_REAL_FINAL.step
    Jonas (Eng.)
    new
  • Can everyone reply on Tuesday's thread?
    Sofia (PM)
    47 replies

Prototype #7 is on the bench, failing at 40°C. Which firmware? Which hinge revision? Which BOM? The label doesn't say — and neither does anyone's memory.

02 · Test results with nowhere to go
FRONTrev A
SIDErev C
ISOrev B
TOPrev A?

The lab emails back a PDF. It lands in a Slack channel. Nobody links it to the requirement it was meant to prove, or to the decision it should have unblocked.

03 · Suppliers see everything or nothing
Compliance matrix
  • EUCE / RoHS / REACH?
  • USFCC Part 15 / UL?
  • UKUKCALegal
  • JPPSE / Giteki?
  • CNCCCFactory
  • NO/SEEMC declaration?

You want the CNC shop to see one housing revision — not your BOM, roadmap and pricing. Today that means zipping files by hand and hoping nothing leaks.

Roles

Four roles. One trail. Every claim backed by evidence.

Persona 01

Developer

"I need to know which firmware, which PCB rev and which mechanical version are actually inside prototype #7."

  • Every prototype snapshots its exact component + file versions
  • BOM diff between any two revisions in plain text
  • Datasheet, changelog and open findings on every part
// prototype #7 · snapshot
- ESP32-WROOM-32E · Qty 1
+ ESP32-S3-WROOM-1 · Qty 1
- LiPo 800mAh
+ LiPo 1200mAh · hinge frozen at v2.7
! 1 open critical finding on this build
Persona 02

Designer

"I want a comment on the geometry to trigger a change — not vanish into a thread."

  • Upload STEP/GLB once — approved versions become the source of truth
  • Pin comments on the model, routed to the part's owner
  • Share a single link — always the latest approved revision
FRONTrev A
SIDErev C
ISOrev B
TOPrev A?
Persona 03

Founder

"I need to know which stage gate we're stuck on and exactly what's blocking it."

  • Stage gates with auto-checked criteria (open criticals, unverified reqs, BOM state)
  • Signed decisions logged against the gate, prototype or file version
  • One dashboard: requirements verified, prototypes built, tests passed
Stage gate status
  • Conceptpassed
  • DFM reviewawaiting sign-off
  • Validation2 criteria open
  • Design freezeblocked · critical finding
Persona 04

Product Manager

"I need external testers and suppliers to contribute — without inviting them into the whole project."

  • Public test portal: send a link, testers file structured findings, no login
  • Share packages: bundle exactly the file versions a supplier may see
  • Every finding, invite and download is logged and revocable
Compliance matrix
  • EUCE / RoHS / REACH?
  • USFCC Part 15 / UL?
  • UKUKCALegal
  • JPPSE / Giteki?
  • CNCCCFactory
  • NO/SEEMC declaration?
Platform

Six primitives. One traceable trail.

housing.step v3 · current
housing.step v2
housing.step v1

Requirements & components

Every requirement links to the components and file versions that satisfy it. Verify, don't guess.

@jonas
prototype #7 · built 12 Mar · hinge v2.7 · fw v1.4.2
pin · x 42 y 18 z 6

Prototype registry

QR-tag every physical unit. Scan to see its exact component + file version snapshot.

Round 04 · durability · 12 findings
Round 03 · functional · closed
Round 05 · field · portal open

Structured testing

Test rounds, findings by severity, and a public portal so external testers can submit without an account.

SKU · qty · lead
ESP32-S3 · 1 · 6w
LiPo 1200mAh · 1 · 3w
PCB v0.4 · 1 · 4w

Stage gates & decisions

Gates with auto-evaluated criteria. Passing writes a signed entry to the decision log.

Traceability

One requirement. Six links. One source of truth.

Every node in Payload — requirement, component, file version, prototype, test finding, decision — knows what it's connected to. Follow the trail in either direction.

NO
Requirement → component that satisfies it
SE
Component → the exact file version approved
DE
File version → prototypes built from it
US
Prototype → tests it went through
JP
Finding → decision that resolved it
CN
Decision → gate it unblocked
Field notes

Teams that stopped asking "which CAD is current?"

Three hardware teams. Three ways Payload's version trail cut the CAD confusion tax.

Case 01
Northwind Acoustics
Consumer audio · 14 engineers
-92%
wrong-version prototypes
We used to build one prototype a month from the wrong STEP file. Payload's linked file versions and stage-gate lock killed it — every prototype now cites the exact revision it came from.
Ida Solheim · Head of Mechanical
Ready to write your own field note?

Start your first project free, or see Payload on your own CAD in a 20-minute demo.

"A field unit failed. In 30 seconds we had its exact BOM, the two open findings against it, and the decision that shipped it anyway. That used to be a two-day archaeology dig."
Head of Hardware · consumer robotics startup, Oslo

Stop doing archaeology on your own product.

Your first project is free. Bring the whole team — including external testers, suppliers and the factory.

Free forever · No credit card · Cancel anytime