Telling Technology · Learning in public
All episodes
EP.26 — THE PROPOSAL
The consulting pipeline, on autopilot

My AI found a lead I'd let go cold — and wrote the proposal by morning

The overnight audit flagged a proposal I'd sat on for five weeks. By the time I woke up, the AI had workshopped the pitch three ways and generated the full styled proposal. A human just has to hit send — deadline tomorrow.

Split scene: last night's overnight audit report on the left, a finished aurora-teal proposal page on the right, an arrow of light connecting them.
⌁ audit → pitch → proposal · one overnight session
It started at 01:00, with a line I'd been avoiding for five weeks.
01 The overnight flag

The audit surfaced a five-week-old lead

Last episode, an overnight workflow audited my whole workspace and filed a ranked action list before coffee. This morning the #1 highest-leverage item wasn't a bug or a stale repo — it was a consulting proposal I'd let go quiet for five weeks. The audit put it at the top of the board, with a hard deadline attached.

claude code — desktop
> Read last night's overnight audit. What's the single highest-leverage action?
Top of the list: #1 — "Send the [client] proposal before deadline. The only finished, tailored, ready-to-send doc in the whole pipeline. Verify spelling + From/signature, tighten the copy, send. Highest leverage-per-minute on the board." Five weeks stale. Hard deadline 2026-07-02.
The overnight audit's ranked action list, with the flagged proposal at #1 and the client identity redacted to a grey block.
action item #1 · redacted
The exact line the audit surfaced — client identity stripped.
02 Three drafts to the positioning

Workshopping the pitch: be the doctor, not the pharmacist

A proposal that's five weeks late can't just be resent — it needs a reason to land. So I had Claude push me through three iterations of the positioning. The winner led with proof instead of credentials: AI can build almost anything now; the edge is knowing what's worth building. The pharmacist hands you what you asked for. The doctor tells you what you actually need.

claude code — desktop
> Here's my pitch. Push me like a coach — is this how an AI operator should position? Three passes.
v1 led with tools and CV — cut it. v2 led with the problem — warmer. v3 lands: lead with a result you already shipped, then name the constraint worth fixing. Positioning line: "AI can build almost anything now — I know what's worth building." Doctor, not pharmacist.
Side-by-side of pitch v1 (credentials-first, crossed out) and v3 (proof-first, checked), with the doctor-not-pharmacist positioning.
v1 → v3
Same lead, opposite opening: credentials out, proof in.
03 One session, full proposal

Claude generated the whole thing — page and outreach

With the positioning locked, one session produced the deliverable: a full HTML proposal in the same aurora-teal design language as this site, plus a short Swedish outreach message to go with it. It's served from the local AIOS machine — the same box that flagged the lead now hosts the answer to it. From cold line to ready-to-send in a single sitting.

claude code — desktop
> Turn the v3 positioning into a full proposal page in the aurora-teal style, plus a short Swedish outreach message.
Built proposal.html — aurora-teal, constraint → KPI → build, one CTA. Wrote a 5-line Swedish intro to paste into the outreach. Both live on the local server. Ready. Yours to send.
The AI-generated proposal page in aurora-teal style, with client name and company redacted to placeholders.
served locally · redacted
The finished proposal, on the machine that flagged the lead.
⚠️

The human still hits send

The AI found the lead, sharpened the pitch and built the page — it did not send anything. A real proposal goes to a real company, so the client's name and copy stay private until I send it tomorrow. Everything on this page is deliberately [redacted]: the loop is the story, not the customer.

04 The loop, in four frames

Discover → sharpen → build → send

Four receipts from one overnight run: what the audit caught, the line that reframed the pitch, the message that goes with it, and the finished page. Tap any image to enlarge it and read the exact prompt that drew it.

BUILT OVERNIGHT · SENDS 2026-07-02

The loop closes: AI finds it, AI drafts it, a human sends it

A stale lead I'd have forgotten went from #1 on an audit board to a finished, tailored proposal in one overnight session — pitch and all. Tomorrow it goes out. That's the consulting pipeline running on autopilot, right up to the one step that should stay human.

The finished aurora-teal proposal page ready to send, client details redacted.
flagged 01:00 · pitched + built same session · human sends 2026-07-02
06 Steal this

Steal the loop: audit → action list → first draft

The pattern is portable — an overnight audit that ranks your real work, then a session that turns the top item into a finished first draft. No client data here; the identity stays private and the loop is the part you can copy. Everything in this series is free and open.

method constraint → KPI → build pattern overnight audit → ranked actions positioning doctor, not pharmacist design aurora-teal proposal page
try the method Ask your AI: "What's the one thing I've let go cold that I should ship this week?"

Want the loop pointed at your pipeline? Mail jacob@skogstrom.se — one call, no pitch.

Next episode

Tomorrow it goes out. Does it land?

The AI found the lead, wrote the pitch, built the proposal. Tomorrow a human hits send — and we find out what happens when an autopilot pipeline meets a real client, and whether "my AI found it" beats "I forgot about it."

Darkened teaser of the AIOS system that ran the overnight loop.
drops when the reply lands · follow so you don't miss it