From Brochure Site to Two-Portal MERN CRM: Moraya Developers Engineering Teardown

Moraya Developers had completed 10+ projects and served 1,800+ buyers across Pune — but their digital footprint was a static brochure site and a WhatsApp-driven sales pipeline. The result: leads slipping through the cracks, no visibility into channel performance, no way to showcase pre-launch projects, and almost zero local search rankings.

This is the engineering teardown of Moraya Developers — what we built, why MERN was the right call here, and how we got to sub-10-second lead routing without paying enterprise CRM prices.

The Problem

Real estate is one of the highest-intent verticals in digital marketing. A buyer searching "3 BHK in Wakad" or "ready possession Hinjewadi" has typically narrowed down to a 2-week buying window. Every minute between enquiry and first salesperson contact materially changes the conversion rate.

Moraya's existing flow:

• Enquiry comes in via website form, Facebook, JustDial, or WhatsApp
• Sales agent eventually sees it via WhatsApp ping or email check
• Manual entry into a Google Sheet
• Source not tracked; follow-up not automated

Sub-30-minute response is industry baseline; Moraya was averaging 2–4 hours. The cost: an estimated 25–40% of leads going to faster competitors.

The Architecture

A two-portal MERN application:

• Public buyer portal — Property listings, pre-launch project pages with countdown timers, rich galleries, embedded Google Maps, enquiry forms scoped per property
• Private admin CRM — Sales-team dashboard for lead management, listing CRUD, pre-launch workflows, source-attribution analytics

Single MongoDB Atlas database, both portals share. Express.js API layer. React frontend split into two builds. Node + Nodemailer for transactional email. Hosted on a Hostinger VPS behind Nginx; SSL via Let's Encrypt.

Key Technical Decisions

Sub-10-Second Lead Routing via Direct Email Trigger

The brief was clear: a lead submitted at 11:47:23 should be in the assigned sales agent's inbox by 11:47:33. We achieved this with a synchronous Nodemailer call inside the form-submission handler, not a queued background job.

Trade-off: if SMTP is down, the API request fails and the user sees an error. We considered a queued job for resilience, but at Moraya's volume (50–150 leads per day) the synchronous path is fine and the failure-path UX is honest. Better to tell the user "submission failed, please try again" than to silently queue and lose the lead in a stalled worker.

Pre-Launch Workflow with Auto-Conversion

A unique requirement: showcase pre-launch projects with countdown timers ("Launching in 23 days") and have them automatically convert to standard listings on launch date — without developer intervention.

We modelled this as a launchDate field on the project model with a status enum (pre-launch, active, completed). A daily cron job (node-cron) checks for projects whose launchDate has passed and status === 'pre-launch', flipping them to active. The frontend renders different layouts based on status. Sales-team admin can manually trigger early activation if a project launches ahead of schedule.

Source Attribution with UTM Awareness

Every enquiry submission captures the URL the form was on, plus any UTM parameters present. The backend parses these on intake, normalises into channel categories (organic, paid-search, social, referral, direct), and tags the lead. The admin CRM dashboard then shows lead-volume and conversion-rate breakdowns by channel.

This was the single biggest organisational win. Within three months, Moraya could see definitively that 40% of converted leads came from organic search — which justified continued SEO investment vs paid spend reallocation.

Local SEO Foundation

The brochure site ranked for nothing. Within four months of launch, the new site ranks on page 1 for "Moraya Developers", "Moraya Wakad", and several project-name queries. The wins came from:

• Server-side rendering all property pages with structured property schema
• Embedded Google Maps with proper schema markup
• Breadcrumb navigation with BreadcrumbList JSON-LD
• Sitemap.xml regenerated nightly to surface new listings to Google fast
• City + locality keywords integrated into headings and meta naturally — not stuffed

For more on the structural decisions behind on-page SEO, the broader patterns we use are covered in Custom Software vs Off-the-Shelf and Build vs Buy CRM ROI — both of which informed this build.

Why MERN, Not Next.js + Supabase

In 2026, the modern default for a build like this would be Next.js + Supabase, not MERN. We deliberately picked MERN because:

• The client's existing developer (one part-time engineer) was a Node + Mongo specialist
• Continuity matters more than framework freshness for a small in-house team
• The cost difference at this scale was negligible

This is one of those cases where the "best" tech-on-paper isn't the best tech-in-context. If we'd handed Moraya a Next.js + Supabase stack, the maintenance bill would have been higher than the build bill within six months.

What We'd Do Differently

If we revisited this build:

• Use a managed transactional email provider (Resend, Postmark) instead of Nodemailer + Gmail SMTP. The setup is simpler and deliverability is better.
• Move from cron-based pre-launch conversion to a scheduled cloud task. node-cron in a single VPS dies if the box restarts mid-job; a managed scheduler is more reliable.
• Add structured property schema to the case-study and project pages from day one. We added it later; should have been baseline.

Where Nexolve Fits

Real estate, B2B services, and education are three verticals where a properly-engineered two-portal site dramatically outperforms generic page-builder solutions. Our SaaS & Web Apps service handles builds like this end-to-end. For more on the broader build vs buy decision, see Custom Software vs Off-the-Shelf.

For the full project context, see the Moraya Developers case study.