SaaS and MVP development
Web app development for SaaS products and MVPs
This is for founders building a first version, and for SaaS teams whose product has outgrown the one they started with. We design the data model, build the app in Next.js, React and Node.js, and set up the infrastructure and deploys so shipping stays routine.
You work with the people doing the work. Sachin Mour has 15+ years of building software at Verizon Media, Danske Bank and ISSUU and is CTO at Hexis. Shruti Mour leads design when a project needs it.
A first version, or a product that has outgrown one
Building an MVP
- We cut the scope to what proves the idea, and write down what we left out.
- Sign-in and payments use services like Clerk and Stripe instead of custom code.
- The data model is designed with version two in mind, so growth doesn't mean a rewrite.
Scaling a SaaS product
- We find what's slow or fragile first. Often it's the data model.
- We fix it while feature work carries on, with tests and zero-downtime deploys.
- At Hexis, a schema rebuild took multi-day queries from several minutes to under 700ms.
How we build
TypeScript end to end
Next.js or React on the front end, Node.js with REST or GraphQL on the back end, and PostgreSQL with Prisma.
Routine deploys
GitHub Actions builds every change into a container and rolls it out without downtime. Hexis ships to production every week.
Tests where they pay off
Unit, end-to-end and load tests on the paths that matter. Coverage stayed above 70% on our RYOT and Fashion Nova work.
Infrastructure as code
Google Cloud or AWS, defined in Pulumi or Terraform and reviewed like any other code.
Monitoring from day one
Dashboards and alerts in tools like Grafana and Slack, so a problem in production reaches the team quickly.
Why Next.js, and when we'd pick something else
Next.js is our default when a web app needs server rendering for search engines, fast first loads and one TypeScript codebase for pages and API routes. A dashboard that sits behind a login can be simpler as a plain React app with a separate API. Heavy backend work belongs in its own services, like the GraphQL microservices we wrote in TypeScript and Go for RYOT. We'll recommend what fits your product.
What you get
Scope and technical plan
What to build first, the data model, the stack and a timeline, agreed in writing.
The web app
A Next.js or React front end, a Node.js API and PostgreSQL, in your repository from the first day.
Auth, roles and payments
Sign-in, permissions and billing with Clerk, Supabase Auth or Stripe where they fit.
CI/CD and environments
Automated tests and zero-downtime deploys to staging and production.
Infrastructure as code
Your cloud set up in Pulumi or Terraform, with private networking.
Handover or ongoing work
Docs and a walkthrough for your team, or we keep building with you.
What we've done for clients
Hexis
Rebuilding the platform behind elite sports nutrition
We rebuilt Hexis's data model, taking multi-day queries from several minutes to under 700ms, a key factor in closing its $2.1M seed round. We also moved it to multi-region Google Cloud and set up deploys that ship to production every week.
Read the Hexis case studyCrosby Health
HIPAA-safe foundations for senior care coordination
We owned authentication, permissions, Stripe payments and the data layer for Crosby360, a platform for CMS care programs like GUIDE. Each person sees only the patients and records their role allows.
Read the Crosby Health case studyVerizon Media / RYOT
A 3D creation pipeline for the NFL, HuffPost and Yahoo
We led a team of nine and built the backend of RYOT's 3D creation tool from scratch: GraphQL microservices in TypeScript and Go with synchronous responses under 300ms, and a headless Blender pipeline on Kubernetes.
Read the Verizon Media / RYOT case studyHow a project starts
From a free call to the end of the second week.
A free 30-minute call
Tell us what you're building, who it's for and where things stand. We'll ask about deadlines, budget and what has to work on launch day.
A fixed price, or hourly
After the call we send a fixed-price quote for a clear scope, or agree on hourly work at $100 to $150 an hour. An MVP with a clear scope is usually a fixed price. Ongoing development on an existing product is usually hourly.
The first two weeks
- We map users, core flows and the data model, and agree on what stays out of the first release.
- We set up the repository, environments and CI/CD, so every change deploys to staging.
- We ship a first thin slice to a staging URL you can click through.
Frequently asked questions
How long does it take to build an MVP?
It depends on scope, and we'd rather cut scope than stretch the timeline. The quote states both. For a range before we talk, get a rough estimate.
How much does a web app cost?
We charge $100 to $150 an hour, or a fixed price for a defined scope. Using managed services for sign-in and payments keeps a first version smaller and cheaper.
Can you work on our existing codebase?
Yes. We start with a short review of the code, data model and deploys, then fix what's in the way while shipping features. At Hexis we rebuilt the data model while the product kept growing.
Why Next.js?
It gives you server rendering for search engines and fast first loads, React for the interface and one TypeScript codebase. We also build plain React apps, Nest.js or Express APIs and GraphQL services when they fit better.
Can you design the product too?
Yes. Shruti Mour leads product design: research, UX, UI and design systems. Design and engineering in one studio means fewer handoffs.