· 4 min read
How I ship a freelance project in 4 weeks
The exact briefing-to-launch process I use on every project — scope, weekly demos, fixed quote and 30 days of free support.
PM
Pol Mendieta · @poldescomm
Freelance full-stack engineer · Barcelona
A freelance project that ships on time isn’t an accident — it’s a process. Here’s mine, end to end.
Week 0 — Briefing
A 30-minute discovery call. I drop my checklist on the screen and we go through it:
- What’s the goal? (signups, sales, MRR, daily active users)
- What’s the success metric? (specific number + deadline)
- What’s the scope, what’s explicitly out of scope?
- What’s the budget range?
I send a fixed quote within 48h. No revisions, no surprise add-ons.
Week 1–3 — Development
- Code on GitHub from day one (private repo, you have access).
- Weekly demo on Loom, ~10 minutes, with the same metrics you cared about in week 0.
- A shared task board you can comment on.
If something is going to slip I tell you on day 2 of the slip — not the day before launch.
Week 4 — Delivery
- QA on staging.
- Lighthouse audit (Performance, SEO, Accessibility, Best Practices).
- Full deploy to production.
- Documentation + a Loom walk-through of every admin tool.
After launch — 30 days of free support
Bug fixes, copy tweaks, small features. Anything bigger goes on a monthly retainer if you want it.
That’s it. Same flow every time. Predictable, transparent, quote-locked.
#freelance#process