<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: OpsPack</title>
    <description>The latest articles on DEV Community by OpsPack (@opspack).</description>
    <link>https://dev.to/opspack</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4213346%2F22a013f5-040a-4651-837e-b3cc7ed44e4c.png</url>
      <title>DEV Community: OpsPack</title>
      <link>https://dev.to/opspack</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/opspack"/>
    <language>en</language>
    <item>
      <title>Client ghosting you after the invoice? A 4-step chase sequence</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:59:42 +0000</pubDate>
      <link>https://dev.to/opspack/client-ghosting-you-after-the-invoice-a-4-step-chase-sequence-24gh</link>
      <guid>https://dev.to/opspack/client-ghosting-you-after-the-invoice-a-4-step-chase-sequence-24gh</guid>
      <description>&lt;p&gt;Getting ghosted by a client after you send the invoice is common, and it is usually fixable with a short sequence instead of an angry email.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 4-step sequence
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Day 1 (due date):&lt;/strong&gt; Friendly nudge. One line with invoice number, amount, and payment link.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 7:&lt;/strong&gt; Ask if anything blocked payment (PO, wrong contact, approval). Offer to resend.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 14:&lt;/strong&gt; State the late-fee clause from your contract and the new total.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 21:&lt;/strong&gt; Final notice with a firm date, then pause work until paid.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Rules that help
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Keep every message to 3-4 sentences.&lt;/li&gt;
&lt;li&gt;Always include the payment link and the invoice PDF.&lt;/li&gt;
&lt;li&gt;Move to phone only after step 3, and confirm the call in writing.&lt;/li&gt;
&lt;li&gt;Stop work in writing, calmly, before step 4 if the contract allows.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Free template
&lt;/h2&gt;

&lt;p&gt;I put the exact wording for each step in a free late-payment email template: &lt;a href="https://opspack.vercel.app/late-payment-email-template" rel="noopener noreferrer"&gt;https://opspack.vercel.app/late-payment-email-template&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Full payment-terms and chase kits: &lt;a href="https://opspack.vercel.app" rel="noopener noreferrer"&gt;https://opspack.vercel.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>productivity</category>
      <category>business</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How to write a freelance proposal that gets a yes: 6 sections</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Wed, 18 Nov 2026 15:02:31 +0000</pubDate>
      <link>https://dev.to/opspack/how-to-write-a-freelance-proposal-that-gets-a-yes-6-sections-2dcp</link>
      <guid>https://dev.to/opspack/how-to-write-a-freelance-proposal-that-gets-a-yes-6-sections-2dcp</guid>
      <description>&lt;p&gt;If you want a head start, the &lt;a href="https://opspack.vercel.app/kits/freelance-proposal-template" rel="noopener noreferrer"&gt;Freelance Proposal Template (with a worked example)&lt;/a&gt; has all six sections below pre-filled. There is also a free set of scripts at &lt;a href="https://opspack.vercel.app/free" rel="noopener noreferrer"&gt;opspack.vercel.app/free&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Most proposals lose because they are long, vague, or about the freelancer. A client skims for three answers: do you understand my problem, what will I get, and what will it cost. Six short sections cover that.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The problem, in their words
&lt;/h2&gt;

&lt;p&gt;Open with two or three sentences restating what the client told you and why it matters to them. If they could copy it into an email to their boss, you got it right.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The outcome
&lt;/h2&gt;

&lt;p&gt;Describe what "done" looks like as a result, not a task list. "A five-page site that takes bookings" beats "web design services."&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Scope: what's in and what's out
&lt;/h2&gt;

&lt;p&gt;List deliverables, the number of revision rounds, and what is explicitly not included. This one section prevents most scope creep later.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Timeline
&lt;/h2&gt;

&lt;p&gt;Give milestones with dates, and say what you need from the client by when (content, feedback, access). Delays on their side should move your dates.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Price and payment terms
&lt;/h2&gt;

&lt;p&gt;Show a fixed price or a clear range. State the deposit (30-50% is common), when the balance is due, and the late fee. Offer two or three tiers if it fits; people often pick the middle one.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Next step
&lt;/h2&gt;

&lt;p&gt;End with one action: "Reply 'approved' and pay the deposit link, and I'll start Monday." Add an expiry date, such as 14 days, so the quote doesn't sit forever.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checks before you send
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Keep it to two pages or fewer.&lt;/li&gt;
&lt;li&gt;Use the client's name and vocabulary throughout.&lt;/li&gt;
&lt;li&gt;Send it as a PDF or a link, and follow up in 3 days if you hear nothing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write the six sections once, save them as a template, and tailor only sections 1 and 2 per client. That is about 20 minutes per proposal instead of two hours.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>The late-invoice email sequence I use (and when to send each one)</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Tue, 17 Nov 2026 15:03:22 +0000</pubDate>
      <link>https://dev.to/opspack/the-late-invoice-email-sequence-i-use-and-when-to-send-each-one-4agc</link>
      <guid>https://dev.to/opspack/the-late-invoice-email-sequence-i-use-and-when-to-send-each-one-4agc</guid>
      <description>&lt;p&gt;Chasing a late invoice feels awkward, so most freelancers wait too long and then send one angry email. A short, boring sequence works better and keeps the relationship intact.&lt;/p&gt;

&lt;p&gt;Here is the cadence I use, with the gist of each message.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before the due date: the heads-up (3 days out)
&lt;/h2&gt;

&lt;p&gt;Friendly and brief: "Invoice #[N] for $[amount] is due on [date]. Here's the payment link in case it's useful."&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 1 overdue: the neutral nudge
&lt;/h2&gt;

&lt;p&gt;No blame. "I don't see payment for #[N] yet. Could you confirm it's scheduled?" Most late invoices are simply forgotten.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 7: the specific ask
&lt;/h2&gt;

&lt;p&gt;Restate the amount, the due date and the link. Ask for a payment date: "Can you let me know when I should expect it?"&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 14: the terms reminder
&lt;/h2&gt;

&lt;p&gt;Point to the payment terms in your agreement and mention the late fee (for example 1.5% per month) will apply from [date].&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 21: the pause notice
&lt;/h2&gt;

&lt;p&gt;Calm and factual: work on the next phase pauses until the balance is settled. Offer a call if there is a problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 30: the final notice
&lt;/h2&gt;

