Product notes often contain the facts but not the explanation a buyer needs. Dimensions, materials, and usage details must become clear copy without turning into claims the product cannot support.
OGAD (Off Grid AI Desktop) can help you draft descriptions from your saved product notes with a local model. Give it verified facts, define the reader, and review every statement before publishing. After setup, the drafting can happen on your computer without uploading the notes to a cloud AI service.
| Download OGAD | Desktop releases |
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
For a small maker or online shop, the useful result is copy that helps a customer understand the item. The model should organise the evidence you provide, not create missing specifications or customer outcomes.
What facts should you prepare first?
Collect the information that is true for the exact product and variant. Keep confirmed facts separate from ideas, supplier statements you have not checked, and copy you are still testing.
Suppose you sell a desk organiser. Your notes include its dimensions, material, compartments, finish, and care instructions. A buyer may want to know what fits, where it can sit, and how to look after it.
| Source fact | Useful question for the description |
|---|---|
| Dimensions | Will it fit the intended space? |
| Compartments | What can the buyer organise? |
| Material and finish | What is the item made from? |
| Care instructions | How should it be maintained? |
| Variant details | Which colour or size does this listing cover? |
Do not turn a material name into unsupported claims about durability, sustainability, safety, or origin. Those need their own verified basis.
What do you need in OGAD?
Install OGAD and download a local text model that fits your computer. Save the product notes in a readable local file. Complete app and model downloads while connected before testing offline drafting.
This workflow uses the free core app on supported Mac and Windows computers. Release 0.0.54-beta.108 also provides Linux beta packages.
Use TXT, Markdown, DOCX, or a text PDF. Plain text or a simple Markdown table is useful for specifications because it makes labels and units easier to review. Scanned supplier sheets need checked text first.
Keep an approved source copy. If different notes disagree about a dimension or material, resolve the difference before using the value in public copy.
How do you make the first description?
Attach the notes to a new chat and ask for a fact table before prose. This gives you an early check that the model read the correct variant and preserved units.
- Choose a downloaded local model in Models > Text.
- Open a new chat and select + > Attach files.
- Add the product notes and any approved voice guidance.
- Wait for processing and inspect the text preview.
- Ask for confirmed facts and missing details.
The document attachment implementation supplies text to the model. It does not independently test the product or verify a supplier’s claims.
Use:
Extract the product facts from these notes. Preserve dimensions, units, materials, variant names, and care instructions exactly. Separate confirmed facts from unclear or conflicting details. Do not add benefits or specifications yet.
Check the table, then provide the approved facts for drafting.
How do you explain benefits without inventing them?
Connect each feature to a use that follows from the facts. A compartment can help separate small items. It does not establish that the organiser will double productivity or eliminate clutter for every buyer.
Ask:
Draft a product description for someone choosing a desk organiser. Use only these approved facts. Explain practical uses that follow directly from the features. Include a short overview, useful details, dimensions, and care information. Do not invent certifications, test results, popularity, guarantees, or customer reviews.
Review every sentence that describes an outcome. Ask what source fact supports it. If the link is weak, make the statement narrower or remove it.
For example, “Three compartments separate pens and small desk items” is supportable if that is how the product is designed. “Creates a stress-free workspace” is a broad result the notes do not establish.
How should you handle missing information?
Leave a visible question for yourself instead of letting the model complete the description from common expectations. A product category does not establish the properties of your particular item.
Try:
Which buyer questions remain unanswered by these notes? List them as questions for me to verify. Do not write plausible answers into the description.
For the organiser, you might need to confirm whether the finish tolerates a particular cleaning method or which dimensions describe the internal compartments. Check the product or approved documentation, then update the source notes.
This creates a better product information record as well as better copy. Future descriptions can start from the same checked facts.
How do you create variants without mixing them?
Draft one variant at a time or provide a clearly structured table. Keep shared facts separate from size, colour, material, or bundle details that change between listings.
Ask the model to identify the variant at the top of its draft. Compare the final specifications with the correct source row before copying the description into your store.
A useful review request is:
Compare this draft with the approved facts for the small natural-finish version. Flag any statement that belongs to another variant, changes a unit, or adds an unsupported claim. Do not rewrite until I review the flags.
The model’s check is another aid, not an independent product inspection. Use your own source record for the final decision.
How do you make the copy fit your store?
Give the model a clear format and tone. Specify the sections you need, the level of detail, and words that do not fit your brand. Keep the buyer’s questions ahead of decorative language.
You might ask for a short opening followed by materials, dimensions, and care. For a technical item, compatibility and limitations may matter more than a lifestyle paragraph.
Read the draft aloud. Remove repeated benefits, vague superlatives, and sentences that do not help someone choose or use the item. Keep necessary limits visible rather than hiding them in a distant note.
What should you check before publishing?
| Check | What to verify |
|---|---|
| Product identity | The description matches the exact item and variant |
| Specifications | Numbers and units agree with the approved source |
| Claims | Every factual or performance statement has support |
| Care | Instructions are complete and correctly stated |
| Copy quality | The buyer can find the information they need |
Copy the approved text into your normal store editor and review the page there. This workflow does not update your shop, calculate shipping, or certify the product.
Draft one description from facts you trust
Download OGAD and start with one product. Build a checked fact table, draft the description, and review it against the source before publishing.
Keep the model local for the writing stage after setup. Your store, supplier checks, and later sharing have separate connections. The useful result is clearer product copy with fewer unsupported assumptions.