<?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: Plainwork Studio</title>
    <description>The latest articles on DEV Community by Plainwork Studio (@plainworkstudio).</description>
    <link>https://dev.to/plainworkstudio</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%2F4246693%2Fbd6897c6-e42b-49d2-8f14-71b213bfb903.png</url>
      <title>DEV Community: Plainwork Studio</title>
      <link>https://dev.to/plainworkstudio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/plainworkstudio"/>
    <language>en</language>
    <item>
      <title>How to Stop Scope Creep Before It Starts: A 4-Document System for Solo Developers</title>
      <dc:creator>Plainwork Studio</dc:creator>
      <pubDate>Tue, 17 Nov 2026 00:33:36 +0000</pubDate>
      <link>https://dev.to/plainworkstudio/how-to-stop-scope-creep-before-it-starts-a-4-document-system-for-solo-developers-2631</link>
      <guid>https://dev.to/plainworkstudio/how-to-stop-scope-creep-before-it-starts-a-4-document-system-for-solo-developers-2631</guid>
      <description>&lt;p&gt;Every freelancer knows the message. It arrives at 9pm on a Thursday, three days before delivery:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Hey — quick one. Could you also add a login page? It's basically the same thing, right?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You are tired. The client is friendly. There is no sentence ready in your head. So you write "sure, no problem", and you have just donated a weekend.&lt;/p&gt;

&lt;p&gt;I used to think this was a client problem. It is not. Scope creep is almost always a &lt;strong&gt;missing document&lt;/strong&gt;: nobody wrote down how many revisions were included, so the fifth revision is not an unreasonable request — it is an undefined one. Undefined requests get answered by whoever is more tired.&lt;/p&gt;

&lt;p&gt;Here is the system that fixes it. Four documents, one script ladder, no confrontation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Document 1: the intake form (send it before you quote)
&lt;/h2&gt;

&lt;p&gt;Half of all scope creep starts with a quote written for a project you did not understand. Twelve questions fix most of that. The three that matter most:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;7. What must absolutely be included?
8. What is explicitly out of scope for this project?
10. How quickly can you answer questions during the project?
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Question 8 is the one almost nobody asks. When a client writes "we definitely don't want a CMS" in their own words, you can paste that sentence into your scope document. It is much harder for them to argue with their own sentence than with your boundary.&lt;/p&gt;

&lt;p&gt;Question 10 sets the response window before you need it. You will quote their answer back in the onboarding email: "you said a two-day reply is realistic."&lt;/p&gt;

&lt;h2&gt;
  
  
  Document 2: the onboarding letter (the highest-leverage email you will write)
&lt;/h2&gt;

&lt;p&gt;Send it within 24 hours of the deposit. It answers the five things a new client is silently worried about: did I choose right, what happens next, what do I have to do, when will I hear from them, and what happens if plans change.&lt;/p&gt;

&lt;p&gt;The paragraph that does the real work:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;One thing that helps: if you'd rather I just handle small things without asking,
tell me a ceiling — for example "anything under an hour, just do it." I'll keep a
log so you always see it.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is the whole trick, and it works because of three properties:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It gives the client a way to grant you &lt;strong&gt;discretion&lt;/strong&gt;, so you sound generous rather than rigid.&lt;/li&gt;
&lt;li&gt;It caps that discretion at a number &lt;strong&gt;they chose&lt;/strong&gt;, so the cap is theirs, not yours.&lt;/li&gt;
&lt;li&gt;It creates a log, so the favour stays visible instead of evaporating.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Clients almost always name a ceiling. Then, when the third "quick one" arrives, your reply is one line: "adding it to the log — inside the hour you set aside." No friction, no resentment, and no unpaid work you did not agree to.&lt;/p&gt;

&lt;h2&gt;
  
  
  Document 3: the one-page scope document
&lt;/h2&gt;

