FAQ
Frequently asked questions about my services, process, and workflow.
General
Which stacks do you commit to? +
Laravel, Angular, WordPress, and modern TypeScript frontends. If a project genuinely needs a different stack I'll say so up front and recommend someone better suited.
Where are you based, and which time zones do you work in? +
I work remotely from West Africa (WAT, UTC+1). I overlap comfortably with Europe and the Americas East Coast, and I'm happy to schedule sync time outside those windows when a project needs it.
What does a typical engagement look like? +
Week one is discovery: a written brief, an architecture sketch, and a milestone schedule. From there I ship in weekly increments with a Friday demo and a written changelog. You can cancel after any milestone, no questions asked.
Do you work with existing codebases? +
Often. About a third of my engagements are inherited codebases that need rescue work, a focused refactor, or a fresh delivery push. I'll always start with a written code review before proposing changes.
Do you offer ongoing maintenance? +
Yes, capped hours monthly retainers for clients I've shipped with. I don't take on maintenance for systems I haven't audited and built, because it usually ends badly for both sides.
Pricing
How do you handle pricing? +
Pricing depends on scope and complexity. I provide custom quotes after discussion.
How are projects priced? +
Fixed-scope engagements are quoted as a single milestone-based price after the discovery call. Ongoing work and architecture reviews are billed on a weekly retainer. I don't bill hourly — it incentivises the wrong things.
Services
Can you maintain existing systems? +
Yes, I can audit, optimize, and maintain legacy applications.