&lt;p&gt;State the total including fees and a hard date before you escalate to collections or small claims. Keep it short.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rules that keep this from backfiring
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Always include the invoice number, amount and a payment link.&lt;/li&gt;
&lt;li&gt;Send from your normal email, in the original thread.&lt;/li&gt;
&lt;li&gt;Log every send so you can show a timeline later.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you'd rather paste than write, I put the full sequence into a ready-made set: &lt;a href="https://opspack.vercel.app/kits/late-invoice-email-templates" rel="noopener noreferrer"&gt;Late Invoice Email Templates&lt;/a&gt;. There is also a free &lt;a href="https://opspack.vercel.app/kits/invoice-aging-tracker" rel="noopener noreferrer"&gt;invoice aging tracker&lt;/a&gt; layout.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>business</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Everything I put in a freelance services agreement, in plain English</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Mon, 16 Nov 2026 15:08:38 +0000</pubDate>
      <link>https://dev.to/opspack/everything-i-put-in-a-freelance-services-agreement-in-plain-english-4n9p</link>
      <guid>https://dev.to/opspack/everything-i-put-in-a-freelance-services-agreement-in-plain-english-4n9p</guid>
      <description>&lt;p&gt;Most freelance disputes aren't about quality. They're about something nobody wrote down. A short services agreement fixes that, and it doesn't need to read like a legal textbook.&lt;/p&gt;

&lt;p&gt;Here is what I put in every one, in plain English.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Who and what
&lt;/h2&gt;

&lt;p&gt;Both parties' business names, and a one-paragraph description of the work. If you can't describe it in a paragraph, scope it smaller.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Deliverables and exclusions
&lt;/h2&gt;

&lt;p&gt;List what the client gets. Then list what they don't (extra rounds, source files, rush work). Exclusions prevent most scope creep.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Timeline and client responsibilities
&lt;/h2&gt;

&lt;p&gt;Dates for your deliverables, and dates for the client's feedback, content and approvals. If they go quiet, your deadline moves.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Fees, deposit and payment terms
&lt;/h2&gt;

&lt;p&gt;Total price, deposit (I use 30-50% upfront), due dates, accepted payment methods, and a late fee (for example 1.5% per month).&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Revisions and change orders
&lt;/h2&gt;

&lt;p&gt;Say how many revision rounds are included. Anything beyond that is a written change order with a price, approved before work starts.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Ownership
&lt;/h2&gt;

&lt;p&gt;Usually: you keep the rights until the final invoice is paid, then the client owns the agreed deliverables. Add a clause letting you show the work in your portfolio.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Confidentiality, termination, liability
&lt;/h2&gt;

&lt;p&gt;A mutual confidentiality line, a notice period for ending the project (and what's owed for work done), and a cap on liability at the fees paid.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Signatures
&lt;/h2&gt;

&lt;p&gt;An e-signature is fine. Keep a dated copy.&lt;/p&gt;

&lt;p&gt;This isn't legal advice. Have a lawyer review anything high-stakes.&lt;/p&gt;

&lt;p&gt;If you'd rather fill in blanks than write from scratch, I put mine into a ready-made layout: &lt;a href="https://opspack.vercel.app/kits/freelance-services-agreement" rel="noopener noreferrer"&gt;Freelance Services Agreement&lt;/a&gt; ($9). There's also a free deposit-and-payment-terms page at &lt;a href="https://opspack.vercel.app/deposit" rel="noopener noreferrer"&gt;opspack.vercel.app/deposit&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>beginners</category>
      <category>business</category>
    </item>
    <item>
      <title>STAR story bank: prep 8 interview stories once, reuse them everywhere</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Fri, 13 Nov 2026 15:11:03 +0000</pubDate>
      <link>https://dev.to/opspack/star-story-bank-prep-8-interview-stories-once-reuse-them-everywhere-4omc</link>
      <guid>https://dev.to/opspack/star-story-bank-prep-8-interview-stories-once-reuse-them-everywhere-4omc</guid>
      <description>&lt;p&gt;Most behavioral interviews ask the same dozen questions in different clothes. "Tell me about a conflict." "Tell me about a failure." "Tell me about a tight deadline." Yet most of us prep by inventing a fresh answer on the spot.&lt;/p&gt;

&lt;p&gt;A better approach: build a small bank of stories once, then reuse them for every interview.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Pick 8 real stories, not 30 questions
&lt;/h2&gt;

&lt;p&gt;Aim for variety: a project you led, a mistake you owned, a disagreement, a deadline crunch, something you taught yourself, a time you influenced without authority, a customer or stakeholder save, and a result you're proud of. Eight covers nearly everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Write each one in STAR form
&lt;/h2&gt;

&lt;p&gt;Situation (1–2 sentences), Task (what you were responsible for), Action (what &lt;em&gt;you&lt;/em&gt; did, not the team), Result (a number if you have one). Keep Action the longest part.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Add a one-line headline and a metric
&lt;/h2&gt;

&lt;p&gt;"Cut onboarding from 3 weeks to 9 days." A headline is what you'll actually remember under pressure, and the metric makes it stick with the interviewer.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Tag each story with the questions it can answer
&lt;/h2&gt;

&lt;p&gt;One story usually fits 3–5 prompts: leadership, conflict, ambiguity, failure, ownership. Make a small table: story on the left, tags on the right. Before an interview, scan the table and pick the best fit for the role.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Rehearse out loud, 90 seconds each
&lt;/h2&gt;

&lt;p&gt;Written answers sound different from spoken ones. Time yourself. If a story runs past two minutes, trim the Situation.&lt;/p&gt;

&lt;p&gt;I keep mine in a ready-made layout so I'm filling in blanks rather than designing a doc: &lt;a href="https://opspack.vercel.app/kits/star-interview-story-bank" rel="noopener noreferrer"&gt;STAR Interview Story Bank&lt;/a&gt; ($7). There's also a free starter kit at &lt;a href="https://opspack.vercel.app/free" rel="noopener noreferrer"&gt;opspack.vercel.app/free&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>career</category>
      <category>interview</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>"While you're here…": a change-order rule for handypersons and home-service contractors</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Thu, 12 Nov 2026 15:17:45 +0000</pubDate>
      <link>https://dev.to/opspack/while-youre-here-a-change-order-rule-for-handypersons-and-home-service-contractors-3hf2</link>
      <guid>https://dev.to/opspack/while-youre-here-a-change-order-rule-for-handypersons-and-home-service-contractors-3hf2</guid>
      <description>&lt;p&gt;Every contractor knows the sentence: "While you're here, could you also…?" Said nicely, it's a bigger job. Left unwritten, it's free work.&lt;/p&gt;

&lt;p&gt;Here's a simple rule that keeps the relationship friendly and the margin intact.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Say yes to the work, not to the price
&lt;/h2&gt;

&lt;p&gt;"Happy to — let me quote that add-on and send it over before I start." You haven't refused anything, and you've moved the conversation to paper.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Use a one-paragraph change order
&lt;/h2&gt;

&lt;p&gt;Write down four things: what's being added, the price, how much it moves the finish date, and a line for the client to reply "approved." A text or email reply counts, as long as it's in writing.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Separate "included" from "extra" up front
&lt;/h2&gt;

&lt;p&gt;In the original scope, list what's included and add one sentence: "Anything not listed is quoted separately as a change order." Clients rarely argue with a rule they read on day one.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Get paid for the change before the next phase starts
&lt;/h2&gt;

&lt;p&gt;Add-ons billed at the end are the ones that get disputed. Bill them when approved, or fold them into the next milestone invoice.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep the templates ready
&lt;/h2&gt;

&lt;p&gt;I keep the change-order wording, scope checklist, and late-payment language in one kit so I'm not rewriting it on a tailgate. The contractor version is here if useful: &lt;a href="https://opspack.vercel.app/kits/client-contract-kit-contractors" rel="noopener noreferrer"&gt;Client Contract &amp;amp; Scope Kit for Home-Service Contractors&lt;/a&gt; ($19). There's also a free starter kit at &lt;a href="https://opspack.vercel.app/free" rel="noopener noreferrer"&gt;opspack.vercel.app/free&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;General information, not legal advice.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>smallbusiness</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Freelancers: how much to set aside before the Jan 15 estimated-tax deadline</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Wed, 11 Nov 2026 15:14:54 +0000</pubDate>
      <link>https://dev.to/opspack/freelancers-how-much-to-set-aside-before-the-jan-15-estimated-tax-deadline-dg8</link>
      <guid>https://dev.to/opspack/freelancers-how-much-to-set-aside-before-the-jan-15-estimated-tax-deadline-dg8</guid>
      <description>&lt;p&gt;If you got paid as a freelancer this year and nobody withheld tax, the IRS expects you to pay as you go. The last quarterly estimated payment for 2026 income is due &lt;strong&gt;January 15, 2027&lt;/strong&gt;. Here's a simple way to stop that date from being a surprise. (General info, not tax advice; check with a tax pro for your situation.)&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Know what you're actually paying
&lt;/h2&gt;

&lt;p&gt;Self-employed income carries &lt;strong&gt;self-employment tax (15.3% on most net earnings)&lt;/strong&gt; on top of regular income tax. That's why a "normal" paycheck mindset under-saves.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Pick a set-aside percentage and automate it
&lt;/h2&gt;

&lt;p&gt;Many freelancers move a fixed share of every client payment, often somewhere around 25 to 30%, into a separate savings account the day it lands. The exact number depends on your bracket and state; the habit matters more than the decimal.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Use the safe-harbor rule to avoid penalties
&lt;/h2&gt;

&lt;p&gt;You generally avoid the underpayment penalty if your estimates cover &lt;strong&gt;100% of last year's total tax&lt;/strong&gt; (110% if last year's AGI was over $150,000), or 90% of this year's. Divide that by four and you have a predictable target per quarter.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Track each payment against each quarter
&lt;/h2&gt;

