# Write your website from how the work really gets done Version 1.1 · Kramaniti Kosh > How to use this file: fill in the Working template section below. It opens in any text editor, or you can paste the whole file into ChatGPT, Claude or Gemini and ask it to help you fill it in for your business. ## Intended outcome A plain-words draft for one website page that describes what the business actually does, step by step, with every promise on the page traced back to a step the team can deliver today, softened, or taken out. ## Before you begin - One page you want to write or fix (a home page section, a service page, a booking or ordering page) - The person who does the work that page describes, and 20 to 30 minutes of their time - The page as it reads today, or the lines people have been suggesting for it ## How to use 1. Sit with the person who does the work and write down how a real job runs from first message to finish: what the customer sees, what happens behind the scenes, and who does each step. 2. List every promise the page makes or wants to make. Next to each one, write which step makes it true and what shows it. Mark each promise as keep, soften, remove or ask first. 3. Write the page in plain words using only the promises you kept or softened. Have the named owner read it against the steps before it goes live. ## Working template ## Page details Business: Page being written (name and web address if it exists): Who this page is for (the customer in one line): What they want to get done when they land here: Person who does this work day to day: Person who approves the page before it goes live: ## How the work actually runs Describe one real job from start to finish. Write what you do now, not what you plan to do. Step 1: - What the customer sees or does: - What happens behind the scenes: - Who does it: Step 2: - What the customer sees or does: - What happens behind the scenes: - Who does it: Step 3: - What the customer sees or does: - What happens behind the scenes: - Who does it: Add more steps the same way until the job is finished. Steps that still depend on one person’s memory or availability: What the customer needs to give you before you can start: What you do not do, or send elsewhere: ## What you can honestly promise List every promise the page makes or would like to make. Speed, quality, price, coverage area, results and “best” or “only” all count. Promise 1: - Promise as written: - Which step makes it true: - What shows it (a record, a sample, a written policy): - Decision (keep, soften, remove or ask first): Promise 2: - Promise as written: - Which step makes it true: - What shows it (a record, a sample, a written policy): - Decision (keep, soften, remove or ask first): Add more promises the same way. Customer names, photos, reviews or work samples you want to show, and whether each customer has agreed in writing: ## Plain-words page draft Headline (what you do, for whom, in one line): What we do (two or three sentences a customer would say back to you): How it works (one line per step, taken from the steps above): What we need from you: What we don’t do: Next step for the customer (call, WhatsApp, form, visit): ## Stop rules - Do not put a promise on the page that no step above makes true. Soften it or take it out. - Do not invent customer numbers, years of experience, delivery times, ratings or results. If you have not checked it, leave it blank or say less. - Do not use a customer’s name, logo, photo, review or work sample without their written agreement. - If the page mentions prices, refunds, guarantees, health, safety or legal matters, the named approver checks those lines before anything goes live. - Write for the customer who arrives, in words they would use. If a line needs explaining inside the team, it needs rewriting for the page. ## Demonstration This is an illustrative scenario, not a client case study or a measured result. Do not reuse its details as facts about your work. A sample family-run printing press in Bengaluru, run by a father and his son, prints visiting cards, brochures and product labels for local shops and small brands. Orders arrive on WhatsApp and by walk-in. The son wants a services page for the new website, and a friend’s draft opens with “Same-day printing, best quality in Bengaluru.” ### Sample inputs Demonstration inputs only. No order volumes, turnaround times or prices are used. From a talk with the father, who checks every file: customers send artwork on WhatsApp; he checks the file for size, bleed and spelling; a proof goes back for the customer to approve; printing starts only after approval and part payment; finished jobs are picked up or sent with a local courier. Some jobs can be finished the same day if the customer approves the proof early. Larger label runs depend on paper stock. ### Example output #### Page details [Fact within this demonstration] Page: Printing services. For: shop owners and small brands who need cards, brochures or labels printed. Person who does the work: the father, who checks every file. Approver: [Name the owner who signs off the page]. #### How the work actually runs [Fact within this demonstration] 1. Customer sends artwork on WhatsApp or brings it in. 2. The father checks size, bleed and spelling. 3. A proof goes back and the customer approves it. 4. Printing starts after approval and part payment. 5. Pickup or local courier. Step 2 depends on the father alone. #### What you can honestly promise “Same-day printing”: [Inference] true only for some jobs when the proof is approved early. Decision: soften to “Some jobs can be ready the same day if you approve the proof by [time the owners confirm]. We’ll tell you when you order.” “Best quality in Bengaluru”: no step or record shows it. Decision: remove. Replace with what the team actually does: “Every file is checked by a person before it prints.” Logos of shops they print for: no written agreement yet. Decision: ask first. #### Plain-words page draft Headline: Visiting cards, brochures and labels printed in Bengaluru, checked by a person before they print. How it works: Send your artwork on WhatsApp. We check the file and send you a proof. You approve it, and we print. Collect it from the shop or we send it by courier. What we don’t do: [Fill in with the owners, for example design from scratch]. #### Stop rules applied [Recommendation] Keep the file check described as it really runs, and name a backup for step 2 before promising same-day work more widely. The father reads the draft against the steps before the son publishes it. This recommendation is not the business’s decision. ## Quality check The page describes one real job as it runs today; every promise on the page points to a step or a record; unsupported promises are softened or removed; no invented numbers, ratings or results appear; customer names, logos and reviews have written agreement; the named approver has read the draft against the steps. ## Limits and human review The template helps the page match how the work runs; it does not check advertising, consumer or data protection rules, and it does not prove that the business will deliver every time. A filled template is not approval to publish the page, quote prices or show customer work. Keep consequential actions with the named human owner. ## Edition notes New in Kosh at version 1.1. Provider-neutral Markdown instructions; no installation or platform compatibility is implied. Runtime behaviour has not been verified across AI providers. Reuse terms have not yet been published. Background reading: [Translate the Workflow, Then Write the Page](/insights/translate-the-workflow-then-write-the-page/). Keeping what you say to customers in step with how the work runs is part of Kramaniti’s [Complete Lifecycle Retainer](/retainer/).