Portfolio & Case Studies
The portfolio is always two years old. Not because the recent work is worse — it is better — but because writing a case study means going back into a finished project and reconstructing why you did what you did. The brief is in one place, the revision history in another, the reason you killed the first direction is in a Slack thread from March. That reconstruction takes a day, and a day of unbillable work loses to a paying client every single time.
Skynet already has the material. If the project ran through it — the brief, the feedback rounds, the decisions — that history is in memory, and the case study can be drafted from it rather than remembered. It reconstructs the arc: what the client needed, what you tried, what you chose, what happened. The narrative and the point of view are yours to shape. The digging is not.
How it works
Reconstruct the project arc
The agent pulls the brief, the direction you chose, the ones you rejected, and the pivotal feedback into a single timeline. The story of the project, assembled from the record rather than from memory.
Find the real decision points
Good case studies are about choices, not screenshots. Skynet surfaces the moments where the project turned — the direction you killed, the constraint that forced the solution — because those are the parts a prospective client actually reads.
Draft in your voice
Point it at case studies you have already written and it matches how you write, not a generic template. Every claim is traceable to what actually happened on the project.
Cut it for each channel
One project, several shapes: the long-form site page, the short portfolio entry, the social version. The agent drafts each from the same source so they stay consistent.
Build it from a prompt
Ask for the project’s story, not a description.
The work you did last quarter ends up in front of prospective clients while it is still recent. And because the draft is built from what actually happened, you are editing a real story rather than trying to remember one.