Doingly: our own services marketplace, web and mobile

We wanted to build our own product, not just ship for clients, and prove the thesis we sell: analysis first, then a production-grade build. The idea was simple to say and hard to build, a marketplace where anyone can list a skill they are good at, from cleaning to coding, and get paid for it.

Two-sided marketplaces are notoriously hard. You need supply and demand at once, real-time messaging, trust and verification, payments, and both a fast web app and a native mobile app, all shipped by a small team on a tight timeline.

We treated our own product exactly like a client engagement: analysis first, then execution. We designed one backend to serve both a Next.js web app and a Flutter Android app, with real-time messaging over Socket.IO, JWT and Google sign-in, and AI-assisted skill verification (Google Gemini) so listings could be trusted.

We built for trust and safety from day one, identity verification, rate limiting and IP blocking, secure media handling, and Razorpay payments, so people felt safe transacting.

We built Doingly end to end, ourselves:

• Web app (Next.js 16, React 19) with real-time chat, maps, and a PWA install experience.
• Native Android app (Flutter) on the Play Store, sharing the same backend.
• An Express + Prisma backend on serverless PostgreSQL (Neon), with Socket.IO real-time, Google Gemini for AI skill-verification tests, and Firebase push notifications.
• Trust and payments done properly: identity verification, Cloudinary media, Helmet + rate limiting + IP blocking, and Razorpay checkout.

Shipped, monitored (UptimeRobot, Vercel Analytics), and iterated as a real product, not a prototype.

In its first months, Doingly reached 7,000+ visitors, 2,000+ signups, and 300+ services listed, a live, two-sided marketplace with real supply and demand, built in 4 months.

It is our own proof that we build what we advise: analysis first, then a production-grade product across web and mobile.