&lt;p&gt;Clients do not read long contracts. A document nobody read protects nobody. Keep it to one page with numbered sections and put real content in section 4, &lt;strong&gt;Out of Scope&lt;/strong&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;4. OUT OF SCOPE (unless added by change order)
   - Additional pages, sections or items beyond the quantities in section 2
   - Copywriting, translation, photography, illustration
   - Ongoing maintenance after the handover date
   - Anything not listed in section 2
   - A new logo (client: "we categorically don't want to touch the brand")
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And define a revision round:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;5. REVISIONS
   3 rounds on the homepage design. A "round" = one consolidated set of comments.
   Further rounds: $X each.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Without that definition, three rounds can mean thirty messages. With it, you can say "we're on round three" in week four and both of you mean the same thing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Document 4: the change order
&lt;/h2&gt;

&lt;p&gt;When the request arrives, do not negotiate in chat. Send a one-page document with three options:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;CHANGE ORDER 001
What was requested: a fourth page (login screen)
Why it's outside scope: section 2 lists three pages
A  As described      $420   +3 days
B  Smaller version   $180   no delay
C  Phase 2           $300   after the 14th

Reply "approved, option B" or I continue with the current scope.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three things happen at once:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The number does the conversation for you.&lt;/strong&gt; The client learns that requests cost money, from a document, not from an argument.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Option B is the important one.&lt;/strong&gt; Most clients take a smaller version rather than nothing. You keep the goodwill and the schedule.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It defaults safely.&lt;/strong&gt; "If I don't hear back, I continue with the current scope" means silence never becomes unpaid work.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That last sentence is what makes the change order a shield rather than a formality.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five-rung ladder for the conversation itself
&lt;/h2&gt;

&lt;p&gt;Documents handle the paper. You still need sentences for the moment. Move up one rung per message; never skip to the top.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Acknowledge and log&lt;/strong&gt; (small, fair ask): "Yes, easy — I'll fold that in with the next deliverable. Noting it in the log."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clarify&lt;/strong&gt; (vague ask): "Happy to look — is this replacing X or adding to it, and does it need to be live before the 14th?"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Size it out loud&lt;/strong&gt; (real addition): "That's about six hours on top of the plan. It's a change order or a phase two — which do you prefer?"&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send the change order&lt;/strong&gt;: "...Option B keeps us on the original date. That's what I'd do if it were my project."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Firm no&lt;/strong&gt;: "I'll pass on that one. It would mean dropping something already committed, and I'm not prepared to do that."
Two substitutions matter more than any others. Stop writing "sorry, that's out of scope" — say "that's outside the scope document, so it needs a change order." And stop writing "don't worry about it" — say "that one's on me." Same action, completely different relationship.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why this works even with difficult clients
&lt;/h2&gt;

&lt;p&gt;The system does not depend on the client being reasonable. It depends on the fact that &lt;strong&gt;every boundary was agreed to when the relationship was still friendly&lt;/strong&gt;, and written down. In week five you are not inventing a limit to be difficult; you are reading out line six of a document they approved.&lt;/p&gt;

&lt;p&gt;The clients who accept it are the ones worth keeping. The ones who fight it have just told you, at the cheapest possible moment, what the next twelve months would look like.&lt;/p&gt;

&lt;h2&gt;
  
  
  Starter checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Intake form with a question about what is &lt;em&gt;out&lt;/em&gt; of scope&lt;/li&gt;
&lt;li&gt;[ ] Onboarding letter with a ceiling the client chooses&lt;/li&gt;
&lt;li&gt;[ ] One-page scope document, with revision rounds defined&lt;/li&gt;
&lt;li&gt;[ ] Change order template with three options and a safe default&lt;/li&gt;
&lt;li&gt;[ ] The five sentences above, written down somewhere you can reach on your phone&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  You do not need all five on day one. Start with the change order — the first time you send one, the relationship changes.
&lt;/h2&gt;

