Everyday admin for a one-person business
The quote, the chase-up, the refusal and the onboarding note, worked through: what to paste, what to hold back, and what to fix on the second pass.
The billable work finishes and the admin does not. A one-person business has nobody to hand the messages to, and four come round again and again: a quote for the person who asked roughly how much, a chase-up on an invoice that went past its terms a fortnight ago, a no to a job you cannot take, and the note a new client gets explaining how you work.
None of the four is long. Each is a small negotiation compressed into a paragraph, which is why they resist being written at speed. A quote fixes your scope for six weeks. A chase-up has to be firm enough to get paid and calm enough to keep the client. A refusal has to close one door and leave the relationship open. An onboarding note sets rules you will be enforcing in week three, when the client asks for a fourth round of revisions.
A chat model is useful on all four for one reason: it produces a version you can react to, and reacting is faster than starting. It also fails predictably: it widens scope, it offers things on your behalf, and it invents consequences you never wrote down. Each section below runs the same four steps: what you paste, what you ask for, what comes back wrong on the first pass, and the fix.
A quote is a scope document with a number at the end
Asking for a quote and letting the model decide what the job is delegates the one decision you cannot delegate, because the quote is what you will be held to.
What you paste. The client's own description of the work, with their name and company stripped out. Your rough bullets of what you would actually do. Your rate and how you charge it. The earliest date you could start.
What you ask for. A quote in five parts: what is included, what is excluded, the price, the timeline, and what you need from the client before day one. Then the instruction that does most of the work: list separately anything you assumed.
What comes back wrong. The scope grows. A brief that said "refresh the homepage copy" returns a quote covering the homepage, the about page and a short tone-of-voice guide, because the model is optimising for a document that looks complete. The exclusions soften in the same pass, into lines like "additional pages can be discussed", which is the sentence that gets you writing the about page for nothing.
The fix. Dictate the exclusions yourself and close the scope in the prompt: use only the deliverables in my bullets, add none of your own, and list anything you had to assume. That assumptions list is worth more than the quote itself on a first pass, because it surfaces what the client left vague. How many revision rounds. Who supplies the photographs. Whether the deadline is the launch or the handover. Those are the questions to send back before you send a number. Ask for the price as a figure with its basis stated rather than a paragraph justifying it, because prose written in defence of a price invites negotiation of the prose.
Three chase-ups, written on a calm day
Most chase-ups get written on the day you notice the money has not arrived, the worst possible day. Write all three in one sitting, while you are still indifferent, and keep them somewhere you can reach on the dates. Nothing here sends them for you; the hard part was never the sending.
What you paste. Invoice number, amount, issue date, the payment terms exactly as they appear in your own terms, and the text of whatever you have already sent.
What you ask for. Three messages that escalate: the first the day after the due date, the second a fortnight later, the third referring to the late-payment clause as you quoted it. Each states the ask in its opening sentence.
What comes back wrong. Two things, reliably. The tone arrives pre-apologised, opening with "hope you are well, sorry to be a pain" and burying the amount and the overdue date in the third paragraph, which turns an administrative fact into a favour you are asking for. Then the third message invents a consequence: interest at a rate the model chose, a referral to a collections agency, a threat to pause work. None of that is in your terms, and sending a remedy you have not got is the one failure here that can cost you real money.
The fix. Paste the clause and instruct that no consequence may appear unless it is in that text. Then constrain the opening: first sentence is the invoice number, the amount and the days overdue, with no apology anywhere in the message. What you may charge for being owed money is a question for your terms and your jurisdiction, so check it rather than letting a model fill the gap with something plausible. The flat version is also easier to send, and the chase-up that sits unsent is the one that costs you.
The refusal, and the favour it offers on your behalf
There are three kinds of no in a small business and they need different messages. Out of scope, which points somewhere else. No capacity, which points at a date. Below your floor, which points at nothing and still has to stay warm.
What you paste. The request, one line on why you are declining, and the single thing you will offer instead: a start date, a referral, or nothing.
What you ask for. Four sentences. The decline in the first. One alternative, the one you named, and no other. No apology longer than a clause.
What comes back wrong. It gives away your time. "Happy to jump on a quick call and talk through the options" turns up in nearly every first-pass refusal, and you never offered a call. The same instinct produces a free look at their brief, a discount you did not authorise, and a closing line that reads as availability. Conceding something is the easiest way to make a refusal sound warm, so that is what you get.
The fix. Put the boundary in the prompt as a prohibition, because an instruction to be brief will not catch it: offer no call, no discount, no review, no free work, and name the one alternative on the table. Cap the length while you are there, since every extra sentence is another place to hedge and hedging reads as an opening. For the budget case, add one line: decline without repeating their number back at them. Quoting a budget back at someone reads as a comment on what they can afford, and that version ends a relationship rather than pausing it.
Write the onboarding note once and reuse it
This is the one with compound interest, because the same note goes to every client you take on. It covers the hours you work and when you answer messages, how many revision rounds are included, what you need before day one, how you invoice, and how feedback should reach you.
What you paste. Your own rules as scrappy notes, in whatever order they occur to you.
What you ask for. A client-facing note in plain language, second person, under 300 words, no headings.
What comes back wrong. The voice inflates. "Our team aims to respond within 24 business hours" is a sentence written by a business of forty, and you are a business of one. Alongside it comes policy the model added from the onboarding documents it learnt from: a cancellation fee, a 48-hour approval window, a clause about materials you never mentioned. It reads as authoritative, which is why it slips through.
The fix. Say you are one person, ask for "I" and "you" throughout, and require it to flag any rule it added rather than folding additions in silently. Then read the result as the client would. Anything that lands like a threat in the first hundred words belongs in your contract rather than your welcome note.
Keep the finished version as text you can paste. Uploading a Word document is a paid-plan feature, and free-plan attachments run one per message at 10MB with three a day, while pasted text has none of those limits. Free accounts get 50 messages every 24 hours, which is a lot of admin.
The four jobs compared
The four differ less in how they are written than in what they need from you before a model can help. The columns people skip are the last two.
The job | What to paste | What to hold back | The answer to prefer |
|---|---|---|---|
A quote | The brief in the client's words, your scope bullets, your rate, your earliest start date | The client's name and company, anything sent to you in confidence | One that lists what it assumed. Models with a thinking step carry a Reasoning chip on the info card, and that step is worth reading |
A chase-up | Invoice number, amount, dates, your payment terms word for word, the message you already sent | Anything about the client's finances or their other suppliers | Short and literal, quoting your clause rather than summarising it. Straight-through answers suit this length |
A refusal | The request, your one-line reason, the one alternative you will offer | Your real reason if it is about them, the names of your other clients | The one that followed the constraint exactly. Length is the failure mode, so prefer the shorter draft |
An onboarding note | Your working rules as rough notes, nothing else | Anything client-specific, since this is a template you reuse | One that holds a long list of constraints at once and adds nothing. Ask it to flag every addition |
Your client's own material and their identifying details are not yours to hand to anyone, so strip them before you paste, and all four jobs work perfectly well on a placeholder name. On our side: we do not train on your conversations, what the provider behind a given model does with them varies by model, and the models where we know of a difference carry a notice on their info card in the picker.
Rates, terms and turnaround, typed once
Retyping your day rate into every quote is how the wrong number eventually goes out. Saving it once is a paid feature called memories: the brain icon on the message bar opens Chat memories, Add memory takes a title and a body, and the Memories tab in Settings can set one to "Include in all new chats by default". Put your rate, minimum engagement, payment terms, standard turnaround, the things your quotes always exclude and how you sign off into one memory, marked as a default. Every new thread then opens with your numbers in it, instead of you fetching them from an old email and fetching last year's by mistake. Memories run to 200 on Pro and are unavailable on free accounts; the plan ladder is on the homepage.
One discipline comes with it. A memory is a copy of the truth and copies go stale, so the day you raise your rate, edit the memory before writing the next quote. Same for terms: if your late-payment clause changes, the version your chase-ups quote changes with it, or you will send a confident paragraph citing a clause you no longer use. Client-specific context belongs in a folder per client rather than in the shared memory.
When the message is awkward, get two versions
Some of these messages are genuinely difficult. The refusal to a client you like. The chase-up to someone who may have a real problem. The quote priced above what they were hoping for. One draft is not enough to judge those, because a single version gives you nothing to measure fluency against.
Ask the same question twice, with two different models. On any answer, Try Again opens a picker and creates a new thread with an alternative response, so the second version lands in its own thread while the first stays where it was. There is no view that places them next to each other, so you read one, switch threads in the sidebar, and read the other. The other route is to stay in one thread and pick a different model for your next message, and the history carries over when you do. The picker holds 59 models from 17 providers, 22 of them free, so the second opinion comes from a different company's model rather than the same one twice.
Then judge both against one test: could you defend every sentence if the client quoted it back to you in three months? The smoother of two refusals usually got smoother by conceding something, and the warmer of two chase-ups often dropped the date. The version you can defend is frequently the blunter one, and sending it gets easier once you have read the alternative.
For each of these messages: decide the part that commits you, then let the model draft around it. Keep the prompt that worked, because all four come round again next month, and check the numbers in your memory before they do.