How a project runs
Nine steps from inquiry to handover. For each one you know whose turn it is and what I’ll need from you. You’ll see the same thing in the portal for your own project.
Step 1: Inquiry received
meI read your inquiry and reply within 1 working day, with follow-up questions or a suggestion for a short call.
What I need from you
Answers to the follow-up questions.
Step 2: Brief
meyouWe write the brief together: what you want to achieve, how we’ll know it worked, and what is not part of the project.
What I need from you
Your goals, examples you like, and the name of the person who approves.
Step 3: Proposal
meI send a proposal with the scope, a fixed price and a date for each step.
What I need from you
Your acceptance of the proposal, or questions about it.
Step 4: Contract and deposit
youWe sign a contract with the same scope and the same rules you’re reading here.
What I need from you
Your signature and the deposit.
Step 5: Materials and access
youYou send me the materials and access. I can’t start without them, so this step has its own deadline.
What I need from you
Text, photos, your logo and access to your domain. For apps, your developer accounts for the App Store and Google Play. For AI, samples of your data.
Step 6: Design
meI prepare a design or a prototype and send a link to the test version.
What I need from you
Your feedback in one go within the agreed time, and your approval.
Step 7: Build
meI build. As I go, I add links to the test version in the portal and note what’s done.
What I need from you
Answers to the questions that come up during the build.
Step 8: Review and testing
youYou go through the test version. Whatever doesn’t match the brief, I fix.
What I need from you
Your testing and approval.
Step 9: Launch and handover
meI put it live and hand over the repository, access and documentation.
What I need from you
The final payment and your go-ahead for the launch.
After launch
Support
meFor 30 days after launch I fix bugs for free. After that it’s up to you whether you want the monthly care plan.
What I need from you
Bug reports and requests for changes.
Rules that apply to both sides
The same rules are in the contract and in the portal.
Open tasks decide whose turn it is
As long as you have an unfinished task or something is waiting for your approval, it’s your turn. Otherwise it’s mine. I never set it by hand.
Waiting for materials moves the deadline
When I’m waiting on you, the deadline moves by as many days as I wait. You pay nothing for that.
After seven days without a reply, I pause the project
The first reminder comes one day after the due date, the second three days after it. After seven days I pause the project, and we pick it up again as soon as you get in touch.
Silence during review means approval
If you don’t respond within the review period in the contract, I take that as your approval.
Nothing extra without approval
I start work outside the signed scope only after you approve its price and how far it moves the deadline.
See what it looks like
The example project is made up, but the screen is the same one you’ll see for your own.
Tell me what you need
A few sentences in your own words are enough. Within 1 working day I’ll come back with questions or suggest a short call.