Questions & Answers
Frequently asked questions
2 of 8 answers from Abdullah Rahman · marked “process”
i. What is your typical project timeline?
✦ Featured Most projects fall into one of three shapes: Audit or small feature: 1–2 weeks MVP / full build: 6–10 weeks with weekly demos Longer engagements:…
Most projects fall into one of three shapes:
- Audit or small feature: 1–2 weeks
- MVP / full build: 6–10 weeks with weekly demos
- Longer engagements: 3-month+ roadmaps, reviewed monthly
After the discovery call you get a written plan with milestone dates before any code is written. I protect the timeline by shipping behind flags and keeping one weekly demo — you see real progress every Friday, not a big reveal at the end.
ii. What does your discovery process look like?
Discovery is a focused 5 working days: 1. Kickoff call (60 min) — goals, constraints, success metrics. 2. Async review — I read your…
Discovery is a focused 5 working days:
- Kickoff call (60 min) — goals, constraints, success metrics.
- Async review — I read your code/docs/analytics and prepare questions.
- Findings + plan — a written document: current state, risks, recommended architecture, milestone plan and a fixed quote.
- Decision call (30 min) — we walk the plan together and you decide with no pressure.
The discovery deliverable is yours to keep and shop around, even if you never hire me for the build.