&lt;p&gt;&lt;em&gt;I build document and prompt systems for one-person businesses at &lt;a href="https://junghamin.gumroad.com/" rel="noopener noreferrer"&gt;Plainwork Studio&lt;/a&gt;. If you want this whole system ready to copy, the &lt;a href="https://junghamin.gumroad.com/l/client-onboarding-scope-creep-shield-kit" rel="noopener noreferrer"&gt;Client Onboarding &amp;amp; Scope-Creep Shield Kit&lt;/a&gt; has the 20-page playbook plus all nine templates in Markdown and CSV. And if you just want the writing side — proposals, client emails, pricing — the &lt;a href="https://junghamin.gumroad.com/l/free-ai-prompts-for-freelancers" rel="noopener noreferrer"&gt;10-prompt starter pack&lt;/a&gt; is free.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>freelancing</category>
      <category>career</category>
      <category>programming</category>
    </item>
    <item>
      <title>5 AI Prompts Every Solo Freelancer Needs for Client Proposals and Onboarding</title>
      <dc:creator>Plainwork Studio</dc:creator>
      <pubDate>Mon, 16 Nov 2026 00:51:13 +0000</pubDate>
      <link>https://dev.to/plainworkstudio/5-ai-prompts-every-solo-freelancer-needs-for-client-proposals-and-onboarding-4no0</link>
      <guid>https://dev.to/plainworkstudio/5-ai-prompts-every-solo-freelancer-needs-for-client-proposals-and-onboarding-4no0</guid>
      <description>&lt;p&gt;Most freelancers don't lose clients because the work is bad. They lose them in the two weeks around the work: the proposal that arrives three days late, the onboarding email that misses the one detail that mattered, the scope that quietly doubles because nobody wrote down what "revisions" meant.&lt;/p&gt;

&lt;p&gt;When you're a one-person business, that admin layer is your second job. It's also the part where AI actually earns its keep, because these are repetitive, high-stakes, text-heavy tasks with a known shape.&lt;/p&gt;

&lt;p&gt;Below are five prompts I use as the template layer of a solo practice. They're written to be pasted into any capable model (ChatGPT, Claude, Gemini). Replace the bracketed parts with your own context, and keep the output in a file you own rather than in the chat window.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The discovery call compressor
&lt;/h2&gt;

&lt;p&gt;You finish a call with a good feeling and no notes. Two days later you're reconstructing what they said from memory, and the proposal reflects your optimism rather than their words.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;You are a business analyst helping a solo consultant turn a sales call
into a shared record of what was agreed.

Here are my raw notes from the call:
[PASTE NOTES OR TRANSCRIPT]

Produce:
1. A two-paragraph summary of the client's situation, in plain language.
2. "What they said they need" — 3-5 bullet points, using their vocabulary,
   not mine.
3. "What I think is actually blocking them" — 2-3 bullets, clearly marked
   as my interpretation, with the evidence from the notes.
4. Open questions that must be answered before I can quote a price.
5. Red flags: scope ambiguity, budget signals, decision-maker uncertainty.

Do not invent details. If a section has nothing to support it, write
"not enough information" instead of filling the gap.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That last instruction matters more than the rest. A model that invents a budget figure because the section looks empty is worse than no summary at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. The proposal skeleton (with the price logic made explicit)
&lt;/h2&gt;

&lt;p&gt;A proposal isn't a price list. It's a document that lets a non-expert decide whether you understand their problem.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a project proposal for the client described below.

Client context: [DISCOVERY SUMMARY]
My service: [WHAT YOU DO, IN ONE SENTENCE]
My rate logic: [HOURLY / FIXED / RETAINER + WHY]
Comparable projects: [1-2 PAST PROJECTS AND WHAT THEY COST]

Structure:
1. Their situation in 3 sentences (their words, not mine).
2. What success looks like, stated as outcomes a client could check.
3. Scope: included, explicitly excluded, and what counts as a revision.
4. Two options — a core scope and a larger scope. Never more than two.
5. Timeline with client dependencies named ("waiting on brand assets"
   is a line item, not an excuse).
6. Price, payment schedule, and what happens if scope changes.
7. A single, concrete next step.

Tone: direct, no adjectives about my own excellence. Do not use the words
"passionate", "seamless", "cutting-edge", or "holistic".
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The two-option structure is the useful part. Three options push the decision back onto the client. One option invites a yes/no on your price. Two options turn the conversation into "which one", which is a different and much easier question.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The onboarding packet generator
&lt;/h2&gt;

