How it works
From brief to
deployed.
No surprises. No mystery timelines. Here's exactly how I work with clients — from the first message to handoff.
Project process steps
Discovery call
We start with a 30-minute video call. I want to understand what you're building, why, and what success looks like to you. I'll ask about your users, your current stack, and anything that's already been decided. You don't need a full spec — just an idea and some context.
Written scope & estimate
After the call I'll write up what I understood: the scope, the approach, the tech stack I'd use, a realistic timeline, and a fixed or capped estimate. This document is detailed enough to act as a lightweight spec. You'll have it within 48 hours.
Kickoff & environment setup
Once agreed, I set up the repo, CI/CD pipeline, staging environment, and any shared tooling we'll use (Notion, Linear, Slack — whatever fits). I send you access to everything from day one. No black boxes.
Build — weekly milestones
I work in week-long cycles. Every Friday you get an update: what was built, what's next, and any decisions that need your input. If anything blocks me, I tell you the same day — not two weeks later when it's a crisis. Staging is always up to date.
Review & iterate
When a major piece is done, we do a structured review call. I walk through the feature, explain the decisions, and collect feedback. I build in time for one meaningful revision round per feature. Out-of-scope additions are scoped separately, never silently added to the bill.
QA, launch & handoff
Before go-live: full QA on all target devices, accessibility audit, performance check, and a run through your definition of done. On launch day I'm available for anything that comes up. After launch I write handoff documentation so you're never dependent on me to keep the lights on.
How we collaborate
Tools & workflow
I adapt to whatever you're using. These are my defaults — happy to use yours.
Project management
- ▸Linear
- ▸Notion
- ▸Trello
Communication
- ▸Slack
Design handoff
- ▸Figma
- ▸Zeplin
Version control
- ▸GitHub
- ▸GitLab
Deployments
- ▸Vercel
- ▸AWS
- ▸Netlify
Payments
- ▸Wise
- ▸PayPal
- ▸Bank transfer
Documentation
- ▸Notion
- ▸Readme.io
- ▸Loom
Testing
- ▸Playwright
- ▸Jest
- ▸Cypress
Common questions
FAQ
- Do you work with clients in different time zones?
- Yes — most of my clients are in Europe, the US, and Southeast Asia. I do async work during my day (IST) and schedule overlap calls at times that work for both of us.
- How do you handle requirements that change mid-project?
- I expect them. Small changes within scope — I absorb them. Meaningful scope additions get scoped separately with a written addendum. You'll always know what you're paying for before it's built.
- Do you work with non-technical founders?
- Absolutely. Part of my job is translating technical decisions into plain language so you can make informed calls. You don't need to understand the code — you need to understand the trade-offs. That's on me.
- Can I see your code before hiring you?
- Yes — my public GitHub is linked in the footer. I'm also happy to do a paid trial task (typically a small feature or bug fix) if that helps you assess the working relationship.
- What's your payment structure?
- For projects: 40% upfront, 40% at midpoint milestone, 20% on launch. For retainers: monthly in advance. I invoice via Wise or PayPal, and accept bank transfers.
- What happens after the project ends?
- You get full handoff docs, a Loom walkthrough, and 30 days of post-launch support for bugs (not new features). After that, I offer retainer arrangements — or hand you off to your team, no strings attached.
Ready to kick things off?
Fill in the project scoping form. I'll come back with a written scope and estimate within 48 hours.
Scope My Project →