&lt;p&gt;One row per client payment, one column for the set-aside amount, one rollup per quarter, and a checkbox for "estimate paid." That's the whole system.&lt;/p&gt;




&lt;p&gt;If you'd rather not build that table yourself, the &lt;a href="https://opspack.vercel.app/kits/freelancer-tax-setaside-notion" rel="noopener noreferrer"&gt;OpsPack Tax Set-Aside + Quarterly Estimate Tracker for Notion&lt;/a&gt; ($12) has the payment log, set-aside formulas and quarterly rollups ready to duplicate. Free client-ops templates are at &lt;a href="https://opspack.vercel.app/free" rel="noopener noreferrer"&gt;opspack.vercel.app/free&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Video editors: footage batches, timestamped notes and the "five more versions" problem</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Tue, 10 Nov 2026 15:16:13 +0000</pubDate>
      <link>https://dev.to/opspack/video-editors-footage-batches-timestamped-notes-and-the-five-more-versions-problem-boe</link>
      <guid>https://dev.to/opspack/video-editors-footage-batches-timestamped-notes-and-the-five-more-versions-problem-boe</guid>
      <description>&lt;p&gt;Most edit projects don't go over budget in the timeline. They go over in the inbox: footage that keeps arriving after you've cut, feedback sent as a voice note, and a cheerful "can you make five more versions for TikTok?" after the final export.&lt;/p&gt;

&lt;p&gt;None of these are bad clients. They're gaps in the agreement. Here are the clauses and line items that close them, in the order they usually bite.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The clock starts when the footage is complete
&lt;/h2&gt;

&lt;p&gt;If footage arrives in six batches over three weeks, you end up cutting the same sequence three times. Put the start condition in writing:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Footage delivery:&lt;/strong&gt; Timeline starts when all footage, assets and brand files are delivered in one batch.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Pair it with a general inputs clause so the rule applies to everything, not just footage:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Client will provide content, access, assets and feedback by the dates agreed at kickoff, and confirms it has the rights to any material it supplies. Delays in inputs extend the timeline by the same number of days.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And in your SOW's out-of-scope list:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Re-cutting from new footage after the first cut&lt;/li&gt;
&lt;li&gt;Raw footage organization over [N] GB&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now a late batch isn't an argument. It's a date shift or a change order, and the client picks which.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. One round = one document of timestamped notes
&lt;/h2&gt;

&lt;p&gt;"Two revision rounds" means nothing if a round can be a voice note on Tuesday, three Slack messages on Wednesday and a stakeholder's comments on Friday. Define a round:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The SOW includes [2] revision rounds per deliverable. A round is &lt;strong&gt;one consolidated list of feedback from the named approver&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Extra rounds are billed at $[RATE]/hour or $[AMOUNT] per round.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then add the video-specific part to your SOW deliverables:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[2] revision rounds via timestamped notes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Timestamped notes ("00:42 – trim the pause", "01:15 – swap to the wide shot") are faster for you to action and harder to contradict later. Voice notes with no timestamps aren't a round yet. Ask for them to be consolidated before you open the project file.&lt;/p&gt;

