SaaS and web app development, from first version to paying users
I build SaaS products and web apps: the part customers use, the admin that runs it, and payments. A first version people will pay for usually costs $30,000–70,000 and takes 6–14 weeks.
Scope
What I build
First versions (MVPs) people will pay for
Customer dashboards and portals
Admin panels and internal tools
Marketplaces and booking platforms
Subscription and payment systems
Multi-tenant SaaS for many businesses
Pricing
How much a SaaS or web app costs
Freelance prices in US dollars. The biggest factor is what the first version has to do. Accounts, payments, and an admin that staff use daily are what move a product from the first row to the third.
| Type | Price | Timeline | What you get |
|---|---|---|---|
| Clickable prototype or demo | $3,000–12,000 | 1–3 weeks | Enough to show investors or test with users. Not built to take real payments or data. |
| Internal tool or admin platform | $15,000–35,000 | 4–10 weeks | One job for your own team, like school admin, operations, or reporting, with logins and roles. |
| First version people pay for | $30,000–70,000 | 6–14 weeks | Customer accounts, payments, the core workflow, an admin, and production hosting. |
| Full platform | $80,000–200,000 | 3–6 months | Several user types, many integrations, and features beyond the first version. Usually built in phases. |
Real examples: an NFC card platform cost $25,000 over 8 weeks and now has 30K+ users. A farm rental platform cost $40,000 over 14 weeks. School software for 1,000+ students cost $32,000 over 10 weeks.
Approach
How I build a SaaS product
Most first versions fail because they try to do everything. I start with the one job the product has to do well, build that properly, and ship it to real users.
Start with the one job
Who pays, what they need to do, and what the first version must include to be worth paying for. Everything else waits.
Build the whole product
The customer app, the admin that runs the business, payments, emails, and the backend. One person, one codebase, no hand-offs.
Built to grow
Accounts, roles, background jobs, and data structured so the product can grow without a rewrite.
Launch and improve
Production hosting, monitoring, and a product real users can rely on. Then we improve it based on what they actually do.
Capabilities
What I can handle
Product
- Scoping the first version
- Customer-facing app
- Admin and back office
- Design from scratch or Figma
Product systems
- Accounts, roles, and permissions
- Payments and subscriptions
- Background jobs and queues
- Multi-tenancy
- Realtime updates
Integrations
- Stripe, Razorpay, PayPal
- Email, SMS, and WhatsApp
- CRMs and third-party APIs
- Maps and location
Production
- Hosting and deployment
- Monitoring and backups
- Security
- Speed at scale
Typical stack
- Next.js
- React
- TypeScript
- NestJS
- PostgreSQL
- Redis
Difference
What goes into the build
Products with real users
An NFC card platform with 30K+ users and 10K cards sold. A printing platform handling 400+ orders a day across 40+ branches. These are live businesses, not demos.
The whole product, not just the screens
The farm rental platform runs everything from plot sizing and farmer matching to live cameras, Stripe subscriptions, and delivery. I build the operations side too.
Fast to a first version
The NFC platform went from start to launch in 8 weeks. School software for 1,000+ students took 10.
Built so it doesn't need a rewrite
The structure is set up for growth from day one, so adding features later doesn't mean starting over.
Proof
Selected work
- Confidential
NFC card platform
2025
NFC business cards: 30K+ users, 10K cards sold, 20K taps
- Confidential
Printing platform
2024
Printing platform: 400+ orders a day across 40+ branches
- Confidential
Farm rental platform
2026
Farm rental platform: 200+ customers and 1,000+ harvest deliveries
Hongirana
2023
School software for 1,000+ students: attendance and fees automated
Process
How a project works
- 01
A call and a written scope
What the first version must do, who uses it, and what it connects to. You get it in writing with a price and timeline.
- 02
Design
The key screens designed or built from your Figma file. You approve them before the full build.
- 03
Build
The product, the admin, and the backend together, with a live preview you can try as it grows.
- 04
Launch and grow
Live in production with real users. Then I keep building the next version, or hand it over to your team.
Clients
What clients say
“Milan built the whole platform, from the profile editor to payments. Our customers change their details in seconds, and every card they've handed out updates.”
Founder NFC business cards: 30K+ users, 10K cards sold, 20K taps“Milan took our print shops online. Customers upload, pay, and pick up their prints in minutes, and every branch gets clear instructions for each order.”
Founder Printing platform: 400+ orders a day across 40+ branches“Milan turned our idea into something that actually runs the business, from the first enquiry to the harvest delivery. Customers love watching their plots live.”
Founder Farm rental platform: 200+ customers and 1,000+ harvest deliveries
FAQs
How much does it cost to build a SaaS product?
A first version people will pay for usually costs $30,000–70,000 with me. An internal tool is $15,000–35,000, and a clickable prototype $3,000–12,000. My recent SaaS projects cost $25,000–40,000.
How long does it take to build an MVP?
Six to fourteen weeks for a first version with accounts, payments, and an admin. My NFC card platform took 8 weeks and a farm rental platform 14. A clickable prototype takes 1–3 weeks.
What should go in the first version of my product?
Only what a customer needs to get the main job done and pay for it, plus the admin you need to run it. Nice-to-have features wait until real users show you what matters.
Which tech stack do you use?
Usually Next.js and TypeScript, with NestJS or a similar backend and PostgreSQL. I pick what suits the product and what your future team can hire for, not what's trendy.
Do you work for equity?
Usually not. I work for cash: a fixed price when the scope is clear, or hourly when the work will keep changing. Equity only makes sense for someone who stays long-term and shares the risk, and you own the product outright either way.
I already have a product. Can you continue it?
Yes. If it's working, I pick up from where it is. If it's buggy or half-built, that's a takeover, which starts with a code review.