Controlled pilot packages
ShipWright is packaged for controlled pilots, managed early deployments, and proof-backed walkthroughs. Pilot pricing is discussed after fit review and structured around scope, order volume, and operational support needs.
Controlled Pilot
Operator / Platform Pilot
Investor / Partner Demo
ShipWright does not publish generic self-serve pricing yet because the pilot shape depends on operating scope, courier coverage, order volume, payment posture, and support ownership.
Readiness standard
Controlled pilots include release readiness, validation evidence, finance visibility, dispatch and support audit posture, and fleet-ready operational context where relevant.
Release readiness and validation evidence show whether release verification, paid proof, and required-auth smoke are current.
Support closeout, dispatch override history, menu rollback, and enterprise access events remain audit-visible.
Finance surfaces show captured, pending, failed, and refund-review posture without automated refunds or payout automation.
Fleet workspace and driver readiness are available for managed courier groups without scoring or automatic suspension.
Pilot questions
ShipWright is ready for controlled pilots, demos, and managed early deployments. Open, unattended real-world operation still requires live operating ownership and agreed guardrails.
Restaurants and retailers can use the controlled pilot path to review menu setup, paid ordering, dispatch workflow, tracking, and support handling before a live operating window.
No. Command Intelligence is deterministic and human-in-the-loop. Operators approve refunds, cancellations, dispatch recovery, customer messages, and incident closeout.
Yes, with boundaries. ShipWright includes courier readiness, driver execution, admin fleet foundations, and a dedicated fleet-manager workspace. Fleet billing and payout automation are not part of v1.
ShipWright supports payment authorization, capture proof, and payment-risk visibility. Full settlement and payout automation remain deferred.
After a pilot fit review, the team defines operating scope, validation gates, support ownership, known limitations, and the next controlled rehearsal or deployment window.
Start with fit
Choose the pilot path that matches your role. The request is persisted for platform-admin review; email, CRM, and automated follow-up remain intentionally deferred.