Skip to content
← All work
2026–PresentCofounder & Full-Stack Engineer

ProntoMigo

Delivery marketplace that unifies food, grocery, and retail orders, bulky-goods van transport, and pre-booked passenger transfers, with upfront pricing and live tracking.

Visit live site

What it covers

MarketplaceLogisticsFood DeliveryLive TrackingPayments & PayoutsRoute OptimizationDemand ForecastingiOSAndroid

Tech stack

React NativeNode.jsStripe ConnectLive trackingPostgreSQL

The challenge

Local delivery, bulky transport, and passenger transfers lived in separate apps with opaque pricing. Unifying them meant one pricing and payments model had to serve instant delivery, scheduled vans, and pre-booked transfers without forking the product.

Collaboration

I cofounded ProntoMigo with a partner based in Italy, where the service launched. Together we met local businesses and drivers in the neighbourhood, found room to add services, and chose delivery as the first vertical: the customer orders, a driver picks up from the shop, and the order is delivered. I built the consumer app, the driver app, the backend, and the shared pricing and payments core, and took that first service from those conversations to a working marketplace.

From discovery to production

  • Delivery as the first live vertical: order, shop pickup, and drop-off
  • Separate consumer and driver apps from one React Native codebase
  • Upfront pricing across food, grocery, retail, and transport
  • Live order and driver tracking
  • Marketplace payouts through Stripe Connect
  • A shared pricing and payments core so van transport and passenger transfers do not require a second product

How it was solved

Consumer and driver are two apps from one React Native codebase. Pricing is shared, so food delivery, scheduled van transport, and pre-booked transfers do not each grow their own checkout. Stripe Connect settles the marketplace from day one. PostgreSQL stores orders, and live tracking follows the driver after pickup.

Key technical decisions

  • 01One pricing and payments core for every service category, instead of a forked product per vertical.
  • 02Consumer and driver as separate apps from one React Native codebase.
  • 03Stripe Connect for multi-party payouts from the first order, not a later payments rewrite.
  • 04Delivery first, because that was the workflow local shops and drivers already had.

Screenshots

ProntoMigo screenshot 1

Impact

  • Delivery launched from neighbourhood conversations with businesses and drivers, not from a guessed feature list.
  • Customers see the price before they order, across food, grocery, retail, and transport.
  • Drivers and orders are tracked live, and Stripe Connect splits the payout.
  • Later verticals reuse the same pricing and payments core instead of becoming separate apps.

What I learned

A shared pricing and payments core lets one marketplace serve very different jobs without forking the product.

Want an outcome like this?