&lt;p&gt;One more line worth having: what counts as a revision vs. a change.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;New footage or a new story structure after the first cut = change order.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A revision refines the approved cut. A new structure is a new edit.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Define "version" before someone asks for five more
&lt;/h2&gt;

&lt;p&gt;"Can you make 5 more versions for TikTok?" is really several requests packed into one: new aspect ratios, new lengths, maybe new captions, maybe new hooks. Each is real work.&lt;/p&gt;

&lt;p&gt;Spell out what you're delivering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[N] edited videos up to [LENGTH] each&lt;/li&gt;
&lt;li&gt;Captions/subtitles in [language]&lt;/li&gt;
&lt;li&gt;Export in [formats/aspect ratios]&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And put this in out of scope:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Additional aspect ratios or versions&lt;/li&gt;
&lt;li&gt;Motion graphics or animation beyond lower thirds&lt;/li&gt;
&lt;li&gt;Licensed music/stock footage (billed at cost)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A practical working definition: a &lt;strong&gt;version&lt;/strong&gt; is any additional export that differs in aspect ratio, length, edit structure or on-screen text from a delivered video. Write your own definition into the SOW. The point is that it exists before the request does.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Price extras as line items, not one number
&lt;/h2&gt;

&lt;p&gt;When "extra version" is already a priced line, quoting it isn't awkward. You're just reading from the sheet.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Pricing model&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Edit per video (up to N min)&lt;/td&gt;
&lt;td&gt;per video&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Captions&lt;/td&gt;
&lt;td&gt;per video&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra aspect ratio/version&lt;/td&gt;
&lt;td&gt;per version&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Motion graphics&lt;/td&gt;
&lt;td&gt;quoted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra revision round&lt;/td&gt;
&lt;td&gt;per round&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rush turnaround&lt;/td&gt;
&lt;td&gt;+25–50%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  5. A change-order clause, and the reply that uses it
&lt;/h2&gt;

&lt;p&gt;The agreement side:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Client may request changes at any time. Provider will reply with a short change order stating the added cost and timeline impact. Work on the change starts after Client approves it in writing (email is fine). Small changes can be billed at $[RATE]/hour, in [15/30]-minute increments.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The email side. When the five-versions request lands, pause first:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; [PROJECT] — treating [REQUEST] as a scope change&lt;/p&gt;

&lt;p&gt;Hi [NAME], thanks for the note on [REQUEST]. Compared to our scope baseline ([DATE / SOW]), this looks like a change because [ONE CLEAR REASON]. I'm pausing on that piece until we pick a path so we don't burn timeline or budget by accident. I'll send options shortly (trade scope, move the date, add a fee, or defer).&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then give a clear choice:&lt;/p&gt;

&lt;blockquote&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Trade scope:&lt;/strong&gt; Add [REQUEST]; remove/reduce [ITEM]; keep deadline [DATE] and fee.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move the date:&lt;/strong&gt; Add [REQUEST] and keep full scope; new deadline [NEW DATE]; same fee.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add a fee:&lt;/strong&gt; Add [REQUEST]; keep deadline [DATE] and full scope; change order &lt;strong&gt;$[FEE]&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Defer:&lt;/strong&gt; Keep the current plan; park [REQUEST] for a later phase.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Reply with 1, 2, 3, or 4 and I'll update the plan. I won't start the extra work until you choose.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Most clients pick quickly when the options are laid out like that.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Two clauses editors forget
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Music &amp;amp; stock:&lt;/strong&gt; Client licenses music and stock in Client's name, or Editor licenses at cost with written approval.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project files:&lt;/strong&gt; Project/source files are archived for [30] days after delivery and delivered for $[AMOUNT] if requested.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The first keeps licensing liability where it belongs. The second answers the "can you send the project file?" request six months later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep a log
&lt;/h2&gt;

&lt;p&gt;Track every request in a simple sheet: date, who asked, summary, in scope or change, hours impact, fee delta, option chosen, approval date. When an invoice gets questioned, the log is what you point to.&lt;/p&gt;




&lt;p&gt;If a client has stopped paying after delivery, the free &lt;a href="https://opspack.vercel.app/final-notice" rel="noopener noreferrer"&gt;final notice email template&lt;/a&gt; is a calm, firm last message before escalation.&lt;/p&gt;

&lt;p&gt;The full set (proposal, SOW and services agreement in .md and .docx, 10 client emails, change-request triage, revision log CSV, invoice emails and the video editor niche guide these clauses come from) is the &lt;a href="https://opspack.vercel.app/kits/client-contract-kit-video-editors" rel="noopener noreferrer"&gt;Client Contract &amp;amp; Scope Kit for Video Editors&lt;/a&gt;, $19.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Templates are practical starting points, not legal advice. Have your agreement reviewed locally once, then reuse it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>video</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A quote calculator for freelance projects: hours rate buffer</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Mon, 09 Nov 2026 13:11:37 +0000</pubDate>
      <link>https://dev.to/opspack/a-quote-calculator-for-freelance-projects-hours-x-rate-x-buffer-kcj</link>
      <guid>https://dev.to/opspack/a-quote-calculator-for-freelance-projects-hours-x-rate-x-buffer-kcj</guid>
      <description>&lt;p&gt;Most underpriced quotes aren't a rate problem. They're a counting problem: the quote covers the deliverables and forgets the kickoff call, the revisions, the emails and the week the client went quiet.&lt;/p&gt;

&lt;p&gt;Here's the simple structure I use. It fits in one spreadsheet and you can rebuild it in five minutes.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. List every line, not just the deliverables
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Line item&lt;/th&gt;
&lt;th&gt;Hours&lt;/th&gt;
&lt;th&gt;Rate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Discovery / kickoff&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Research / audit&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Production: deliverable 1&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Production: deliverable 2&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Revisions (2 rounds)&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Project management / comms&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Approved expenses&lt;/td&gt;
&lt;td&gt;at cost&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two lines people skip: &lt;strong&gt;revisions&lt;/strong&gt; (budget roughly 20–30% of production time) and &lt;strong&gt;project management&lt;/strong&gt; (status updates and email are real hours).&lt;/p&gt;

