~/ faq
faq

Questions, answered.

The things people usually ask before we start. Don't see yours? Just send it over.

What kinds of projects do you take on?
Just about anything that runs on code — web apps, business websites, custom internal tools, automations, integrations, APIs, and bug fixes. Genuinely, no job too big or too small. If it's not something I can do well, I'll tell you and point you in a better direction.
How much will my project cost?
It depends on scope, but you'll always know the number before we start. I work hourly, fixed-price per project, or on a monthly retainer — see the pricing page. Small fixes can be a flat fee or a single hour.
How long will it take?
Small tasks can be days; a full product is usually weeks. After we scope it, you get a realistic timeline up front — and honest updates if anything shifts.
Do I own the code?
100%. Everything lives in your repository and on your accounts, documented so any developer can pick it up later. No lock-in, ever.
How do we communicate?
Email by default, plus whatever channel you prefer (Slack, WhatsApp, calls). You get regular plain-English updates and clickable previews — no wondering what's happening.
I already have code or another developer — can you still help?
Absolutely. I regularly join existing teams, take over half-finished projects, and audit or fix inherited code. I'll get up to speed on what's there before changing anything.
Can you maintain the project after launch?
Yes — software is never really "finished." I offer ongoing maintenance and improvements, either ad-hoc or on a monthly retainer.
What do you need from me to get started?
A description of the problem in plain words, any examples or references, and a rough sense of timeline and budget. That's enough for me to come back with a plan. Start here →

Still have a question?

Ask away — I'll get back to you within one business day.

$ start a project