Lesson 14 of 25
The Transmutation of Form
Content and form are separable. The same material can become a plain-English summary, a story, or a sales paragraph - and the prompt that works names three things: the source, the destination form, and who the result is for. The reader is what actually decides the rewrite, which is why "simplify this" produces so much less than "explain this to the tenant who has to sign it".
The real gain here is not the prompt but the pipeline: attach the actual document, photograph the clause in the lease, pull the data from the Sheet it lives in, and send the output to the Doc where it will be edited. Multimodal input matters for this chapter specifically - a photo of the page you were handed is more useful than the retyped paragraph, because the clause above and below it change the reading.
- Attach or photograph the real document, not a retyped extract.
- Tell it not to search during the conversion itself.
- Pull the data from the Sheet it already lives in.
- Send the draft to the Doc where it will be edited.
- Save a recurring conversion as a Gem.
Perplexity version
### THE CONVERSION ### Turn the rental agreement clause below into a three-point summary in plain English. ### WHO IT IS FOR ### A first-time tenant in Hyderabad, not a lawyer, being asked to sign. They will read the three points and nothing longer. They need to know what they are agreeing to and what could cost them money. ### RULES ### * Three points, each one short sentence, spoken register. * No legal vocabulary survives - "indemnify", "hold harmless", "lessee", "demised premises", "invitees" all translated, not restated. * One point must cover "invitees" concretely, including that it can reach to guests brought home. That is the part tenants miss and the part that bites. * State the practical consequence, not the legal mechanism. ### DO NOT SEARCH ### Do not ground this in Google Search. I want this clause read, not general Indian tenancy commentary mixed into it. Search results about standard lease terms will quietly change the reading of my specific wording, which is the opposite of what I need. ### BETTER INPUT - USE IT ### I will attach a photograph of the full page of the agreement rather than only this paragraph. Read it and tell me whether the clauses immediately before and after change how this one should be understood - a limitation of liability or a security deposit clause nearby can alter the practical effect considerably. If the photograph is unclear anywhere, say which words you cannot read rather than guessing them. ### AFTER THE THREE POINTS ### 1. "What this summary leaves out" - what the three points do not carry. 2. "Ambiguous" - any part with more than one reading, named rather than silently resolved. "Any act or omission" is very broad; tell me how broad. 3. "Questions to ask" - two or three things to ask before signing. 4. One line stating that this is a plain-English reading, not legal advice, and that you are not assessing enforceability under Indian law. ### OUTPUT ### Put the summary into a Google Doc called "Lease - plain English" so I can share it with the person co-signing. Save this conversion as a Gem called "Legalese to plain English" - there are eleven more clauses in this agreement. ### THE CLAUSE ### The Lessee hereby covenants to indemnify and hold harmless the Lessor from and against any and all claims, liabilities, damages, and expenses, including reasonable attorney's fees, arising out of or in connection with the Lessee's use and occupancy of the demised premises, or any act or omission of the Lessee, its agents, employees, or invitees.
Perplexity version
### THE CONVERSION ### Turn the data points below into a success story of about 250 words for our internal company blog. Tone proud and inspiring, but earned from the specifics rather than asserted. ### WHO IT IS FOR ### Our own employees, most of whom built this product and know the real story. Anything inflated will be obvious to them, which is the constraint that matters. ### PULL THE REAL DATA ### The six points below are what I typed out, but the actual numbers live in our analytics Sheet, which I am attaching. Use the Sheet as the source of truth and tell me where it differs from what I wrote - if Q3 growth is 287% rather than 300%, I want the real figure and I want to know I had it wrong. ### DO NOT SEARCH ### Do not use Google Search for this. 'ConnectLocal' and 'Latha's Sarees' are generic enough that you will find unrelated businesses, and their details will end up in my internal blog post with a citation attached, which is the hardest kind of error to catch. ### NOTHING ADDED ### No reasons for the growth beyond what the data states. Nothing about the team, the process, late nights or anyone's motivation. No numbers outside the data or the Sheet. No further customers or testimonials. Nothing forward-looking. The Latha's Sarees quote verbatim, attributed exactly as given. Build the story with structure, not embellishment: open on the saree shop whose sales doubled, widen to the growth figure, land on 'Local Discovery' as the mechanism. ### AFTER THE DRAFT ### * "Inferred" - everything the copy implies that the data does not state, including implied causation. The data says the feature was used, not that it drove the growth; if the copy suggests otherwise, list it. * "Discrepancies" - where the Sheet and my typed figures disagree. * One line: the single fact you most needed and did not have. ### OUTPUT ### Draft into a Google Doc called "ConnectLocal - Q3 story" for the comms team to edit, with the "Inferred" list as a comment thread rather than body text so it does not get published by accident.
Perplexity version
### ROLE ### A senior marketing copywriter. ### THE CONVERSION ### Turn the technical features below into one persuasive paragraph of about 90 words for a product webpage. ### WHO IT IS FOR ### A busy working professional in India. Commutes, works from cafes and client offices, takes calls from noisy places, often cannot find a socket. Not reading spec sheets. ### THE RULE ### No technical vocabulary in the output. None of these words may appear: magnesium-alloy, 1.1 kg, 18-hour, fingerprint sensor, AI-powered, noise-cancelling. The numbers go too. Each feature becomes an experience: the weight becomes carrying it all day, the battery becomes not hunting for a socket, the login becomes seconds not lost, the microphone becomes being heard clearly from somewhere loud. ### DO NOT SEARCH WHILE WRITING ### Do not ground the copy in search results. You will find competitor product pages and the paragraph will come out reading like all of them, which defeats the purpose. ### USE THE PRODUCT IMAGES ### I am attaching the product photography that will sit alongside this copy. Look at it and write copy that does not repeat what the picture already says - if the image clearly shows how thin the machine is, the paragraph should spend its words elsewhere. Tell me in one line where the copy and the images overlap. ### AFTER THE PARAGRAPH ### 1. Two alternative opening sentences. 2. "Jargon check" - confirm no banned word appears, and name any sentence that is still a spec sheet in disguise. "Remarkably light" is the number removed; "carry it from meeting to meeting without feeling it" is a translation. 3. "Hardest to translate" - which feature resisted most, and why. The feature that will not become an experience is usually the one the reader cares least about. 4. Avoid "seamless", "effortless", "game-changing", "empower", "unleash". Do not invent features, prices, warranty terms or competitor comparisons, and do not imply speed - nothing in the features claims it. ### THEN, SEPARATELY ### Under a heading "Researched, not in the copy" - now you may search: what claims do Indian consumer protection rules and ASCI guidance restrict in laptop advertising, particularly around battery life stated without conditions? Cite what you find with dates. Keep this entirely out of the paragraph; it is a check on it. ### OUTPUT ### The paragraph and the two alternative openings into a Google Doc called "Laptop page - copy v1" for the web team.