&lt;p&gt;Onboarding is where trust is either confirmed or quietly lost. The freelancer who sends a single, complete email the day the contract is signed looks like an organisation. The one who sends four emails over a week asking for the same asset twice does not.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Build a client onboarding packet for a project starting on [DATE].

From the signed scope: [PASTE SCOPE]
Client's main contact: [NAME, ROLE]
How we'll work: [TOOLS, MEETING CADENCE, TIME ZONE]

Produce:
1. A welcome email (150 words max) that confirms the start date, names the
   one thing I need from them first, and sets the next checkpoint.
2. A checklist of everything I need from the client before kickoff,
   grouped by when it blocks me.
3. A short "how we work" page: response times, revision process, how
   changes get priced, where files live.
4. Three status-update templates (on track / waiting on you / at risk)
   that are honest without being alarming.

For each item, say whether it belongs in the first email or the shared doc,
and why.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Point 4 is the one most freelancers skip. Status updates that only get sent when something is wrong teach clients that hearing from you is bad news.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The scope-creep reply
&lt;/h2&gt;

&lt;p&gt;The request arrives as a favour: "quick tweak", "one more version", "while you're in there". Answering it badly costs you either the margin or the relationship.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A client has asked for work outside the agreed scope:

Their message: [PASTE MESSAGE]
Signed scope, verbatim: [PASTE RELEVANT CLAUSE]
Our history: [ANY PREVIOUS FAVOURS / FLEXIBILITY]

Write three replies:
A. It's genuinely small — absorb it, and mention what it substitutes for.
B. It's small but recurring — absorb this one, set the boundary for next time.
C. It's real work — quote it as a change order with a price and a timeline impact.

Each reply: under 120 words, no apology padding, no passive-aggressive
tone, and it must leave the client feeling informed rather than corrected.
Then tell me which one you'd send and what in my history made you choose it.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  5. The project close-out and referral ask
&lt;/h2&gt;

&lt;p&gt;The best time to ask for the next piece of work is the week the last one landed well. Most of us are already three projects ahead and forget.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm closing out a project. Here's what happened: [OUTCOME, DELIVERABLES]

Write:
1. A close-out summary the client could forward to their boss without
   editing it.
2. A request for a testimonial that tells them exactly what to comment on
   (specific beats "great to work with").
3. One referral ask that is easy to say yes to — not "let me know if you
   know anyone", but a named type of person and a one-line intro.
4. A three-line note I can send in six weeks that reopens the conversation
   without pretending the project is still running.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  A note on using these well
&lt;/h2&gt;

&lt;p&gt;Three habits make the difference between these being useful and being generic output you still have to rewrite:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Feed it your own words.&lt;/strong&gt; A prompt with an empty client context section produces a proposal for nobody.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a library, not a chat history.&lt;/strong&gt; Every output you improve should be saved back as a template. That's how a repeatable process forms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read it as your client would.&lt;/strong&gt; If a sentence only makes sense to someone who already knows the project, it's not finished.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;If you want these five in a single file with the client-facing templates that go with them — plus 47 more prompts I use for quotes, invoices, follow-ups, and project admin — they're collected here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The kit ($9):&lt;/strong&gt; &lt;a href="https://junghamin.gumroad.com/l/solo-operator-ai-kit" rel="noopener noreferrer"&gt;The Solo Operator AI Kit — 52 AI Prompts &amp;amp; Client Templates for Freelancers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Store page (free prompt downloads plus the full kit):&lt;/strong&gt; &lt;a href="https://junghamin.gumroad.com" rel="noopener noreferrer"&gt;junghamin.gumroad.com&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No subscription, no community to join. Just the files.&lt;/p&gt;

&lt;p&gt;If you'd rather try before buying, the &lt;strong&gt;free starter pack&lt;/strong&gt; — &lt;a href="https://junghamin.gumroad.com/l/free-ai-prompts-for-freelancers" rel="noopener noreferrer"&gt;10 Essential AI Prompts for Freelancers&lt;/a&gt; — is the $0+ preview of the same kit.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>freelancing</category>
    </item>
  </channel>
</rss>