&lt;p&gt;Line total = hours × rate + any fixed cost. In this example the subtotal is 25 hours, $2,500.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Add a risk buffer as its own line
&lt;/h2&gt;

&lt;p&gt;Unknowns and slow feedback always cost something. Add 10–20% as a visible buffer instead of quietly inflating your rate.&lt;/p&gt;

&lt;p&gt;At 15%: $2,500 × 0.15 = $375.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Round up, on purpose
&lt;/h2&gt;

&lt;p&gt;$2,500 + $375 = $2,875. Round up to the nearest $50: &lt;strong&gt;$2,900&lt;/strong&gt;. A round number reads as a considered price, and the rounding is a little extra margin.&lt;/p&gt;

&lt;p&gt;In a spreadsheet: &lt;code&gt;=CEILING(subtotal + buffer, 50)&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Split deposit and balance in the same sheet
&lt;/h2&gt;

&lt;p&gt;With a 50% deposit: &lt;strong&gt;$1,450 due to start&lt;/strong&gt;, $1,450 on delivery. Putting this in the quote means the deposit is never a surprise conversation later. (If you want wording for asking for one, there's a free deposit request page at &lt;a href="https://opspack.vercel.app/deposit" rel="noopener noreferrer"&gt;https://opspack.vercel.app/deposit&lt;/a&gt;.)&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep the sheet as your master
&lt;/h2&gt;

&lt;p&gt;Save it blank. Next project you only change the hours. Over time your actual hours per line become your best pricing data.&lt;/p&gt;




&lt;p&gt;If you'd rather not build it, the &lt;a href="https://opspack.vercel.app/kits/project-quote-calculator" rel="noopener noreferrer"&gt;Freelance Project Quote Calculator&lt;/a&gt; is this exact sheet (Excel + CSV) for $9. If you track quotes and deposits in Notion, there's also a &lt;a href="https://opspack.vercel.app/kits/freelancer-quote-deposit-notion" rel="noopener noreferrer"&gt;Quote + Deposit Tracker for Notion&lt;/a&gt; for $12.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Templates, not financial advice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Copywriters: revision vs. rewrite — get the brief approved first</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Sun, 08 Nov 2026 13:11:37 +0000</pubDate>
      <link>https://dev.to/opspack/copywriters-revision-vs-rewrite-get-the-brief-approved-first-4d0k</link>
      <guid>https://dev.to/opspack/copywriters-revision-vs-rewrite-get-the-brief-approved-first-4d0k</guid>
      <description>&lt;p&gt;"Two revision rounds included" sounds clear until round two arrives with a new audience, a new offer and a new stakeholder. That isn't a revision. It's a rewrite, and rewrites are new work.&lt;/p&gt;

&lt;p&gt;The line that makes this easy to hold: &lt;strong&gt;a revision refines the approved brief; a rewrite responds to a new brief.&lt;/strong&gt; That only works if there &lt;em&gt;is&lt;/em&gt; an approved brief, in writing, before you draft a word.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Make brief approval a gate in the agreement
&lt;/h2&gt;

&lt;p&gt;Add this clause to your services agreement:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Brief approval:&lt;/strong&gt; Drafting starts after Client approves the messaging brief. Changes to the brief after approval are billed as new work.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Then list the brief as its own deliverable in the SOW, priced flat, so the client sees it as a real step and not admin.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Put these in "Out of scope"
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Rewrites after a change in brief, offer or audience&lt;/li&gt;
&lt;li&gt;Design, layout, uploading to CMS&lt;/li&gt;
&lt;li&gt;Keyword research beyond [N] keywords&lt;/li&gt;
&lt;li&gt;Sourcing images or graphics&lt;/li&gt;
&lt;li&gt;Legal/compliance review of claims&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And one more clause worth having: the client is responsible for verifying factual, medical, financial or legal claims in final copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Quote it in line items, not one number
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Pricing model&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Discovery + messaging brief&lt;/td&gt;
&lt;td&gt;flat&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Per page/email/article&lt;/td&gt;
&lt;td&gt;per piece&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Revision rounds (2 included)&lt;/td&gt;
&lt;td&gt;included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra round&lt;/td&gt;
&lt;td&gt;per round&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CMS upload/formatting&lt;/td&gt;
&lt;td&gt;per piece&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rush&lt;/td&gt;
&lt;td&gt;+25–50%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;When "extra round" is already a priced line, asking for one stops being awkward.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The three red flags (and the reply)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;"Make it pop"&lt;/strong&gt; with no specifics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A stakeholder joins in round 2&lt;/strong&gt; and rewrites the brief.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;"Can you also design the page?"&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For the first, ask before you touch the draft:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Quick details on [REQUEST SHORT NAME]&lt;/p&gt;

&lt;p&gt;Hi [NAME], thanks for sending this. Before I place it in the plan, could you confirm what "done" looks like, the format/audience, and who has final say? Once I have those, I'll confirm whether it fits the current revision round or outline the smallest adjustment needed.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;For the other two, pause and name it:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; [PROJECT] — treating [REQUEST] as a scope change&lt;/p&gt;

&lt;p&gt;Hi [NAME], thanks for the note on [REQUEST]. Compared to our approved brief ([DATE]), this looks like a change because [ONE CLEAR REASON]. I'm pausing on that piece until we pick a path, so we don't burn timeline or budget by accident. I'll send options shortly: trade scope, move the date, add a fee, or defer.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Log every one of these in a simple revision log (date, request, revision or change, decision). It's the thing you point to when the invoice gets questioned.&lt;/p&gt;




&lt;p&gt;If a client has gone quiet on an approved draft, the free &lt;a href="https://opspack.vercel.app/client-ghosting" rel="noopener noreferrer"&gt;client-ghosting follow-up page&lt;/a&gt; has the nudge sequence.&lt;/p&gt;

&lt;p&gt;The full set (proposal, SOW, services agreement in .md and .docx, 10 client emails, change-request triage, revision log CSV and invoice emails, with this copywriter niche guide) is the &lt;a href="https://opspack.vercel.app/kits/client-contract-kit-copywriters" rel="noopener noreferrer"&gt;Client Contract &amp;amp; Scope Kit for Copywriters&lt;/a&gt;, $19.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Templates are practical starting points, not legal advice. Have your agreement reviewed locally once, then reuse it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>writing</category>
      <category>career</category>
      <category>productivity</category>
    </item>
    <item>
      <title>VA retainers: how to stop 'quick favours' eating your hours (hours-cap clause)</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Sat, 07 Nov 2026 13:07:51 +0000</pubDate>
      <link>https://dev.to/opspack/va-retainers-how-to-stop-quick-favours-eating-your-hours-hours-cap-clause-5ckc</link>
      <guid>https://dev.to/opspack/va-retainers-how-to-stop-quick-favours-eating-your-hours-hours-cap-clause-5ckc</guid>
      <description>&lt;p&gt;A retainer priced for 10 hours becomes a 30-hour month when every Slack "quick favour" lands in the same bucket. The fix is not working faster — it is an &lt;strong&gt;hours-cap clause&lt;/strong&gt; in the SOW, a short task-category list, and a written path for anything over the cap.&lt;/p&gt;

&lt;p&gt;Save the four emails below as Gmail templates. Replace the &lt;code&gt;[BRACKETS]&lt;/code&gt; once per client and reuse.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Put the cap in the SOW (not in chat)
&lt;/h2&gt;

&lt;p&gt;From the OpsPack VA niche guide, typical deliverables to list:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[N] hours/month of support in listed task categories&lt;/li&gt;
&lt;li&gt;Inbox and calendar management during agreed hours&lt;/li&gt;
&lt;li&gt;Weekly written status update&lt;/li&gt;
&lt;li&gt;Shared task tracker maintained daily&lt;/li&gt;
&lt;li&gt;Monthly hours report&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Write these into &lt;strong&gt;Out of scope&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tasks outside listed categories (e.g. bookkeeping, design, ads management)&lt;/li&gt;
&lt;li&gt;Work outside agreed hours / weekends&lt;/li&gt;
&lt;li&gt;Urgent same-hour requests unless on a priority plan&lt;/li&gt;
&lt;li&gt;Paid tools and subscriptions&lt;/li&gt;
&lt;li&gt;Rollover of unused hours (unless stated)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Hours-cap clause to paste into the services agreement&lt;/strong&gt; (from the same guide — brackets are yours to fill):&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Hours cap:&lt;/strong&gt; VA will notify Client at [80]% of monthly hours. Hours beyond the cap require Client approval and are billed at $[RATE]/hour.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Unused hours:&lt;/strong&gt; Unused hours [expire at month end / roll over up to [N] hours for one month].&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And the SOW baseline:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Included: up to &lt;strong&gt;[N] hours per calendar month&lt;/strong&gt; across the task categories listed in Schedule A. Hours are logged weekly and shared in the monthly hours report. Work requested after the cap is reached is out of scope until a written overage quote is approved.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  2. Task categories beat vague "VA support"
&lt;/h2&gt;

&lt;p&gt;Retainers drift by &lt;strong&gt;task-creep&lt;/strong&gt;, not by revision rounds. Keep 5–8 categories in Schedule A. A new category triggers a scope review — not a free add. Hours over the cap need written approval.&lt;/p&gt;

&lt;p&gt;Line items that keep the quote honest:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Pricing model&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Monthly retainer (N hours)&lt;/td&gt;
&lt;td&gt;monthly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Additional hours&lt;/td&gt;
&lt;td&gt;per hour, 15-min increments&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Priority / rush add-on&lt;/td&gt;
&lt;td&gt;monthly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Onboarding + SOP setup&lt;/td&gt;
&lt;td&gt;flat&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Project work (outside retainer)&lt;/td&gt;
&lt;td&gt;quoted separately&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  3. Four emails when hours are about to blow
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Approaching 80% of the monthly cap
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Heads-up — &lt;code&gt;[RETAINER / MONTH]&lt;/code&gt; hours at ~&lt;code&gt;[XX]&lt;/code&gt;% of cap&lt;/p&gt;

&lt;p&gt;Hi &lt;code&gt;[NAME]&lt;/code&gt;,&lt;/p&gt;

&lt;p&gt;Quick status on our &lt;code&gt;[MONTH]&lt;/code&gt; retainer (&lt;code&gt;[HOURS CAP]&lt;/code&gt; hours / month): we’ve used about &lt;strong&gt;&lt;code&gt;[HOURS USED]&lt;/code&gt; hours (~&lt;code&gt;[XX]&lt;/code&gt;%)&lt;/strong&gt;, with roughly &lt;strong&gt;&lt;code&gt;[HOURS REMAINING]&lt;/code&gt; hours&lt;/strong&gt; left before the cap.&lt;/p&gt;

&lt;p&gt;To keep priority work inside the retainer, I suggest we:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Finish &lt;code&gt;[IN-SCOPE ITEMS]&lt;/code&gt; with the remaining hours
&lt;/li&gt;
&lt;li&gt;Park or schedule &lt;code&gt;[LOWER-PRIORITY ITEMS]&lt;/code&gt; for next month
&lt;/li&gt;
&lt;li&gt;Or approve a small overage block if &lt;code&gt;[URGENT ITEM]&lt;/code&gt; can’t wait&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Reply with your preference and I’ll plan the rest of the month against the cap.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;&lt;br&gt;
&lt;code&gt;[YOUR NAME]&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  At the monthly cap
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; &lt;code&gt;[RETAINER]&lt;/code&gt; — monthly hour cap reached for &lt;code&gt;[MONTH]&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Hi &lt;code&gt;[NAME]&lt;/code&gt;,&lt;/p&gt;

&lt;p&gt;We’ve hit the &lt;strong&gt;&lt;code&gt;[HOURS CAP]&lt;/code&gt;-hour&lt;/strong&gt; cap for &lt;code&gt;[MONTH]&lt;/code&gt; on &lt;code&gt;[RETAINER]&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Anything new from here is outside the included block. Options:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pause&lt;/strong&gt; new requests until &lt;code&gt;[NEXT BILLING DATE]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Swap scope&lt;/strong&gt; — drop/defer &lt;code&gt;[ITEM]&lt;/code&gt; so I can take &lt;code&gt;[NEW ITEM]&lt;/code&gt; inside remaining/next-month hours
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Overage&lt;/strong&gt; — I’ll send a short quote for the extra hours at &lt;strong&gt;&lt;code&gt;$[RATE]&lt;/code&gt;/hr&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I won’t start unpaid overflow work until you pick a path. Happy to jump on a 10-minute call if useful.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;&lt;br&gt;
&lt;code&gt;[YOUR NAME]&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Overage quote
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Overage quote — &lt;code&gt;[HOURS]&lt;/code&gt; hrs on &lt;code&gt;[RETAINER]&lt;/code&gt; (&lt;code&gt;[MONTH]&lt;/code&gt;)&lt;/p&gt;

&lt;p&gt;Hi &lt;code&gt;[NAME]&lt;/code&gt;,&lt;/p&gt;

&lt;p&gt;As discussed, here’s the overage for work beyond the &lt;code&gt;[HOURS CAP]&lt;/code&gt;-hour retainer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Work:&lt;/strong&gt; &lt;code&gt;[SHORT DESCRIPTION]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hours:&lt;/strong&gt; &lt;code&gt;[QUOTED HOURS]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rate:&lt;/strong&gt; &lt;code&gt;$[RATE]&lt;/code&gt;/hr
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total:&lt;/strong&gt; &lt;code&gt;$[AMOUNT]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timing:&lt;/strong&gt; &lt;code&gt;[START / DELIVERY WINDOW]&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Reply &lt;strong&gt;approved&lt;/strong&gt; (or tweak the hours) and I’ll start. Payment terms: &lt;code&gt;[NET 7 / due on invoice / same as retainer]&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;&lt;br&gt;
&lt;code&gt;[YOUR NAME]&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Decline unpaid overflow ("quick favour")
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Re: &lt;code&gt;[REQUEST]&lt;/code&gt; — needs an overage or next-month slot&lt;/p&gt;

&lt;p&gt;Hi &lt;code&gt;[NAME]&lt;/code&gt;,&lt;/p&gt;

&lt;p&gt;Thanks for sending &lt;code&gt;[REQUEST]&lt;/code&gt;. We’re at (or past) the included hours for &lt;code&gt;[MONTH]&lt;/code&gt;, so I can’t take this as unpaid overflow without blowing the retainer.&lt;/p&gt;

&lt;p&gt;Happy to help via either:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Overage&lt;/strong&gt; at &lt;code&gt;$[RATE]&lt;/code&gt;/hr — I can send a 1-line quote today
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Next month&lt;/strong&gt; — first priority when the &lt;code&gt;[NEXT MONTH]&lt;/code&gt; block resets on &lt;code&gt;[BILLING DAY]&lt;/code&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Which do you prefer? I’ll hold on the work until you choose so nothing gets lost.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;&lt;br&gt;
&lt;code&gt;[YOUR NAME]&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;For the classic “it’s just one quick change” message that arrives before you are near the cap, the VA kit’s triage reply still applies — pause, confirm whether it fits the current round, or send options (trade scope, move the date, add a fee, or defer).&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Rollover: say none, or say the rule
&lt;/h2&gt;

&lt;p&gt;Default that keeps arguments short: &lt;strong&gt;unused hours expire at month end&lt;/strong&gt; unless the client pays for a banked-hours add-on. Silence here is how “unused hours” become a dispute in month three.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. One kit link
&lt;/h2&gt;

&lt;p&gt;Want the VA-ready proposal, SOW, services agreement, scope-creep emails and niche guide in one ZIP?&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://opspack.vercel.app/kits/client-contract-kit-virtual-assistants" rel="noopener noreferrer"&gt;https://opspack.vercel.app/kits/client-contract-kit-virtual-assistants&lt;/a&gt; ($19)&lt;/p&gt;

&lt;p&gt;Also: &lt;a href="https://opspack.vercel.app/kits" rel="noopener noreferrer"&gt;https://opspack.vercel.app/kits&lt;/a&gt; · free page &lt;a href="https://opspack.vercel.app/client-tracker" rel="noopener noreferrer"&gt;https://opspack.vercel.app/client-tracker&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Tracking hours against the cap in Notion: &lt;a href="https://opspack.vercel.app/kits/freelancer-retainer-hours-notion" rel="noopener noreferrer"&gt;https://opspack.vercel.app/kits/freelancer-retainer-hours-notion&lt;/a&gt; ($15)&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>productivity</category>
      <category>writing</category>
    </item>
    <item>
      <title>The 10 scope-creep emails I'd save as Gmail templates</title>
      <dc:creator>OpsPack</dc:creator>
      <pubDate>Fri, 06 Nov 2026 15:30:14 +0000</pubDate>
      <link>https://dev.to/opspack/the-10-scope-creep-emails-id-save-as-gmail-templates-262l</link>
      <guid>https://dev.to/opspack/the-10-scope-creep-emails-id-save-as-gmail-templates-262l</guid>
      <description>&lt;p&gt;"Can you just add one more thing?"&lt;/p&gt;

&lt;p&gt;If you answer yes in the chat and start working, you've already lost the negotiation. The fix isn't a longer contract — it's ten short emails you can paste from Gmail templates so every new request gets triaged before unpaid work starts.&lt;/p&gt;

&lt;p&gt;Save each of these as a canned response. Replace the &lt;code&gt;[BRACKETS]&lt;/code&gt; once per project and reuse.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Clarifying a vague request
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Quick details on [REQUEST SHORT NAME]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Thanks for sending this. Before I place it in the plan, could you confirm:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[Desired outcome / what "done" looks like]&lt;/li&gt;
&lt;li&gt;[Format, quantity, audience, or platforms]&lt;/li&gt;
&lt;li&gt;[Needed-by date and who has final say]&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Once I have those, I'll confirm whether it fits the current [scope / revision round] or outline the smallest adjustment needed.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Confirming something is in scope
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Confirmed — [REQUEST] is in scope&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Good news: [REQUEST] fits our agreed scope / current revision round for [PROJECT].&lt;/p&gt;

&lt;p&gt;I'll include it in [MILESTONE / THIS WEEK'S PLAN]. No change to fee or deadline from this item alone.&lt;/p&gt;

