Process - How a project runs
Three phases, from first conversation to launch. Each one ends with something concrete you can review, so you always know where the project stands.
Discover
We start with your goals, your users, and your constraints: what success looks like, what already exists, and where the risks are.
That usually means a kickoff call, a look at your current site or product, and a short written summary of requirements, so we agree on scope before anything is built.
You leave this phase with a practical plan: prioritized features, a recommended stack, and a realistic timeline.
Included in this phase
- Kickoff call
- Requirements & scope
- Stack recommendation
- Timeline & milestones
- Optional prototype
What I'll ask you for
- Your goals and audience
- Existing designs, brand assets, or content
- Access to current hosting, domains, or code
- One decision-maker for feedback
Build
With the plan agreed, I build in short iterations — interface, application logic, APIs, and integrations — with demos on a staging link so you can click through what's done.
You get regular written updates, open questions raised early, and trade-offs explained in plain language.
Code reviews, testing on critical flows, and automated deployments are part of the work, not extras at the end.
Included in this phase
- UI implementation
- Backend & APIs
- Third-party integrations
- Staging demos
- Feedback rounds
Deliver
Launch is its own milestone: production setup, final QA, and a rollout plan so your product is fully usable on day one.
After launch I hand over documentation and access, walk your team through it, and can stay on for maintenance and improvements if you want ongoing help.
Included in this phase
- Testing & QA. Checks on critical flows, browsers, and devices before go-live.
- Infrastructure. Production hosting, domains, environment setup, and CI/CD so updates stay repeatable.
- Handover & support. Documentation, account access, and an optional support plan for follow-on work.
Working principles - Reliable delivery, modern tools
Sensible defaults, new tools when they genuinely help, and a focus on what your users will notice.
- Meticulous. Details matter when your website or app is how customers judge your business.
- Efficient. The most important paths ship first. I don't rebuild what already works.
- Adaptable. The stack follows your needs and budget, not a template.
- Honest. Risks, estimates, and trade-offs are raised early so decisions stay grounded.
- Long-term. Happy to stay on after launch for maintenance, improvements, and the next phase.
- AI-assisted. I use AI coding tools to work faster and build my own open-source Agent Skills, while every change stays reviewed and tested.
FAQ - Process questions
How discovery, build, and launch work when you hire me directly.
What happens in the Discover phase?
We clarify your goals, users, and constraints, review what already exists, and agree on a practical plan: prioritized features, a recommended stack, and a realistic timeline.
How does the build phase work day to day?
I work in short iterations with demos on a staging link and regular written updates, so you see progress and decisions as they happen.
What do I get at launch?
A live, production-ready product, documentation, and a walkthrough, plus the option of ongoing support.
How long does a project take?
It depends on scope. Discover produces a shared plan and timeline first, so estimates are based on real requirements, not guesswork.
Will I work with you directly?
Yes. You work with me on scope, priorities, and delivery from start to finish.
Who owns the code?
You do. Code, hosting, and accounts are handed over at launch.