Two developers,
working parallel, not in line.

Everything a member touches directly. Harsh works through it in the order a member actually experiences the app — assessment first, then the daily habit loop, then courses, rewards, and finally real payments. Each piece is built, reviewed with you, and revised before the next one starts, rather than banking changes for a review pass at the end — which is what fills the ten weeks, not extra padding.

• Health assessment closed out to the full clinical spec

  Today's assessment only covers part of the intake spec. This closes the gap to the complete 37-question, 8-category questionnaire — demographics, diabetes history, medication, food habits, activity, stress, sleep and goals — with male/female-conditional sections and every question type the spec calls for. Every new member is risk-scored against the full picture from day one, not a partial one.
• Daily habit tracker with photo capture and real points formula

  The engagement loop that drives daily app opens. Members check off all 10 fixed habits — from fixed bed time and gratitude practice to avoiding refined sugar — every day, with 3 of them (detox tea, protein breakfast, healthy-plate) requiring an actual photo upload as proof, not just a tap. Each habit is worth 10 points, capped at 100 points a day, replacing the placeholder event-based reward system currently in the app.
• Course library with tier-gated content

  The in-app replacement for Lifetrons. Admin builds courses out of a Course → Module → Lesson structure, adding video, PDF or text lessons and assigning each to a tier. Members watch or read at their own pace with a resume-from-where-you-left-off player, pass an end-of-module quiz to earn a completion badge, and see an upgrade prompt — not a broken page — if a course sits above their tier.
• Rewards, tier enforcement, and live Razorpay payments

  Where the point economy and the money meet. Points a member earns convert to a real ₹ credit they can apply toward a DWC or DWM upgrade at checkout, and every paid page and course in the app — not just the ones flagged during onboarding — checks and enforces the member's actual tier. Razorpay handles the underlying subscription billing and renewal.
• Full device testing, App Store & Google Play submission

  Before anything reaches a real user: full testing on the current and one prior OS version on both Android and iPhone, including a live end-to-end run of the actual Razorpay payment flow, not a sandbox stub. Once that passes, the build is filed to both the App Store and Google Play for review.
• Your review and revisions folded into every step, not saved for the end

  Every deliverable above is shown to you as it lands, not bundled into one review pass in Week 10. If something needs a change, that happens before the next piece starts, so revisions stay cheap instead of stacking up.

The CRM, accounts and HR tools are already built and tested. This track doesn't touch the app, so it doesn't need to wait for one — Guru starts the same day Harsh does. The backend panel and journey engine are built, reviewed with your team, and revised piece by piece over six weeks, so nothing reaches Week 6 as a surprise that still needs reworking.

• CRM, Accounts and HR — already live

  Not a promise — this is already running. The CRM tracks leads through a 5-stage pipeline (New → Contacted → Demo → Converted → Lost) with CSV import and duplicate detection; Accounts handles revenue/expense entry, monthly P&L with margin %, and month-end close; HR covers staff directory, attendance, leave approval, and a full payroll run with payslips. All three have been tested against real data, not just built.
• Backend control panel — points, pricing, visibility, roles

  The single settings hub that removes "ask a developer to change that" from your team's daily work. From here, your team edits a habit's point value, rewrites an HRA question, changes what DWC costs, or hides a page from a role — and it takes effect immediately, with no code deploy.
• Journey engine — auto plan assignment on client entry

  Right now, every new client's plan is assigned by hand. This automates it: the moment someone signs up, a Day-1 clock starts automatically and they're placed on the correct journey template for their program — no one on your team has to remember to do it.
• Journey-template editor, configurable by your team

  The tool behind the journey engine. Your team creates and edits journey templates directly — the stages, the day-offsets between them, what unlocks when — through a screen, not a support ticket to a developer.
• Full regression across every module

  Before this ships, CRM, Accounts, HR, and the new journey engine are tested together as one system, not four separate pieces — catching anything that breaks when they interact, not just when each one runs alone.
• Production deployment and handover docs

  Live on your actual servers by Week 6, with documentation written for your team to operate — not just for a developer — so day-to-day use doesn't depend on anyone being on call.

The moment the dashboard ships in Week 6, Guru moves straight into the CRM and marketing-automation side of the lead engine — no idle week waiting on the app. Harsh adds the piece members actually see, in-app webinar registration, in Weeks 11–12 once the consumer app ships. Both pieces are reviewed and signed off with you as they land, so the finish line is just the last of many check-ins, not the first one.

• Facebook Lead Ads auto-create leads in the CRM — Guru

  Right now, leads from Facebook ads have to be added to the CRM by hand. This wires a webhook directly from your Facebook Lead Ads account so every lead lands in the CRM the moment they submit the form, already tagged with the campaign and ad that produced them.
• WhatsApp, SMS and email sequence builder — Guru

  Your team builds a drip sequence — a series of WhatsApp, SMS or email messages sent automatically over time — from inside the dashboard, routed through your existing marketing tool rather than a new platform to learn.
• Ad spend imported for a real cost-per-channel number — Guru

  Today, CAC (cost per acquisition) is a guess. This imports actual ad spend into the P&L and matches it against which leads converted, so you get a real cost-per-channel number instead of an estimate.
• Multi-program support beyond diabetes reversal — Guru

  Built so the same CRM, journey engine and lead automation extend to future programs — Weight Management, Fitness — without rebuilding any of it from scratch when you're ready to launch one.
• Webinar registration inside the app — Harsh

  Members register for a webinar without leaving the app, get an automatic reminder before it starts, and — if they don't show up — an automatic follow-up message afterward, instead of your team tracking attendance by hand.
• Combined regression across both tracks before ship

  The app side (webinar registration) and dashboard side (CRM automation, sequences) of the lead engine are tested together as one working system before anything is called done — not verified separately and hoped to connect correctly.