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 · You write to me
02 · A free 15-minute scoping call
03 · A written scope and a fixed price
04 · The build, in the open
05 · The attack
06 · Launch
07 · After
step 01 of 07You 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.
process
Boring in the ways that matter.
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.
How an engagement runs
A free 15-minute scoping call, then a written scope and a fixed price within two working days. Then the work, findings ranked by severity, and one retest of the fixes within 30 days.
Delivery
One engineer in Pune, IST. Replies within one working day. Invoiced in USD or INR, exclusive of taxes: builds 40 / 30 / 30, reviews and pentests at the start. No hourly billing.
what I need from you
The timeline depends on this more than on me.
Four things. None of them technical.
- 01
Someone who can decide
And give feedback within a few days.
- 02
Two hosting accounts in your name
I'll tell you which and walk you through it; it takes ten minutes. The app lives on them, not on mine.
- 03
Real content, or a plain “we don't have any yet”
Either is fine; guessing at it is what costs time.
- 04
For a review or pentest: written permission and a login for each kind of user
There's a free permission template at amansploit.com.
step one
Write to me.
What you're building, who'll use it, when you need it, roughly what you can spend.