How a project runs
The same three steps whether your site is in Webflow or custom-built.
Agree a monthly block
A set amount of time each month, sized to what you actually have coming. No scoping document for every small change.
Send work as it comes up
One running list instead of scattered messages. We prioritise it together, so the most useful thing is always next.
Reviewed, then live
Work goes up for you to look at before it ships, and gets published once you are happy with it.
What usually goes wrong
Small changes sit around for weeks.
A landing page for a launch, a pricing tweak, a new case study. None of it is big enough to be a project, which is exactly why it never gets done. A retainer is the slot those live in.
There is not enough work to hire someone.
Most early-stage teams need a few days of design and development a month, not a full-time salary. This is the shape that fits that.
Every request turns into a new quote.
Agreeing the time up front means the small things get picked up as they come, rather than each one needing to be priced and scheduled from scratch.
Whoever built it is no longer around.
Picking up someone else's site is slow, and it shows in the bill. Staying with the person who built yours means none of that time is spent relearning it.
One person, both jobs
Design and development sit in the same retainer, so a change does not need handing between two people to get done.
- The same person who built it does the work
- Design and development in one arrangement
- Webflow and custom-built sites both covered
- Time agreed up front, so nothing needs re-quoting