A written scope
What is in and what is out, and which roles, screens and languages are needed.
Step 2 / 5 · When you bring the brief
Proposal
Before any code is written we agree what will be built, by when, and for what price. A clear proposal means no surprises for either side.
- Scope
- Timeline
- Price
What happens
In this step.
A realistic timeline
Milestones you can plan around, with regular check-ins built in.
A price agreed up front
Clear before work begins, so there are no surprises later.
Talk it through
Where it matters, in person. Rannikon moved forward because of face-to-face meetings, not only emails.
Project references
See it in real projects.
Work where this step actually happened.
Examples
What that looks like.
Example 1
Proposing a whole system
For Rannikon I proposed a complete digital workforce management system to the farm manager, who approved the project.
RannikonExample 2
Face to face where it counts
Meetings with the farm manager and the payroll team moved the project forward more than messages could.
RannikonExample 3
Starting small on purpose
Rannikon began as a basic timesheet calculator. Later features were added on request rather than promised up front.
RannikonKeep exploring
The rest of the process.
Previous step
Discovery
A quick call or written brief to understand the problem, the audience, and what success looks like.
Learn moreNext step
Build
Custom-coded, with regular check-ins so there are no surprises at handoff.
Learn moreThe other way to start
Spot the problem
Something slow, manual, or error-prone that people live with every day.
Learn moreLet’s talk about your project.
Brand partnerships, freelance projects, or just to talk shop.