A matrimony platform, and the console that actually runs it

What was the problem?

A matrimony business is mostly operations. Every profile photo and identity document needs human review before it goes live, reported profiles need investigating, plan enquiries need following up, member details need correcting, and staff need different levels of access depending on their role. Without a purpose-built tool, that work spreads across spreadsheets and shared logins — slow, unauditable and unsafe for data this sensitive.

What we built

A verification queue where photos and documents are approved or rejected with a reason and images can be cropped before approval. A 360-degree member editor spanning twelve sections. Staff management with custom roles scoped per section. Enquiry and complaint workflows with status progression. A notification system covering instant sends, topics, scheduled campaigns and delivery monitoring. And an analytics dashboard over registrations, verification, engagement and notification performance.

What it does

• Photo and document verification queue

  Approve or reject with a reason, with in-place cropping and adjustment before approval.

• 360-degree member profile editor

  Twelve dedicated sections covering everything from KYC to partner preferences.

• Configurable staff roles

  Custom roles with per-section view and edit control, activatable and deactivatable at any time.

• Member directory

  Search, filters, sorting and export across the full membership.

• Push notifications and campaigns

  Instant pushes, topics and subscribers, scheduled campaigns with send/cancel control.

• Delivery monitoring

  Success rates, failures, retries and a complete event log of everything sent.

• Reported user workflow

  Review reports and warn, block or dismiss.

• Plan enquiry tracking

  Status progression through follow-up.

• Profile PDF generation

  Downloadable member profiles for sharing.

• Credential management

  Reset member passwords and PINs, and employee passwords.

• Analytics dashboard

  Registrations, verification status, engagement and notification performance.

• Responsive operations

  The full panel works on mobile, tablet and desktop with live data refresh.

What changed as a result?

MatchingJodi runs members, verification, staff, enquiries, complaints and campaigns from one place, on desktop or mobile, with fast search, live refresh and one-click export from every list.

• Delivered the mobile app, backend, marketing site and operations panel as one engagement
• Built a verification queue with reasoned approval and in-place image adjustment
• Made staff permissions configurable per section for any custom role
• Added campaign scheduling with delivery monitoring and a full event log
• Made the whole operations panel usable on mobile as well as desktop

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