# Content repurposing demonstration **Prepared by mei so · Fictional self-authored source · Public fictional demonstration** This demonstrates editorial work, not a real client engagement. The source below was invented for this sample. It contains no testimonial, measured result or claim about an actual business. All first-person output is written in the voice of the fictional source speaker, not as a claim about mei so's personal experience. No client campaign has been published; these examples are shared only as a portfolio demonstration. ## Sample brief Audience: independent service-business owners who receive vague project enquiries. Purpose: explain a simple way to clarify a request before quoting. Tone: practical, plain and friendly. Deliverable: three distinct LinkedIn posts and one short newsletter, drawn only from the source. This smaller demonstration illustrates the method; it is not a completed five-post paid package. ## Self authored source article ### Before you quote ask what needs to be done [S1] A project enquiry can be enthusiastic and still be hard to act on. “Can you help with our website?” does not tell you which page needs attention, what is wrong with it or whether the person wants writing, design or implementation. [S2] I use a simple starting point for thinking through these requests: ask about the item, the problem and the deadline. What needs changing? What is not working about it now? When does the person need the work, and what is driving that date? These questions help define the conversation. They do not replace a full brief. [S3] Ask for one concrete example. A link to the page or a short extract can be more useful than a general description. If the material contains customer information, ask for a redacted example instead. You do not need account passwords to discuss what a piece of copy should say. [S4] Before quoting, write back a short summary of what you understand. For example: “You want the introduction and enquiry button on one existing page rewritten. You will add the approved copy to the website yourself.” Ask whether that describes the request accurately. It leaves room for the person to correct you before you price a different job from the one they intended. [S5] Keep questions about missing facts visible. If you do not know the actual service area, price or cancellation policy, mark the gap instead of guessing. A polished sentence can still be wrong. The owner should confirm business facts before the copy is published. [S6] Agree what the first delivery includes and how feedback will work. A single list of comments is easier to work through than a mixture of messages about different versions. This is a preference for organising the work, not a claim that every project needs the same revision policy. [S7] You do not need a complicated intake system to try this. A short email can contain the three starting questions, a request for an example and a scope summary. The aim is a shared understanding of the job. This example makes no claim about how much time it saves or how many enquiries become paying customers. ## Output one ### LinkedIn post A Clarifying the request “Can you help with our website?” is a starting point, not a brief. Before talking about the work, I would ask three questions: - What needs changing? - What is not working about it now? - When do you need it, and what is driving that date? Then ask for one concrete example: a page link or a short extract, with customer information removed. These questions do not answer everything. They give you something specific to discuss before you quote for writing when the person actually needs design or implementation. Try them on your next unclear enquiry. ## Output two ### LinkedIn post B Confirming the scope Before quoting for a website-copy job, send a short summary of what you think the person is asking for. For example: “You want the introduction and enquiry button on one existing page rewritten. You will add the approved copy to the website yourself.” Then ask: “Is that right?” That last question matters. You might be describing a copywriting job while the other person is expecting a finished website update. Let them correct the scope before you price it. The summary can be a few sentences in an email; it does not need a new system. ## Output three ### LinkedIn post C Handling missing facts A polished sentence can still be wrong. If a client has not confirmed their service area, price or cancellation policy, leave a visible question in the draft. Do not fill the gap with something that sounds plausible. “Please confirm the towns you cover” is more useful than publishing a confident claim about places the business does not serve. Ask the owner to check those facts before the copy goes live. You can improve the wording once you know what is true. ## Output four ### Newsletter Subject: Three questions before you quote Preview: Start with the item, the problem and the deadline. An enquiry can sound promising without telling you what the person actually needs. If someone asks for help with their website, start with three questions: What needs changing? What is not working about it now? When do they need the work, and why that date? Ask for a concrete example, such as a page link or a short extract with customer information removed. These questions are a starting point for the brief, not a substitute for it. Before quoting, send back your understanding of the job. If you will write the copy and the owner will add it to the site, say so. Give them a chance to correct the scope. Keep missing business facts visible too. A service area, price or cancellation policy should come from the owner, not a guess. Agree what the first delivery includes and how feedback will be collected. You can try this in a short email. Start with the three questions and build the brief from the answers. ## Source to output map | Output | Source support | Editorial treatment and factual boundary | | --- | --- | --- | | Post A | S1, S2, S3 | Reuses the three-question method and redacted example request. No claim of measured effectiveness. | | Post B | S1, S4, S7 | Preserves the fictional scope example. The quoted summary is an example, not a customer quotation or testimonial. | | Post C | S5 | Turns the missing-facts principle into a distinct post. The towns sentence is an illustrative request, not a fact about a business. | | Newsletter | S1–S7, excluding S3's password detail | Condenses the sequence without claiming results. It omits a detail rather than changing it. | ## Editorial verification - Every substantive claim maps to a labelled source paragraph. - The posts use different angles: intake, scope and factual approval. - No invented statistic, customer, testimonial, quote from a real person, income claim or performance result appears. - The sole scope quotation is retained from the self-authored example and labelled as such. - The source's uncertainty is preserved: these are starting questions, not a complete brief or guaranteed improvement. - No new business policy, response-time commitment or fixed revision entitlement is invented. - Calls to action are relevant suggestions; there is no unsupported sales offer or functioning enquiry link. - The sample's first-person writing belongs to the explicitly fictional source speaker. ## Proposed paid version boundary Pilot scope for project requests: one owned or licensed source up to 3,000 words, five posts up to 150 words each and one newsletter up to 350 words, one audience, one consolidated revision. The owner approves facts and voice before publishing. Indicative price: US$59. Scope, final price, terms and delivery date are confirmed before payment. No transcription, graphics, posting, account access, new factual research or promised engagement results.