| Question | Why it matters | |----------|----------------| | (e.g., a product, a software component, a dataset, a research paper, etc.) | Knowing the subject lets me focus on the right details (specifications, performance, methodology, etc.). | | What’s the purpose of the report? (e.g., internal decision‑making, marketing, technical documentation, academic review) | The tone, depth, and format differ a lot between a marketing brief and a technical audit. | | Who will read it? (e.g., engineers, managers, customers, investors) | Audience determines the level of jargon, visual aids, and emphasis. | | What key sections do you want? (e.g., executive summary, features, benchmarks, pros/cons, recommendations, future roadmap) | I can include or omit sections based on what’s most useful to you. | | How long should it be? (e.g., 1‑page cheat sheet, 2‑page executive summary, 5‑page deep dive) | Helps me gauge how much detail to provide. | | Any specific data or sources you already have? (e.g., performance metrics, user feedback, market analysis) | I can incorporate those directly rather than recreating them from scratch. | | Preferred format? (plain text, markdown, PDF‑ready markdown, slide‑style bullet points) | I can output in the format that’s easiest for you to share or publish. |
Look at the original packaging or the underside of the device for a brand name or manufacturer logo. bakkybksd015 15avi best
Possible next steps if you have the file: | Question | Why it matters | |----------|----------------|