Trajectory · product leadership
Where Phase 1 stands.
The number that survives scrutiny, the customer-facing capabilities proven by tests, and an honest read of what's still in flight — every figure derived live from the project's own test results, not asserted.
The number to lead with
93%of the product is test-verified
202 of 218 acceptance criteria pass an automated scenario that exercises the real handler and data path and asserts the behavior — not "the code exists," but "the behavior is verified by a test." None of the verified scenarios are currently failing. It's the figure a skeptical engineer can re-run.
18 of 28 feature areas are fully verified— every acceptance criterion in them passes. The other 10 are the near-term runway.
Verified by tests
Customer-facing capabilities where every acceptance criterion passes an automated scenario — the durable proof, tied to the code and re-runnable on demand.
Subscribe & save
Test-verified
Gift, prepaid & build-a-box
Test-verified
Free trial, intro offers & annual billing
Test-verified
What's still in flight — named before the reviewer asks
- 10 feature areas are partially verified — the active Phase-1 runway (#8 (2/6), #17 (4/5), #18 (10/11), #20 (6/7), #22 (8/9), #23 (17/18), #24 (10/11), #25 (9/11), #27 (6/7), #28 (4/7)).
- 16 acceptance criteria are not yet at the verified bar (no scenario gate, or a scenario not yet passing).
- 3 capabilities are waiting on BigCommerce's own platform, not on us — the native payment rail depends on a BigCommerce capability still gated on their side. We do not claim the payment rail is live; everything above runs independent of it.
GA target
Not yet committed. The remaining work is scoped as a list of items, not a locked calendar date, and there is no ship-date commitment to cite. If a date is needed for planning, that's a decision to make deliberately — not a number to read off this page.
Footnote for the technical reviewer — do not lead with this
Engineering dashboards also track a "capabilities present" figure —591 of 683 (87% across all phases). That measures whether a code artifact exists (a file, a column, a function), not whether it works end-to-end. It's a build-progress signal, useful internally, but it is not a completion number and should never be presented as one. The 93% test-verified figure at the top is the honest completion signal.