Four roles, four products, one delivery platform — built for Kuwait.

You start with how the market actually pays. Kuwait runs on KNET, the national debit network, and on MyFatoorah as the aggregator most local merchants already use — a platform that only accepts international cards will not convert there regardless of how good the app is. The same principle extends to hosting in-region for latency and data residency, and to Arabic support that's built in rather than translated on. Connect was built against local rails from the first sprint, not retrofitted after launch.

Through a KYC flow that ends at a human, not an algorithm. On Connect, vendors and drivers submit documents during onboarding, applications land in a review queue in the admin dashboard, and the client's own team approves, rejects or suspends them. The important design decision is that it belongs to the operator: a platform where onboarding a restaurant requires a developer will not scale past its first fifty vendors.

More than an app, because it isn't one. Connect needed a customer app, a driver app, a vendor dashboard and an admin dashboard, each with different screens, permissions and release cycles. We scope platforms in phases and quote each phase fixed-price after a free scoping call, so you can launch one role at a time rather than funding all four before seeing anything work.

Yes, and that's the test of whether it's a platform or a project. Commissions, pricing rules, membership tiers, coupons and promotions are all configuration in Connect's admin dashboard. If a business can't change its own take rate without a deployment, it doesn't control its own economics.

Driver position and order state push over websockets to the customer's map and the vendor's queue, rather than each client polling for updates. That keeps everyone looking at the same order status at the same moment, and it costs far less battery and bandwidth than repeated requests — which matters on a driver's device across a full shift.

Yes. Connect shipped four store listings — two apps across two platforms — each with its own metadata, screenshots, review notes and privacy declarations. Multi-app submissions are their own workstream: a rejection on the driver app shouldn't hold up the customer app, and the two need genuinely different compliance answers because they collect different data.