Build Log Outline Prompt
insighttech.blog/library

Use this to turn a rough project brain-dump into a submission-ready
Build Log outline before you write the full draft. Paste your own notes
in place of the bracketed section.

---

PROMPT:

I built something and want to write it up as a "Build Log" — an honest
case study, not a highlight reel. The site's standard is: what I built,
who/what it was for, what actually broke along the way, and the result,
stated plainly. Failures are expected content here, not something to
hide.

Here are my raw notes:

[PASTE YOUR ROUGH NOTES, VOICE MEMO TRANSCRIPT, OR BULLET LIST HERE]

Turn this into a Build Log outline with these sections:

1. ONE-LINE OUTCOME SUMMARY — a single concrete result stated as a
   number or fact where possible (e.g. "Cut order-taking time by 40%",
   not "improved efficiency"). This becomes the card's outcome line.

2. THE PROBLEM — 2-3 sentences on what was broken or missing before,
   and for whom.

3. WHAT I BUILT — the actual stack/approach, specific enough that
   another builder could roughly reproduce the decision, not just the
   category of tool used.

4. WHAT BROKE — at least one real failure or wrong turn. If nothing
   went wrong, say so honestly rather than inventing drama — but push
   back on me if my notes are hiding an obvious rough patch.

5. THE FIX — how the failure was resolved, or what's still unresolved
   if it isn't yet.

6. THE RESULT — expand on the one-line summary with the actual before/
   after, even if the numbers are rough estimates (say so if they are).

7. LESSON FOR OTHER BUILDERS — one takeaway that's useful to someone
   about to attempt something similar, not a generic "always test
   thoroughly" platitude.

Also suggest: which category tags from insighttech.blog fit best
(ai-agents, aeo-geo, seo-search, automation-workflows, ecommerce-ai,
tools-frameworks, failures-fixes), and whether this reads more like a
Build Log (3-10 min) or should be trimmed down to a Quick Win (1-3 min)
instead.

---

Notes:
- Free submissions can't include company names, product names, or links
  in the body — keep the outline generic enough to pass that check, or
  flag anything that needs to be genericized before you submit.