A marketplace where strangers trust each other with their homes and their money

What was the problem?

Helpora came to Softivum with a brand, a market and a clear vision, and no product. A task marketplace is not one problem but three, each able to sink the product alone: trust between strangers when nobody has a reputation yet, money moving between two private individuals with the platform as guarantor, and a live event moving through the real world that both parties must see identically. All of it had to work for the Indian market specifically — phone-number identity, UPI, Aadhaar, and the everyday realities of connectivity and device quality — and be ready for an app-store launch on a schedule.

What made it hard

What we built

Four products were delivered: an installable consumer application with map discovery, escrow payment, chat, live tracking and door-code completion; the marketplace engine underneath it; an operations command centre where a non-technical team reviews verifications, oversees every movement of money, processes withdrawals, resolves disputes and tunes the marketplace economics; and the brand website with the full legal and compliance layer a regulated Indian marketplace must publish. A tested API package, integration guide and formal contracts for sensitive flows were delivered to the specialist mobile team in advance.

What it does

• Map-based task discovery

  Tasks nearby shown on a live map, with true distance-based search and an operations-controlled radius.

• Guided task creation

  Categories, photos, urgency and scheduling, plus recurring tasks that regenerate automatically.

• Escrow-protected payment

  Funds collected when the task is posted, held during the work, released only on genuine completion.

• Government-source identity verification

  Aadhaar via DigiLocker, plus bank, UPI, profile and face verification, with tiered eligibility.

• Live helper tracking

  Realtime tracking of the helper en route, with routing and live ETA, visible only to the two people involved.

• One-to-one chat

  Direct messaging with image sharing, typing indicators, read receipts and online presence.

• Arrival verification by one-time code

  A code confirmed at the door, plus photo evidence of completion.

• Earnings wallet and withdrawals

  A complete transaction ledger with payouts to bank account or UPI.

• Dispute resolution

  Handled with full conversation context, with refund and release paths.

• Runtime-configurable economics

  Commission, urgency pricing, referral rewards, escrow windows and search radius, all adjustable from the console.

• Trust scores, badges and two-way reviews

  Reputation accrues once the marketplace has history.

• Reporting, blocking and moderation

  Content and conduct moderation with an administrative audit trail.

• Push notifications at every stage

  Both sides are told the moment anything changes, whether the app is open or not.

• Saved addresses and autocomplete

  Address search and autocomplete with saved addresses.

• Data export and deletion

  Automated purging of personal and biometric data on account deletion, and data export on request.

Engineering decisions

Choices that could have gone another way, and what each one bought.

1. 1

   The payment gateway is a replaceable part

   Two fully working gateways sit behind a single internal contract. Payments already in flight continue to settle correctly with the provider that began them.

   Why it matters. Payment providers change their pricing, their approval outcomes and their reliability. Switching becomes a business decision rather than a development project, and Helpora is never tied to one vendor's terms.

2. 2

   Identity verified without ever being held

   Aadhaar verification runs through DigiLocker, the government's own consent mechanism. The user never types an Aadhaar number and Helpora never stores one — the platform receives a verification verdict and the last four digits.

   Why it matters. Enough to prove a person is real, and nothing left worth stealing. The liability of holding India's most sensitive identity data simply never arrives.

3. 3

   Provider downtime means 'not yet', never 'rejected'

   Identity providers go down, payment notifications get lost, phones lose signal mid-verification. Each is handled as a deferred outcome rather than a failed one, and payment confirmations are re-read from the gateway rather than trusted from the browser.

   Why it matters. A genuine user is never locked out of earning because someone else's service had a bad afternoon, and a lost callback never silently loses a payment.

4. 4

   One platform, not three

   The web app, the operations console and the native apps all draw on the same marketplace engine and inherit the same rules — one definition of who may cancel a task, when escrow releases and who may read a conversation.

   Why it matters. Rules cannot drift between surfaces, features arrive everywhere at once, and a third-party mobile team cannot accidentally implement a different marketplace.

5. 5

   The business controls the business

   Commission, urgency pricing, referral rewards, escrow windows and search radius are all adjustable from the operations console, with no developer and no deployment.

   Why it matters. Marketplace economics are the product. Tying them to a release schedule means the market moves faster than the business can respond.

Technical detail

Collapsed by default. Open whichever part you are evaluating.

Before and after

The build, by the numbers

What was built, at what scale. These describe the system's size, not its business results.

products delivered

4products deliveredConsumer application, marketplace engine, operations command centre and brand website

external platforms integrated

6external platforms integratedCashfree, Razorpay, Surepass, MSG91, Google Maps Platform and Firebase

live payment gateways

2live payment gatewaysBoth fully working behind a single internal contract, making provider choice a business decision

Aadhaar numbers stored

0Aadhaar numbers storedVerification runs through DigiLocker; the platform keeps only a verdict and the last four digits

What changed as a result?

Helpora moved from a brand and a business plan to a complete, launch-ready platform: a live consumer application, an operations team equipped to run the marketplace, payments and identity verification wired into India's financial and government infrastructure, and a mobile team building on foundations that were ready before they arrived. One partner. One platform. Every layer.

• Delivered a complete launch-ready marketplace platform from a brand and a business plan
• Verified identity against government records without ever storing an Aadhaar number
• Made the payment gateway a replaceable part, with two live providers behind one contract
• Put commission, pricing, escrow terms and search reach under business control with no deployment
• Handed the native mobile team a documented, tested integration package before they started

Why does this matter in SaaS & startups?

Most first builds are too large. The useful MVP is the smallest thing that tests whichever assumption would sink the business if it were wrong. Both of our internal SaaS builds — a multi-tenant school portal and a restaurant POS — started as the narrow system one operator needed, then earned their scope.

• Scope that assumes the idea is already validated

  Settings screens, admin tooling and dashboards feel like progress and prove nothing. Building them before anyone has paid is the most common way a runway disappears.

• Multi-tenancy retrofitted too late

  Serving a second customer from a system built for one is an expensive rewrite. Where multiple organisations are clearly coming, tenancy belongs in the first architecture.

• No route to a real user

  A product that exists only on a laptop cannot be tested. Deployment, accounts and access need to work from the first week, not the last.

• Handover that leaves you dependent

  Code you cannot access, hosting in someone else's account and no documentation turn your own product into a negotiation. Ownership from day one avoids that entirely.

More on what we build for SaaS & startups →

See it running