Pilot
What a successful 30-day pilot looks like
Our pilot is fixed-scope and fixed-price — $8,000 for 30 days. No open-ended “let’s see how it goes.” Below is the exact scorecard we agree on with you in week one, so there’s no ambiguity about what success means.
Connected in week one
ProductFlo reads your schematic, firmware repo, CAD, and BOM in place — no migration. Success means your product graph is indexed and agents are reading live data within the first 5 business days.
→ Time to first value < 1 hour from kickoff call
The merge gate catches real issues
Every firmware PR that touches a pin is cross-checked against the schematic; BOM changes are diffed against the ECAD source. Success means the gate flags at least one genuine mismatch your existing review process missed.
→ ≥ 1 caught mismatch in 30 days
ECO cycle time moves
We baseline your engineering change order cycle time in week one and measure again at day 30. Success is a directional, measured reduction — not a vibes-based claim.
→ Measured ECO cycle-time reduction vs. baseline
Engineers stay in their tools
No new tool to learn, no workflow replacement. Success means your engineers interact with ProductFlo through the GitHub PR bot and their existing CAD/ECAD plugins — not a new dashboard they have to remember to open.
→ Zero mandatory workflow changes
Humans approve everything
Agents propose diffs; they never commit. Every agent-proposed change carries a full audit trail: what changed, what the agent checked, and who approved it.
→ 100% of changes human-approved, fully auditable
If we don’t hit the scorecard, you don’t continue.
The pilot is designed to produce a go/no-go decision with evidence — not a sunk-cost slide into an annual contract.
Book a pilot scoping call →