Web Platforms
Web apps that load fast and grow with you
We build SaaS products, marketplaces, dashboards and portals on proven stacks, so your first version is fast, secure and ready to scale.
- Core Web Vitals in Google's “good” range at launch
- Live staging link from week 2
- Your cloud, your repo, your accounts
Sound familiar?
The problems we hear most
“Our MVP slows down every time real users show up.”
“The last team left code nobody can safely change.”
“We've spent months building features nobody uses.”
Outcomes
What changes for you
A launch-ready MVP, scoped to what your users need first.
Pages that pass Core Web Vitals: LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1.
An architecture that grows to multi-tenant and new markets without a rebuild.
Capabilities
What we build
SaaS & multi-tenant platforms
Subscriptions, roles and team workspaces.
- Next.js
- PostgreSQL
Marketplaces & portals
Listings, search, bookings and payouts.
- Node.js
- Redis
Dashboards & internal tools
Real-time data, admin panels and reporting.
- React
- WebSockets
Payments & commerce
Razorpay, UPI and Stripe, with GST-ready invoices.
- Razorpay
- Stripe
Integrations & APIs
CRMs, ERPs, WhatsApp Business, webhooks and public APIs.
- REST
- Webhooks
Rescue & rebuild
Audits, performance fixes and migration off legacy stacks.
- Audits
- Migration
Deliverables
What you walk away with
Everything is yours at handover: in your repository, your accounts and your files.
- Architecture document
- Design system and screens
- Web app: front end and back end
- Admin panel
- Authentication and user roles
- Payments
- Analytics events set up
- CI/CD pipeline
- Staging and production on your cloud account
- Automated tests
- Technical docs and a recorded handover
Timeline
Typical MVP
A typical engagement, week by week. Your plan is confirmed in the Discovery Sprint.
- 01
Week 1
Discovery and scope
- 02
Weeks 2–3
UX and UI design
- 03
Weeks 3–9
Build in 1-week sprints, demo every Friday
- 04
Week 10
QA, security review, launch
- 05
After launch
Free post-launch fixes
Technologies
What we build with
We choose the stack that fits your product, not the other way round.
- Front end
- Next.jsReactTypeScriptTailwind CSS
- Back end
- Node.js (NestJS, Express)Python (FastAPI)
- Data
- PostgreSQLMongoDBRedis
- Cloud
- AWSVercelGoogle Cloud
- Payments
- RazorpayStripe
Ways to start
Pick the size of the first step
Each option has a fixed scope and a fixed quote.
1–2 weeks
Discovery Sprint
Best for: Founders who want a clear scope and price before committing
Fixed quote after a free call
- Scope and product brief
- Clickable prototype of the core flow
- Fixed quote for the build
8–10 weeks
MVP Build
Best for: A custom web product, launched and ready to grow
Fixed quote after a free call
- Design, build and launch
- Staging link from week 2
- Free post-launch fixes
1 week
Rescue Audit
Best for: Products another team built that now feel risky to change
Fixed quote after a free call
- Code quality, security and performance review
- Written report
- Prioritised fix plan
Right fit
Are we right for this?
Great fit if you…
- Need a custom product, not a template site
- Can join a weekly 30-minute demo
- Want to own the code
- Plan to grow past the first version
Probably not a fit if you…
- Need a 5-page brochure site
- Need launch in under 3 weeks
- Want to change scope daily without a product owner
Quality & security
Standards this work ships with
- OWASP Top 10 review before launch
- WCAG 2.2 AA accessibility
- Automated tests on core flows
- Uptime monitoring and daily backups
- Personal-data handling ready for India's DPDP Act: consent, export and deletion
FAQ
Common questions
Something else on your mind? Ask us directly.
How much does a web app or SaaS MVP cost with ZARX?
It depends on scope: how many user roles, integrations and screens the first version needs. Most clients start with a 1–2 week Discovery Sprint that ends with a clickable prototype and a fixed quote for the build. You commit to the build only after you've seen the plan and the price, and the quote stays fixed for the agreed scope.
Can you take over and fix a product another team built?
Yes. We start with a one-week Rescue Audit of the code, security and performance, then give you a written report and a prioritised fix plan. You can fix the riskiest parts first, rebuild in stages, or hand the plan to your own team. We only recommend a full rewrite if the audit shows it costs less than repairing what you have.
Which tech stack will you use, and can we choose?
Our default is Next.js and TypeScript on the front end, Node.js or Python on the back end and PostgreSQL for data, because they are proven and easy to hire for. If you already have a stack, or a strong reason to use another, we compare the trade-offs during discovery and use what fits your product and your team.
Who owns the hosting, domain and third-party accounts?
You do. We set up hosting, domains, payment gateways and other services in accounts your company owns, and work inside them with access you control. Code lives in your GitHub or GitLab from day one. At handover you already hold every credential, so there is nothing to transfer and no lock-in.
Will the app be SEO-friendly and fast on mobile?
Yes. We use server rendering where it helps search, clean URLs, metadata and structured data. We test on mid-range phones and set a performance budget so pages meet Google's Core Web Vitals “good” thresholds at launch: LCP within 2.5 seconds, INP within 200 milliseconds and CLS under 0.1.
Can you accept Indian and international payments?
Yes. We integrate Razorpay for UPI, cards and netbanking in India, and Stripe for international cards and subscriptions. We also set up GST-ready invoices, refunds and payment webhooks so your finance records stay accurate. The payment accounts are opened in your company's name, so the money and the data stay with you.
What does post-launch support cost?
Every build includes free post-launch fixes for bugs in what we delivered. After that, support is optional: a monthly retainer covers monitoring, updates and new features, sized to the hours you need. You can also take everything in-house, because the handover docs and recorded walkthrough are written for exactly that.
Often paired with
Services that work well together
Let's build
Ready to put your product on the web?
Tell us what you're making. A founder replies within one working day with next steps, a rough timeline and a budget range.
NDA on request. You own the code.
