HOW I WORK
rule one: read the manual. you are doing great.
The project starts with a conversation. We talk about what you're trying to achieve, the problem you're facing, what you already have, and what the project actually needs.
After understanding the project, I prepare the proposal. It defines the work, scope, expected outcome, timeline, and commercial terms.
If you agree with the proposal, I prepare the contract for the work. The project does not begin before the agreement is signed.
step zero: we talk. i ask annoying questions.
Once the contract is signed, the project officially begins.
I send the welcome information and collect everything required to begin properly: access, credentials, existing assets, documentation, requirements, references.
I turn everything we've discussed into a clear project blueprint. What will be built, how it will work, the structure, the important requirements, and the intended direction.
We review the blueprint together. You give feedback, questions, corrections, and final direction. The blueprint is finalized before development begins.
the paperwork phase. boring. load-bearing.
Once the direction is finalized, I start building. The work follows the agreed scope and contract.
You don't have to wonder what's happening. Regular progress updates and working demos come throughout the build, so you stay involved and small issues get caught while they're still small.
this is the part with demos. you will like this part.
The completed project gets reviewed against the agreed scope. Any final agreed adjustments are completed.
Final payment follows the terms established in the contract. Payment and delivery move together, exactly as agreed.
Once the project is complete and payment is received, I hand everything over: complete source code, project files, assets, documentation, credentials where applicable. Everything included in the agreed scope.
my favourite step. no shame.
— ovi, field manual ends. read it twice.