Templates — Copy & Paste

Hi {Client},

I read your post about {specific problem}. I've shipped 3 similar fixes (Stripe webhook race condition, Postgres deadlock under load).

My plan:
1. Reproduce locally with your repo + sample payload
2. Patch + add regression test
3. Deliver PR with changelog

I work async (GMT+7) and reply within 4 hours during your business day. 90-second Loom walkthrough on delivery.

Estimated: {X} hours / {Y} milestone.

— {Your name}

Hi {Client},

Your stack ({Next.js + Supabase + Stripe}) overlaps 90% with my last 4 projects.

I'd like to suggest splitting this into 3 milestones:
- M1 (week 1): {discovery + auth flow}
- M2 (week 2-3): {core features}
- M3 (week 4): {payments + deploy}

Each milestone ships a working demo URL — you only release escrow when you've clicked through it.

I'm GMT+7, async-first, async-default. Available for 1 weekly 30-min call (with captions).

Portfolio: {link} · GitHub: {link}

— {Your name}

Hi! Thanks for the brief.

I can deliver this gig with these adjustments:
- Scope: {bullet exact deliverables}
- Timeline: {X} days
- Revisions: 2 included
- Price: {Y} (covers {what's in})

What's NOT included: {scope creep guard — list 2-3 things}

Confirm and I'll start within 6 hours.

Hey {Client}, excited to start!

To kick off cleanly, I need:
1. Repo access (GitHub username: {x})
2. Staging/test credentials
3. Slack/Discord channel (or we use Upwork chat)

Quick note on my workflow:
- I push WIP to a feature branch daily
- Every Friday I send a 90s Loom recap
- For urgent stuff, ping me — I'm online 9am–6pm GMT+7

Starting M1 today, expect first commit within 24h.

Happy to jump on a call! Quick favor — I want to come prepared so we use the time well.

Could you record a 5-min Loom walking through the problem? I'll watch tonight and reply with a written plan + 2-3 clarifying questions. If we still need a call after that, I'll book a 20-min slot.

This usually saves both of us 30+ minutes. Loom: https://loom.com (free).

Quick bump — wanted to make sure my proposal didn't get buried.

If you're still evaluating, no rush. If priorities shifted, totally understand — just let me know so I don't ping you again.

Either way, good luck with {project}!

Weekly update — Week {N}

Done this week:
- {bullet 1}
- {bullet 2}

Next week:
- {bullet 1}
- {bullet 2}

Blockers / need from you:
- {decision needed by Tue}

Demo: {URL or Loom link}

Great idea! That feature would add {meaningful value}.

It's outside our current scope (M2: {original}). Two options:

A) Add it as M4 — I estimate {X hours / $Y}. I can start after current milestone.
B) Park it for v2 and stay focused on the launch.

Which works better for you?

I hear the urgency. To hit {new date}, here's what I can flex:

- Cut: {feature X — saves 2 days}
- Defer: {feature Y to v1.1}
- Add: a second pair of hands ({+$Z})

Keeping full scope at original quality needs the original timeline. Which trade-off works?

Before we go further, I want to make sure we're aligned.

Could you confirm:
1. Definition of done = {your understanding}
2. Acceptance criteria = {checklist}
3. If we hit issue X, fallback is {Y}

I'd rather over-clarify now than rebuild later. Reply "confirmed" and I'll proceed with M2.

Happy to keep things simple — let's keep all project comms here on {Upwork/Fiverr}.

Platform chat = automatic dispute log + payment protection for both of us. Once we wrap this milestone, I'm open to discussing direct work for follow-ups.

It's been great working on {project}. Marking the final milestone complete now.

If you're happy with the work, a 5-star review with a quick line about {specific thing — speed / async style / quality} would mean a lot. It directly affects my visibility on {platform}.

If anything's NOT 5-star, please tell me first — I'd rather fix it than have you compromise the rating.