01 — Services
Ways we can work together.
Fixed-scope builds, retainers or embedded contracting — pick the shape, the standard of work stays the same.
E-commerce product build
A storefront that actually converts: catalogue, cart, checkout with Stripe, order management and an admin your team can run without a developer.
- Next.js storefront with ISR and edge caching
- Stripe payments (incl. authorize/capture flows)
- Order lifecycle & fulfilment tooling
- Custom admin panel
- Analytics & SEO foundations
SaaS MVP build
From validated idea to a launched product: auth, billing, the core workflow, and the boring-but-critical production plumbing.
- Full-stack build (Next.js / Node.js / MongoDB)
- Auth, roles & permissions
- Subscription billing
- Background jobs & email
- Deploy pipeline & monitoring
Rescue & performance work
Inherit a codebase that's slow, fragile or unshippable? I find the bottlenecks, fix the architecture and leave the team faster than I found it.
- Performance audit with numbers, not vibes
- API latency & database optimisation
- Refactors that land incrementally
- Documentation & handover
Ongoing retainer
A fixed monthly block of senior full-stack capacity for teams that need features shipped without hiring full-time.
- Guaranteed weekly hours
- Feature development & code review
- Direct async access (Slack/email)
- Monthly progress summary
02 — How an engagement runs
How an engagement runs
01
Scope call
A 20-minute call to understand the product, constraints and what done looks like.
02
Written proposal
Scope, milestones, timeline and price in writing — no surprises later.
03
Build in increments
Weekly demos and shippable slices from the first week, in your repo.
04
Launch & handover
Deployment, monitoring, docs, and a handover your team can run with.
03 — Ways to work together
Ways to work together
Fixed-scope project
Agreed scope, price and delivery date. Best when the outcome is well defined.
Best for: MVPs, storefront builds, migrations
Retainer
A monthly block of hours for continuous product work with flexible priorities.
Best for: Post-launch iteration, growing products
Embedded contractor
Overflow & async contribution I pick up scoped tickets or features in your repo on a fixed weekly cadence, async-first — code review, PRs, and a written handoff. Best for: Teams that need a capacity boost without adding headcount
Best for: Teams needing senior capacity now
04 — Timezones & overlap
Timezones & overlap
I work from India (IST) and keep deliberate overlap with client timezones:
- US East: 3–4 hours of overlap every working day (your morning, my evening)
- UK / EU: most of your working day overlaps naturally
- Calls: scheduled in your timezone; everything else is async with same-day responses
Agencies: overflow builds and short-timeline rescues, white-labelled — your client, my code, your brand.
05 — Common questions
Common questions
How do timezones work if you're in India?
Who owns the code?
Do you work with agencies?
What stack do you work in?
How do payments work?
// contact
Want to build something together?
Tell me what you're working on — I read every message myself and reply within a day.