Supplement — A Note Before We Begin
Ten short articles. So we both know what to expect — clarity, respect, focus on the work.
On discovery & scoping.
If you already have a clear brief with well-defined goals and requirements, send it over. We'll review it together and I'll provide a quote and timeline.
If your idea is still taking shape, we start with a paid discovery session — a focused, fixed-price engagement to produce a clear written specification and roadmap. The discovery fee is credited back to the project if we move forward.
A free 15-minute intro call is always available before committing to anything.
On milestones, not hours.
I don't bill by the hour. I deliver finished, high-quality work broken into well-defined milestones with clear deliverables and timelines.
Every project begins with a written scope document — what's included, what's out of scope, what each phase produces.
On scope management.
Once we agree on scope, I treat it as our guiding agreement. New ideas during development are normal — they'll be quoted separately so they don't disrupt the original timeline and budget.
On communication & decisions.
Major decisions affecting scope, timeline, or budget will be confirmed in writing. This isn't bureaucracy — it's making sure we both remember the same thing weeks or months later.
On payment structure.
50%
40%
10%
Work is delivered progressively with staging environments and demo links. Before final delivery, you'll have a defined testing window with a clear checklist.
On ownership & handover.
On full payment, you receive complete ownership — source code, credentials, documentation, assets. Until then, full access to staging environments for review.
On pace & responsiveness.
If I'm blocked or going to miss a deadline, you hear from me proactively. I ask the same in return — extended silence after delivery for review will adjust the timeline on a day-for-day basis.
On collaboration style.
I see myself as a partner, not a pair of hands. I'll share honest opinions and respectfully push back if a decision could hurt the outcome. Once we agree on a direction, I commit fully to executing it well.
On what i won't do.
I'd rather spend my energy building great products with you than chasing payments or renegotiating scope.
On why i work this way.
The projects that succeed share the same ingredients: clear scope, written agreements, structured payments, mutual respect. This document exists so we can focus on creating something meaningful instead of dealing with preventable misunderstandings.
If anything here doesn't feel right, tell me upfront. Once we start, this is how I work — with clarity, respect, and a strong focus on quality.