Custom marketplace — web and native app MVP

A marketplace operator was preparing a two-sided launch and needed real product to stand it up—discovery, booking requests, and payments—rather than a patchwork of manual tools.

Launch operations were running on spreadsheets, DMs, and manual invoicing. The operator was stuck stitching those pieces together by hand instead of running a product.

Without a shared product surface, the core flows of a two-sided marketplace—onboarding, discovery, booking, and getting paid—had no system to run on, leaving every transaction dependent on manual coordination.

The launch needed one integrated web and mobile surface, not a list of disconnected features. The work was to scope a real MVP and draw explicit boundaries around anything outside it, so the build stayed shippable.

OpsPal scoped and delivered a fixed-fee MVP: a web app plus a native iPhone app sharing the same backend. Authentication, profile approval workflows, browse and search, request-to-book with operator visibility, and a payment flow on the client's Stripe account run together, with basic admin metrics and a staging environment. Platforms and features outside the agreed MVP are handled through explicit change-order boundaries.

Handoff included a staging environment for releases and a release-candidate handoff so the operator could take the product to launch.

The result is one integrated web and mobile surface for launch operations—discovery, booking requests, and payments running as a product instead of spreadsheets, DMs, and manual invoicing.

This was a fixed-fee MVP with clear change-order boundaries, so anything beyond the agreed scope—additional platforms or features—is a defined next build rather than scope creep.