Freelancer Toolkit Pack
Proposals, client emails, project scoping, and invoicing templates. Look professional in half the time. More time doing the work, less time on the business of work.
One-time purchase. Instant download. No subscription.
Prompt Categories
30 prompts across 4 categories. Every stage of freelance business operations is covered.
Who This Is For
Sample Prompts from This Pack
Real prompts. Real outputs. See what you're buying.
Write a project proposal for [PROJECT TYPE] for [CLIENT NAME/TYPE]. Project details: [BRIEF DESCRIPTION]. My rate: [YOUR RATE]. Timeline: [ESTIMATED TIMELINE].
Structure:
1. Executive summary (2-3 sentences — what, why, outcome)
2. Understanding of the problem (show you listened)
3. Proposed approach (3-5 phases with deliverables)
4. Timeline with milestones
5. Investment (price + what's included)
6. Why me (2-3 relevant results, not a resume)
7. Next steps (clear, single CTA)
Tone: Professional but human. Confident without being arrogant. Short paragraphs. No jargon.
Executive Summary
I'll redesign your marketing website to increase conversion rates, with a focus on mobile experience and clear CTAs. Expected outcome: a site that turns visitors into leads instead of bouncing them.
Understanding Your Problem
Your current site gets traffic but doesn't convert. The mobile experience is clunky, CTAs are buried, and the messaging doesn't match what your customers actually care about...
Proposed Approach
Phase 1: Discovery & Audit (Week 1) — Review analytics, heatmaps, and competitor sites. Deliverable: Audit report with 5 quick wins...
[Continues through all 7 sections with specific, client-ready language...]
Write a professional email to a client who has requested work outside the original project scope. Context: [DESCRIBE THE EXTRA REQUEST]. Original scope: [WHAT WAS AGREED]. My relationship with this client: [NEW/ONGOING/VIP].
The email should:
- Acknowledge their request positively (don't make them feel bad for asking)
- Clearly explain what was in the original scope vs. what's being requested
- Offer two options: add it as a paid add-on with a specific price, or save it for a Phase 2
- Keep the tone warm but firm — no apologizing for having boundaries
- End with a clear next step
Subject: Quick note on the new feature request
Hi Sarah,
Great idea on adding the customer dashboard — I can see why that would be valuable for your team.
Just want to flag that this falls outside what we scoped in our original agreement (which covered the marketing site redesign and landing pages). The dashboard would be a separate build with its own design, data integration, and testing.
Two options that could work:
Option A: I add it to this project as an add-on. Estimate: $2,400, adds ~1 week to the timeline.
Option B: We finish the current project first, then kick off the dashboard as Phase 2. I'd scope it properly so you get an accurate quote.
Either way works for me. Which sounds better to you?