Questions & Answers
Frequently asked questions
8 of 8 answers from Abdullah Rahman
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. Do you offer ongoing maintenance after launch?
✦ Featured Yes. Launch is the beginning, not the end: Care plan: fixed monthly retainer covering updates, dependency upgrades, monitoring and a guaranteed…
Yes. Launch is the beginning, not the end:
- Care plan: fixed monthly retainer covering updates, dependency upgrades, monitoring and a guaranteed response time for incidents.
- On-demand: small fixed-price fixes whenever you need them.
Every handoff includes documentation and a 30-day post-launch warranty on the work we shipped together, so defects found early are fixed free.
iii. How do you handle payments?
Simple, transparent and ethical: Fixed-price milestones agreed in writing before we start — you never pay an open-ended hourly meter. Typical split:…
Simple, transparent and ethical:
- Fixed-price milestones agreed in writing before we start — you never pay an open-ended hourly meter.
- Typical split: 40% on kickoff, 40% at mid-point demo, 20% on final handoff.
- Invoicing is straightforward: an agreed price for an agreed deliverable, with no interest-based (riba) invoicing, late-interest penalties or financing charges. Any late-fee arrangement is a fixed, pre-agreed amount — never a compounding percentage.
You receive an invoice per milestone with exactly what was delivered listed on it. No hidden fees, ever.
iv. Which technologies do you specialize in?
My core stack is TypeScript everywhere: Frontend: Astro, React, Svelte — light-by-default, server-rendered first Backend: Node/Bun, Hono,…
My core stack is TypeScript everywhere:
- Frontend: Astro, React, Svelte — light-by-default, server-rendered first
- Backend: Node/Bun, Hono, PostgreSQL/SQLite, edge functions
- Infra: Docker, CI/CD pipelines, observability (logs, metrics, traces)
- Performance: Core Web Vitals work, edge caching, bundle surgery
I pick boring, proven tools on purpose — the ones your team can still maintain in five years. If your stack differs, the discovery call is where we honestly decide whether I am the right fit.
v. Do you sign NDAs?
Yes — I sign your NDA before the discovery call if the project is sensitive, and I am happy to work under your MSA. By default I keep engagement…
Yes — I sign your NDA before the discovery call if the project is sensitive, and I am happy to work under your MSA.
By default I keep engagement details private anyway: I only publicise work you have explicitly approved as a case study, and repository access stays inside your organisation.
vi. Can you work with our existing team?
That is my favourite way to work. I embed into your rituals — your standup, your PR review flow, your issue tracker — and leave the codebase more…
That is my favourite way to work. I embed into your rituals — your standup, your PR review flow, your issue tracker — and leave the codebase more maintainable than I found it:
- PRs reviewed by your engineers, with knowledge-transfer comments
- Architecture decision records for anything non-obvious
- Pairing sessions on request, at no extra cost
The goal is that when I leave, your team does not need me.
vii. 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.
viii. How do we get started?
Three steps: 1. Send a message through the contact form with a paragraph about the project and your timeline. 2. Discovery call within a week — we…
Three steps:
- Send a message through the contact form with a paragraph about the project and your timeline.
- Discovery call within a week — we map the problem and I follow up with a written plan and fixed quote.
- Kickoff — milestone schedule, repo access, first invoice, and we ship.
I take on a limited number of projects at a time so each one gets full attention — if my plate is full I will tell you honestly and suggest a start date or a trusted colleague.