The Real Cost of Rebuilding AI Context (And How to Stop Paying It)

#ai #llm #productivity

Here's a calculation most people haven't done:

How much time per week do you spend getting an AI back up to speed on what you're working on?

I did this calculation six months ago. The number was uncomfortable.

The baseline

At the time I was doing about 8 meaningful AI-assisted work sessions per week — writing, research, code, analysis. Each session started with some amount of context-setting: explaining the project, pasting in relevant documents, reminding the AI of decisions we'd already made, re-establishing the constraints.

I timed it. The average context-reconstruction overhead per session was 12–15 minutes.

8 sessions × 13 minutes = ~1.75 hours per week on context reconstruction.

That's one full work session. Every week. Just getting back to where I was.

What you're actually reconstructing

Context reconstruction isn't a single task. It breaks down into:

1. State recovery — "Where were we?" You paste in the document, scan for where you left off, remind yourself what you were trying to do. Even if you remember perfectly, the AI doesn't.

2. Decision archaeology — "What did we already decide?" The thing you're about to ask the AI might be something you explicitly resolved two sessions ago. Without a record, you won't remember. You'll explore the same territory again.

3. Constraint re-establishment — "What are the rules?" The specific requirements, client preferences, or non-obvious constraints that shape this work. They live in your head. Every session, you rediscover how many of them matter when the AI violates them.

4. Approach rejection — "What didn't work?" The approaches you've already tried and discarded. Without a record, the AI will suggest them again. You'll spend time re-evaluating options you've already closed.

Each of these has a time cost. Together, they're the overhead that prevents AI-assisted work from compounding.

The ROI of a session-state protocol

The fix is simple: write a structured note at the end of every session. Not a transcript — a state snapshot.

Five fields:

## Objective
[What this project is trying to accomplish]

## Active constraints  
[Non-obvious rules that shape the work]

## Decisions made
[What's been decided, with brief rationale — especially what was rejected]

## Open questions
[What's still unresolved]

## Next step
[The concrete next action, specific enough to act on immediately]

This takes 3–5 minutes to write at session close. At session open, the AI reads it. Context-reconstruction time drops from 13 minutes to 90 seconds.

Weekly time saved: ~1.5 hours. Per year: ~75 hours. At any reasonable hourly rate, the compounding value is significant.

The less obvious ROI: decision quality

The time calculation understates the value. The bigger return is decision quality.

When you have a record of why you made previous decisions, you make better decisions on subsequent sessions. You don't re-open questions that are already closed. You don't lose constraints in the noise. You don't repeat failed approaches.

The AI's output quality also improves — not because the model got better, but because it's receiving better context. A well-contextualised session with an average prompt outperforms a poorly-contextualised session with a perfect prompt.