Illustrative report structure
What an eight-week Paid Pilot should answer.
This example shows the evidence and decisions StowGauge would deliver for one Facility. It contains no customer data and makes no claim about past performance.
Scope record
Begin with the conditions that make the numbers interpretable.
- Evaluation window
- Eight weeks with start and end dates recorded
- Facility
- One agreed Facility and its configured Unit Catalog
- Placement
- The pages and rental destinations where the Decision Widget appeared
- Baseline
- The aggregate traffic, rental, or size-question counts the Operator can reliably provide
Pilot Funnel
Follow intent without building renter profiles.
Each stage is reported as an aggregate count for the Facility and evaluation window.
- 01
Widget views
The Decision Widget loaded on an approved page.
- 02
Planning starts
A Planner User first changed a planning input.
- 03
Recommendations
A Planner User reached a Recommendation from the configured Unit Catalog.
- 04
Rental handoffs
A Planner User intentionally continued into the Operator's existing rental path.
- 05
Rental outcomes
Operator-reported reservations or rentals associated with the agreed StowGauge source.
Evidence boundary
Separate observed activity from reported outcomes.
StowGauge observes
- Daily aggregate Pilot Funnel counts
- Configuration and installation checks
- Recommendation and handoff behavior at the Facility level
The Operator reports
- Rental Outcomes available in the existing system
- Size-related calls or staff observations
- Operational issues that changed the evaluation
Neither side should infer
- A Rental Outcome from a click alone
- An exact-fit guarantee from a Recommendation
- Performance beyond the agreed Facility and window
No renter names, emails, phone numbers, item lists, or raw sessions are included in the Pilot Report.
End-of-pilot decision
Finish with Continue, Revise, or Stop.
Start with the Facility