&lt;p&gt;If anything expands beyond [BOUNDARY — e.g. one consolidated feedback batch], I'll flag it before doing extra work.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Flagging a change (pause before unpaid work)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; [PROJECT] — treating [REQUEST] as a scope change&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Thanks for the note on [REQUEST]. Compared to our scope baseline ([DATE / SOW]), this looks like a change because [ONE CLEAR REASON].&lt;/p&gt;

&lt;p&gt;I'm pausing on that piece until we pick a path so we don't burn timeline or budget by accident. I'll send options shortly (trade scope, move the date, add a fee, or defer).&lt;/p&gt;

&lt;p&gt;If you meant something smaller — e.g. [NARROWER INTERPRETATION] — reply and I'll re-triage.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Presenting the four options
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Options for [REQUEST] on [PROJECT]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Here's a clear choice for [REQUEST SHORT SUMMARY]:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Trade scope&lt;/strong&gt; — Add [REQUEST]; remove/reduce [ITEM]; keep deadline [DATE] and fee.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move the date&lt;/strong&gt; — Add [REQUEST] and keep full scope; new deadline [NEW DATE]; same fee.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add a fee&lt;/strong&gt; — Add [REQUEST]; keep deadline [DATE] and full scope; change order &lt;strong&gt;$[FEE]&lt;/strong&gt; ([when due]).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Defer&lt;/strong&gt; — Keep the current plan; park [REQUEST] for [Phase 2 / after launch].&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My recommendation is &lt;strong&gt;Option [N]&lt;/strong&gt; because [ONE SENTENCE].&lt;/p&gt;

