Project

Dharmsy Innovations — SaaS & AI Product Studio

Next.js + MongoDB marketing site for a SaaS and AI product studio — per-service and service × location pages, a blog with its own admin, and structured data on every page type, positioned around shipping a founder's MVP in about 30 days.

Dharmsy Innovations homepage hero — a SaaS and AI product studio site showing an MVP delivered in 30 days
Cover image for the Dharmsy Innovations case study.

About this project

Dharmsy Innovations is a registered product studio, and dharmsy.com is the site I designed and built for it. There was no external brief on this one: the positioning, what the studio sells, and how the pages are structured were all part of the work rather than handed over as a spec. The positioning is deliberately narrow: SaaS products, AI agents and mobile apps for early-stage founders, shipped as a working MVP in about 30 days, with the founder as the single point of accountability rather than an account manager and a rotating team. Narrow positioning makes the site easier to write and much easier to rank, because every page can argue one thing properly instead of listing everything a generalist agency could theoretically do. Structurally it is a full marketing site rather than a landing page: a services layer with individual pages per capability, service × location pages for the markets the studio actually sells into (Bengaluru, Delhi NCR, Chennai, London, New York, Sydney, UAE, Canada, Australia), an industries section, case studies, a blog with its own category system, careers, and a contact flow that puts leads into a database rather than an inbox. The engineering side is the part I would point a hiring manager at. It is a Next.js App Router build on MongoDB, server-rendered with incremental static regeneration so the marketing pages are static-fast while the content stays editable from an admin dashboard. Every page type ships structured data — Organization, WebSite, Service, OfferCatalog, Offer, FAQPage, Person and ContactPoint — because the studio sells to founders who increasingly find suppliers through AI answer engines rather than through ten blue links, and a page with no machine-readable summary does not get quoted. The lesson from building it: the hard part of a studio site is not the code, it is refusing to widen the offer. Every extra service you list makes the site less convincing and every page harder to rank. The version that went live says no to more than it says yes to, and it is the better site for it.

Tech Stack

Next.jsReactTailwind CSSNode.jsMongoDBMongooseAWS S3CloudFrontJSON-LD Structured DataVercel

Frequently Asked Questions

Dharmsy Innovations is a registered private limited product studio in India. It partners with founders and early-stage startups to design, build and launch SaaS products, AI-powered tools and mobile apps — from idea through to something running in production with real users. The studio site is at dharmsy.com.
I worked as the full-stack developer across the whole build — the Next.js front end, the admin-driven content system, the service and location page architecture, and the structured data layer. The positioning and information architecture were part of the work rather than delivered as a brief, which is why the site argues one narrow offer instead of listing everything an agency could theoretically do.
Next.js (App Router) with React and Tailwind CSS on the front end, Node.js and MongoDB behind it, and AWS S3 with CloudFront for media delivery. Content is editable through a custom admin dashboard rather than a headless CMS, and pages use incremental static regeneration so they serve static-fast while staying editable. The studio's stated stack — Next.js, React, React Native, Node.js, TypeScript, MongoDB, PostgreSQL, OpenAI, AWS, Vercel — is listed on the site itself.
It is a full marketing site rather than a single landing page: individual service pages per capability, service × location pages for the markets the studio sells into, an industries section, case studies, a blog with its own category system, a careers page, and a contact flow that writes leads to a database. The service × location layer covers Bengaluru, Delhi NCR, Chennai, London, New York, Sydney, UAE, Canada and Australia.
Two layers. Conventional SEO — one clear intent per page, canonical URLs, a generated sitemap, real internal linking between services and locations rather than a footer link dump. Then answer-engine optimisation on top: every page type emits JSON-LD, including Organization, WebSite, Service, OfferCatalog, Offer, FAQPage, Person and ContactPoint, and every page carries a real FAQ block whose answers are in the served HTML rather than hidden behind a click. AI answer engines quote what they can parse, and an accordion that only renders its answer in the browser gives them nothing.
They do different jobs. This portfolio is about the engineer — what has been built, how I work, and whether I am the right person to hire. Dharmsy is about the offer: a defined scope, a timeline, and a company a founder can raise an invoice against. Making one page do both would have made it worse at each. Keeping them separate also meant the same content and schema approach could be tested twice, on two sites with different goals.
It refers to the MVP scope the studio sells: one core workflow built properly — authentication, the workflow itself, billing, an admin panel, deployed and handed over — inside roughly a 30-day window. It is not a promise that any product can be built in a month. The scoping conversation exists precisely to establish what fits into that window and what has to be a later phase, and the written scope names both.
Agencies sell hours and assign a team you rarely meet. At Dharmsy you work with the founder directly — one person accountable for the whole product, from architecture through to handover. The trade is honest: capacity is limited and only a small number of projects run at a time. Fewer layers buys faster decisions and no translation loss between the person who scoped the work and the person writing the code.
AI is core to the offer, not a bolt-on. That means AI agents that carry out real work, LLM integrations wired into the product's own data, and workflow automation designed as part of the architecture rather than added as a chat widget at the end. The studio also sells AI-search visibility work — answer engine and generative engine optimisation — which is the same discipline applied to being found rather than to the product itself.
Both are possible and it depends on what you need. For a scoped product build with an invoice, a contract and a company behind it, Dharmsy is the right route — start at dharmsy.com or use the contact form here. For a senior full-stack or AI engineering role, or a longer-term embedded engagement with your team, contact me directly through this site. Either way you are speaking to the same person, and I will tell you plainly if what you need is not something I should take on.

Details

Organization
Dharmsy Innovations Pvt. Ltd.
Role
Full-Stack Developer
Timeline
Ongoing — own product

Questions about this project?

Tell me what you're building — I'll reply within 24 hours.