Skip to content

Full-Stack SaaS Developer I build software
that runs businesses.

For founders and teams with serious SaaS and business products, especially when the software is already live, interconnected, or getting harder to change.

12+ years
Experience · modern workflows
SaaS & business software
Production products
Full-stack ownership
Backend through production
Production systems
Code through to live
Production evidence

Systems I've helped build and evolve.

Shoprocket logo
Flagship case study 7+ year client relationship

A multi-tenant commerce platform where merchant operations, payments, orders and storefront embeds share one backend.

7+ years as lead engineer on most of the platform, from backend architecture to the vanilla JavaScript storefront embed.

Laravel Livewire Vanilla JS MySQL REST APIs
Explore the Shoprocket case study
Shoprocket shipping management across the merchant dashboard and customer storefront
Shoprocket merchant dashboard listing customer orders
Shoprocket storefront product listing, product detail and checkout on mobile
SaaS · Competition platform
Basecomp logo

Lead backend engineer on a multi-tenant competition platform, auditable draw logic, entrant management and payment paths that had to stay correct under spiky traffic.

Laravel · MySQL · AWS · Stripe

Explore the case study →
File-sharing · Existing product at scale
ufile.io logo

Joined a live file-sharing platform already under load, production fixes, query optimisation and chunked uploads with pause and resume, without disrupting users.

PHP · MySQL · AWS

Explore the case study →
Systems thinking

The difficult part wasn't building the features.

It was making interconnected production workflows behave reliably when a change in one area affects products, inventory, payments, orders and shipping elsewhere in the system.

See how this played out on Shoprocket →

One commerce workflow

  1. Products
  2. Inventory
  3. Cart
  4. Checkout
  5. Payment
  6. Order
  7. Fulfillment
  8. Shipping

Multi-tenant commerce

Thousands of independent merchant stores on one platform, each with isolated data, workflows and configuration.

Connected state

Products, inventory, carts, payments and orders have to stay consistent as workflows move through the system.

Unreliable integrations

Payments, webhooks and third-party systems fail, retry or arrive out of order. The platform still has to stay correct.

How I work

I don't start with code.

I work backwards from the product problem, the users and the constraints toward the simplest solution that can survive production. When a feature touches orders, payments, APIs and integrations, I map dependencies and tradeoffs first, then implement with ownership across the stack.

01

Understand

What the product needs, what's already in place, and the architecture and tradeoffs before choosing how to build it.

02

Build

Hands-on work across backend, frontend, data, APIs and integrations, validated for edge cases, failures and performance before and in production.

03

Own

I care about what happens after the code ships: production issues, technical debt and what comes next, not ticket completion.

You stay in the loop throughout. These stages loop continuously, not a one-way handoff from spec to delivery.

AI-assisted engineering

Modern tools. Experienced engineering.

AI-assisted development helps me move faster through exploration, implementation and iteration. Architecture, security and production decisions stay mine.

AI accelerates

Exploration, implementation, refactoring, test scaffolding and debugging assistance.

I remain responsible for

Architecture, requirements, tradeoffs, security, correctness, code review and production decisions.

What you get when you work with me

Built for ownership, not just tickets.

You don't just get someone to write code. You get an experienced engineer who understands the product, owns the engineering and stays accountable in production, with evidence for each claim on this site.

01

I understand the product

You shouldn't have to translate the entire business problem into tickets before I can help. I want to know what the software needs to accomplish before deciding how to build it.

See the work →
02

I can own the whole problem

When a checkout change affects inventory, payments and order state, I can follow the problem across backend, APIs, integrations and frontend without handing off every boundary.

See the work →
03

I improve what already exists

I look at what already works, identify the real constraints and improve the system incrementally, the same approach behind Shoprocket's V1 to V2 evolution and joining ufile.io at scale.

See the work →
04

I stay accountable after it works

I care about reliability, edge cases and what happens after deployment, and I've stayed involved long enough for clients to validate that independently.

Read the testimonial →
Client perspective

From the person behind the product.

Ryan Badger, CEO of Shoprocket, has worked with me for 7+ years across the evolution of the platform, from the original stack through V2 and the commerce systems that followed.

Shoprocket logo 7+ year engineering relationship
Explore the Shoprocket case study →

“I've had the pleasure of working with Indesh for several years across multiple projects, and I can confidently say he's one of the best developers I've worked with. His technical skills are exceptional, particularly in Laravel, APIs, SaaS platforms, and scalable backend systems. He consistently delivers high-quality work, communicates clearly, and always approaches challenges with professionalism and attention to detail.

Beyond his technical ability, Indesh is reliable, trustworthy, responsive, and genuinely enjoyable to work with. His English is excellent, deadlines are met, and he takes real ownership of his work. I would recommend him without hesitation to anyone looking for a highly skilled and dependable developer.”

Portrait of Ryan Badger
Ryan Badger
CEO, Shoprocket
View original message ↗
Indesh Prinja, full-stack SaaS developer
About

An engineer who stays with the product.

I've spent most of my career on products where the hard part isn't writing code. It's understanding how orders, payments, permissions and workflows need to work together, and keeping that system reliable as the business grows.

I'm a full-stack engineer who takes ownership across backend architecture, APIs, frontend products and production systems. You work directly with me, not an agency handoff.

Laravel, PHP, JavaScript and AWS are how much of the work gets done. I'm also comfortable joining an established product team or taking something end to end on my own.

What I build

The systems businesses depend on.

SaaS platforms, commerce systems, APIs and modernization for products where backend, frontend and business workflows have to work together in production.

Technologies

Grouped by what they're used to build.

Backend & application architecture

Laravel · PHP · MySQL

Core backend framework across production SaaS and business applications.

See relevant work →

Modern frontend applications

JavaScript · React · TypeScript · Ionic · Livewire · Alpine.js

Storefronts, dashboards and interactive interfaces, including vanilla JavaScript embeds where the product demands it.

Systems that connect

REST APIs · Webhooks · Integrations · Authentication

Products talking to payment providers, external tools and the systems a business already runs.

See relevant work →

Cloud & production

AWS · Deployment · Background processing

Infrastructure, queued work and production debugging once software is live.

See relevant work →

Capabilities

Each links to proof: a case study, article or section on this site.

Also in the toolkit

Node.js · Next.js · Redis · Tailwind CSS

Used where the product needs them, not every project uses every tool.

A good fit if

You're building or evolving serious software, not looking for a brochure site or the cheapest hourly rate.

  • You have an existing SaaS or business application, or you're building one where backend complexity matters.
  • The product is getting harder to change and needs modernization, not necessarily a rewrite.
  • Your next feature crosses backend, frontend, APIs, data or integrations.
  • You want a long-term engineering partner and will work directly with the person doing the work.
Available for select engagements

Production SaaS · Growing commerce platforms · Existing applications that need modernization, new features or senior engineering ownership

Let's talk
Have a product worth evolving?

Let's talk about the problem.

A short note is enough, what your product does, what's not working, or what needs to ship next. I'll come straight to the engineering problem, not a sales pitch.