&lt;p&gt;Reply with 1, 2, 3, or 4 (or tweak) and I'll update the plan and log. I won't start the extra work until you choose.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Pausing work (blocked on input / decision)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; [PROJECT] paused on [ITEM] — need [INPUT / DECISION]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;I'm pausing [DELIVERABLE / TASK] because [missing asset / access / approver decision].&lt;/p&gt;

&lt;p&gt;What I need: [SPECIFIC ASK]&lt;br&gt;
Needed by: [DATE] to hold [MILESTONE DATE]&lt;/p&gt;

&lt;p&gt;Once that arrives, I'll confirm the revised sequence. Related dates may shift day-for-day if this slips past [DATE].&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  6. "It's just one quick change"
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Re: quick change on [PROJECT]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Happy to help with [REQUEST]. Even small adds can affect [revision count / QA / other deliverables], so I run them through the same triage as larger ones.&lt;/p&gt;

&lt;p&gt;I'll confirm within [24 hours / today] whether it's covered in the current round or needs a small trade-off (scope, date, fee, or defer).&lt;/p&gt;

&lt;p&gt;Appreciate you flagging it early — that's the easy version of scope control.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Revision-round limit reached
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; [DELIVERABLE] — revision rounds used; next steps&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;We've completed the [N] revision rounds included for [DELIVERABLE]. Further changes are welcome — they just move into the change-order path so the rest of [PROJECT] stays on track.&lt;/p&gt;

