1
Merchant setup
A real restaurant and menu foundation exists for the pilot merchant.
Shows that the pilot merchant can be activated and made orderable without admin theatre.
ShipWright
Investor demo mode
Show the proven Stage 1 loop as one connected operating product.
This route is the guided control panel for merchant activation, public ordering, paid delivery execution, notifications, and platform oversight. It points at real screens and documented staging proof rather than demo-only logic.
Demo narrative
What each screen proves
2
Public restaurant order
Customers can browse a real active menu, build a cart, and enter checkout details.
Proves the Stage 1 spine starts from a customer-facing route, not an internal-only backend.
3
Payment authorised
Paid checkout creates a customer order, payment, and linked delivery job.
Shows order, payment, and fulfilment entering operations as one connected flow.
4
Dispatch and Needs Review
Blocked or delayed jobs surface in the operator review queue with diagnosis and next action.
Demonstrates that operations are guided by decision surfaces, not raw logs.
5
Driver assignment and execution
A staged driver can go online, receive offers, accept, and progress delivery steps.
Shows the execution layer is connected to the paid order loop.
6
POD and delivery completion
Proof of delivery is recorded before final completion and downstream state updates.
Shows the delivery loop closes with evidence, not just status toggles.
7
Payment captured and order fulfilled
Delivered jobs trigger payment capture and the customer order moves to FULFILLED.
Proves commercial completion, not just dispatch success.
8
Notifications and admin oversight
Operators and platform admins can inspect system signals, outbox pressure, and intervention queues.
Shows the product has control-plane depth for pilot support and investor review.
Control panel
Fast screen access
Public restaurant route
Customer browse, cart, and checkout path.
Orders queueCustomer order -> payment -> delivery linkage.
Jobs consoleDispatch, review queue, and job decision surfaces.
Driver executionOffer accept, pickup, POD, and delivery completion.
Platform adminCross-org intervention queue, health posture, and outbox signals.
NotificationsIn-app operational notifications and event mapping.
Latest documented proof
Staging paid-delivery summary
No static proof summary loaded
Add a documented proof artifact before claiming a fresh staging pass in the investor demo.
Demo guardrails
What to say and what not to fake
- Business, driver, and admin views require seeded staging credentials. The public restaurant route does not.
- The proof summary is the latest documented staging result, not a live monitoring feed.
- If Stripe, email, or domain configuration is unavailable, use the documented fallback sequence instead of improvising on stage.
Full talk track: /Users/olubusayoadewale/Coding Projects/shipwright/docs/demo/investor-demo-script.md