Tulsi Heritage Farms

Overview

Tulsi Heritage Farm is a third-generation family farm in Frederick County, Maryland, balancing four revenue streams — a public farm store, indoor/outdoor event spaces for weddings and gatherings, a membership community, and seasonal produce sales. We shipped the public site and the back-office dashboard in 3 weeks, working remotely from Kagaznagar with the owner family on a daily async cadence.

The problem

The farm had grown past the spreadsheet-and-phone-call stage. Event enquiries arrived through the contact form, the old website, Facebook messages, and word-of-mouth, all converging on the owner's phone. Farm-store inventory lived in one spreadsheet. Member sign-ups in another. Stripe payments landed in a third place. There was no single view of 'what's this weekend' — events, staffing, farm-store stock, expected walk-in traffic. The owner was the integration layer, manually, every day.

What we built

• •Designed and built a public marketing site — heritage story, farm-store storefront with Stripe checkout, event-space enquiry form, and member sign-up flow — all with imagery the farm already had.
• •Built an operational dashboard with a single home screen: today's events, tomorrow's events, this week's deposits due, low-stock farm-store items. Everything the owner needs to see at 7am before opening.
• •Integrated Stripe for farm-store checkout and event deposit collection — deposit receipts land automatically, event status updates from 'enquiry' → 'deposit paid' → 'confirmed' without the owner touching anything.
• •Added a winter-closure banner that the owner can flip from the admin panel without a code change — farm stays seasonal, the site should reflect that without a redeploy.
• •Built the community membership surface with tiered sign-up (Supporter / Harvest Share / Full Member) tied to a Firestore-backed member directory the owner can filter and export.

Key features

• Event-space enquiry + deposit flow with Stripe integration
• Farm-store storefront with seasonal inventory toggles (a farm closes in winter)
• Admin-editable seasonal banner (e.g. 'Winter Farm Closure') without a code change
• Tiered community membership sign-up with a Firestore-backed member directory
• Today/tomorrow dashboard home — events, deposits due, low-stock items, all on one screen
• SEO-optimised public site with Stripe checkout and live event availability

Results

The farm runs its entire digital operation from one admin panel. Event enquiries convert into Stripe-paid deposits without the owner having to chase, farm-store inventory stays current without a separate spreadsheet, and the membership community has a proper home. A Maryland family farm, run from a laptop, with the dev team sitting in Kagaznagar — shipped in 3 weeks.

Replaced the spreadsheet-and-phone-call operation with a single admin dashboard plus a public marketing site that handles event enquiries, farm-store ordering, and member sign-ups. Owner runs the farm's digital operations from a laptop instead of chasing the paper trail across three rooms.

What we learned

• →Working across a 10-hour time-zone gap (Maryland ↔ Telangana) forced a proper async cadence — video walkthroughs instead of calls, and daily Loom updates instead of live demos. Ended up being faster than a co-located build.
• →'Farm operations' looks different in Maryland than in India — event-space revenue + four-season closures are core concerns we wouldn't have intuited from the brief alone.
• →Designing for a two-generation family business requires the dashboard to work for both the tech-comfortable child and the tech-averse parent. Simpler is always the right bet.

Stack