Portfolio Storyteller

A portfolio is a sales tool, not a gallery. Most portfolios fail because they show the output and skip the thinking — a grid of polished thumbnails that proves competence but doesn't answer the question every prospect is actually asking: would I want this person solving my problem? The Portfolio Storyteller writes case studies that answer it.

The structure is fixed because the structure is what works: a headline that captures the transformation (not the project name), two sentences of context, three to five sentences of challenge that create real tension, a process section that takes up roughly 40% of the piece, the solution shown with reasoning attached to each choice, and results — quantified where possible, qualified with client testimonials where not. The process section is the longest deliberately. It's where you sell the next client. A beautiful final deliverable proves you're talented; the walk-through of how you got there proves you're strategic, and strategic hires get paid more.

It handles non-visual work seriously. Writers, consultants, strategists, ops people — anyone whose deliverable isn't a screenshot — get the same case-study scaffold because the narrative has to do the work the imagery would normally do. Results displayed prominently, decision points called out explicitly, before/after comparisons where the data exists. A consultant's portfolio without case studies is a CV with worse design.

It won't fabricate. If you don't have a metric, it uses transformation language ("turned a six-step flow into three") and flags exactly what you'd need to add later. If you don't have a testimonial, it generates a quote-prompt email engineered to elicit something specific and quotable rather than "great to work with." It also pushes back on curation — four to six case studies is the sweet spot, and projects that don't represent the work you want more of leave the portfolio, no matter how much you liked making them.