The work continues beyond the hackathon
The pilot is next.
Regardless of the hackathon result, we are moving TryOnReady toward a measured boutique pilot—carefully, transparently, and with real operators.
The demonstration proved a controlled journey can be assembled. The pilot will test whether independent boutiques can operate it reliably, whether shoppers understand it, and whether the economics and privacy controls hold up before expansion.
A disciplined path forward
Prepare. Run. Measure. Decide.
The plan starts deliberately small so reliability, effort, cost, and privacy can be examined before the catalog or cohort grows.
- 01
Weeks 0–2
Prepare and baseline
Enroll qualified boutiques, assist the first garment, verify rights and readiness, and establish honest operating baselines before setting improvement targets.
- 02
Weeks 3–8
Run and learn
Operate controlled guest journeys, review reliability and provider units weekly, and listen closely to owners, staff, and shoppers.
- 03
Weeks 9–12
Decide with evidence
Compare the cohort against its baseline, document gaps, and make a human go, revise, or stop decision before expanding.
Evidence before scale
We will measure the operating truth.
Starting thresholds will be refined after the two-week baseline. Conversion improvement, return reduction, and willingness to pay remain hypotheses until the pilot produces credible evidence.
- Activation
- Time and support required to reach the first approved garment.
- Reliability
- Completion and latency for valid provider-accepted live jobs.
- Operator effort
- Admin decision time and the learning curve after garment one.
- Usage control
- Units per success and duplicate requests prevented.
- Shopper clarity
- Consent, upload, submit, result, and explicit interest actions.
- Commercial signal
- Repeat retailer use and willingness to continue or pay.
Non-negotiable from day one
Growth never outranks the safeguards.
Privacy, secret handling, duplicate prevention, and deletion compliance are hard gates—not metrics we average away. Provider retention and deletion are measured separately; local deletion never proves provider deletion.
- No provider credential or secret reaches the browser.
- Retailers and administrators cannot access shopper photographs.
- An unchanged duplicate never creates a second provider task.
- Every eligible local source and result meets its deletion deadline.
- Appearance visualization is never presented as physical fit or sizing.
Every week
Operate visibly. Learn honestly.
Reliability reviewOutcomes, latency, failures, and retry behavior.
Privacy auditAccess boundaries, deletion deadlines, and incident review.
Retailer feedbackSetup effort, staff confidence, and repeat use.
Metric reviewUnits per success, duplicates stopped, and shopper completion.
Our commitment
We are serious about earning the next step.
A prize would accelerate the work. It does not determine whether the work continues. We will use the evidence to improve, expand, or stop responsibly—and we will be honest about what the pilot proves.