&lt;p&gt;If you have another consolidated pass, I can send the four options (trade scope / move date / add fee / defer) for that pass.&lt;/p&gt;

&lt;p&gt;Also happy to lock what's done and ship as-is if you're ready.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Deadline must hold — trading scope
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Keeping [DATE] — proposed scope trade for [REQUEST]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Understood that [DATE] can't move. To add [REQUEST] without slipping the date or fee, I recommend &lt;strong&gt;Option 1 — trade scope&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Add:&lt;/strong&gt; [REQUEST]&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remove or reduce:&lt;/strong&gt; [SPECIFIC ITEM]&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deadline / fee:&lt;/strong&gt; unchanged&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you'd rather keep [ITEM], we can look at a fee (Option 3) or a later phase (Option 4) instead.&lt;/p&gt;

&lt;p&gt;Which do you prefer?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Fee objection / pushback
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Re: change-order fee for [REQUEST]&lt;/p&gt;

&lt;p&gt;Hi [NAME],&lt;/p&gt;

&lt;p&gt;Totally fair to pressure-test the fee. The &lt;strong&gt;$[FEE]&lt;/strong&gt; reflects roughly [HOURS] hours for [work packages], so we can keep [DATE] and the rest of the scope intact.&lt;/p&gt;

&lt;p&gt;If budget is tight, these alternatives still work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Trade scope&lt;/strong&gt; — add [REQUEST], drop [ITEM], same fee/date&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Move date&lt;/strong&gt; — add [REQUEST], new date [NEW DATE], same fee&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Defer&lt;/strong&gt; — ship current scope now; estimate Phase 2 separately&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'm flexible on &lt;em&gt;which&lt;/em&gt; lever we pull — less flexible on doing unpaid expansion that quietly breaks the plan.&lt;/p&gt;

&lt;p&gt;What works on your side?&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
[YOUR NAME]&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Confirming written approval
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Subject:&lt;/strong&gt; Confirmed — [REQUEST] approved as Option [N]&lt;/p&gt;

&lt;p&gt;Always close the loop in writing. Once they pick an option, reply with the choice, the new fee/date/scope (if any), and that work starts after this confirmation. Paste that into your revision log so the next "quick change" has a baseline.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to install these as Gmail templates
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open Gmail → Settings → Advanced → enable Templates.&lt;/li&gt;
&lt;li&gt;Compose each email once with your usual signature.&lt;/li&gt;
&lt;li&gt;More (⋮) → Templates → Save draft as template.&lt;/li&gt;
&lt;li&gt;When a client pings you, insert the matching template and fill the brackets before you reply in chat.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The pause-before-work habit matters more than perfect wording. Email 3 (flag the change) plus email 4 (four options) cover most of the damage.&lt;/p&gt;




&lt;p&gt;If you want the full set as copy-paste Markdown (plus the proposal and late-invoice scripts), the &lt;a href="https://opspack.vercel.app/kits/scope-creep-client-emails" rel="noopener noreferrer"&gt;10 Scope-Creep Client Emails&lt;/a&gt; pack is $5, and the &lt;a href="https://opspack.vercel.app/kits/freelancer-email-scripts-bundle" rel="noopener noreferrer"&gt;Freelancer Email Scripts Bundle&lt;/a&gt; is $12. Free triage scripts live on &lt;a href="https://opspack.vercel.app/scope-creep" rel="noopener noreferrer"&gt;/scope-creep&lt;/a&gt;. Full library: &lt;a href="https://opspack.vercel.app/kits" rel="noopener noreferrer"&gt;opspack.vercel.app/kits&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>freelance</category>
      <category>career</category>
      <category>productivity</category>
      <category>writing</category>
    </item>
  </channel>
</rss>
