IProcess · seven steps
What happens after you message me.
commercial and communication · offer-specific checklists live on the offer pages
From first message to thirty days after launch: what happens, in what order, what you get at each step, and what I need from you.
How it goes
One idea, seven instances.
Every engagement runs the same way, whether it's a build, a review or a pentest — the only thing that changes is what I'm attacking in step five.
- 01
Step 1: You write to me
WhatsApp or email — whichever you'd actually use. Tell me what you're building, who'll use it, when you need it, and roughly what you can spend. Two lines is enough. I reply within one working day.
- 02
Step 2: A free 30-minute call
To understand what you're building and decide, both of us, whether I'm the right person. I'll tell you on this call if I'm not — if what you need is a marketing site, an app in a stack I don't work in, or a team of five.
- 03
Step 3: A written scope and a fixed price
Within two working days of the call. What's included, what isn't, the timeline, the price, the payment terms (40% to start, 30% mid-way, 30% at launch on a build). You can send it to a co-founder or a lawyer. Nothing starts until you've agreed it in writing.
- 04
Step 4: The build, in the open
You get a staging URL in the first week and it's updated as I work, so you're never waiting for a “reveal”. A short written update every week covers what's done, what's next, and anything I need from you. Client communication happens in Indian business hours; I'll tell you my hours on the first call.
- 05
Step 5: The attack
In the final week I run the pre-launch security review against what I built — or, on a Build + pentest engagement, a full penetration test in the final two weeks. You get the findings in writing. Anything that needs fixing is fixed before launch. On a standalone review or pentest, this is the whole engagement, and step 4 is me getting access rather than building.
- 06
Step 6: Launch
Deployed on your accounts — your Vercel, your Supabase, your domain — so you own it the day it goes live. A handover of how it's built and how to run it: written docs and a call.
- 07
Step 7: After
5 working days to review and accept. Then 30 days of bug fixes on anything within the agreed scope. New features and scope changes are quoted separately, in writing, the same way as the original.
What I need from you
The timeline depends on this more than on me.
Four things. None of them technical.
- 01Someone who can decideAnd give feedback within a few days.
- 02Access to the accounts the app will live onVercel, Supabase, the domain — created in your name, not mine.
- 03Test contentOr an honest “we don’t have any yet”.
- 04For a pentest or review: written authorisation and test accounts at each roleThere's a free rules-of-engagement template at amansploit.com.
IIStep one
Write to me.
What you're building, who'll use it, when you need it, roughly what you can spend.