The problem
Real work starts with reading something you didn’t write. A client’s industry before the discovery call. A competitor’s site before the proposal. A report somebody forwarded with “thought this might be relevant.” Nobody hands a solo operator a research assistant, so the reading happens badly: skimmed, half-absorbed, the kind where you remember a vague shape but not the one sentence that mattered.
If you’re a fractional exec or consultant, every new engagement opens with a stack of material you’re not getting paid to read, you’re getting paid for the judgment after. If you run a function alone inside a company, the analyst report and the competitive deck arrive in the same week as everything else, and you’re expected to have an opinion on both by Thursday.
The volume is annoying. What it costs you is worse: the claim you half-remember and can’t find again, the thing two sources disagree on that you never noticed because you only read one, the question a document already answered on page four.
What’s inside
Five workflows. Each one is a copy-paste prompt with paired worked examples (one for a solo professional, one for a corporate team-of-one) and customization tips.
- The source intake & skim pass. Paste a document, get an honest verdict: full read, skim summary enough, or skip, with reasons.
- The deep-read extractor. Key facts, claims worth scrutiny, and quotes worth keeping, pulled from one long document, with what’s missing flagged too.
- The multi-source synthesizer. Cross-check several sources on one question and surface where they agree, where they genuinely conflict, and the gap none of them cover.
- The question-driven research pass. A real question plus your raw material, answered directly, with citations and an honest confidence rating instead of a generic summary wearing the shape of an answer.
- The weekly research digest. What you actually learned this week, what changed your mind, and what’s still open. The reading feed of your command center.
Every workflow includes the copy-paste prompt, where to fill in your specifics, what to expect from the output, and paired examples for both a corporate operator and a solo consultant.
What this is not
Not a course. Not a community. Not a subscription. Not a tutorial on what AI is. It assumes you already have an approved AI tool and you know how to type into a chat box. It also does not pretend AI replaces your judgment. You decide what’s worth reading and what to do with what comes out. The AI does the part that used to require a research assistant: reading the whole document with the same attention every time, including the paragraph where two sources quietly disagree.
How it works in your tools
No integrations. No file uploads. No “connect your drive” step. You copy text out of a document, article, or report, paste it into the AI tool you already use (Claude, ChatGPT, or Gemini), and get structure back. Nothing you read leaves your hands until you paste it somewhere.
The kit builds on the same three context files you set up in the free Foundation Kit, so the output sounds like you instead of a generic AI. If you haven’t set those up yet, start with the Foundation Kit first.
Format
Lives in your Solo Operator OS members area as copy-paste workflow pages, yours to keep with no expiry. Each prompt block is structured so you can copy it verbatim, instruction first, then the brackets you fill in, then the expected output shape. No PDF to lose, no file to keep in sync. The version in your members area is always the current one.
Who this is for
You run real work alone: a consulting practice, a fractional book of clients, a one-person service business, or a full corporate function with no team under you. Reading before you can do the actual work is a tax you pay alone. This kit is the system, not the tips.
It pairs with the free Foundation Kit (the context files every workflow reads from) and the Meeting and Inbox Intelligence kits, a third feed into the same command center. It also stands alone just fine.
What’s next
This is the reading feed of the Solo Operator OS, the fourth kit in the catalog. The catalog gets built from what people actually ask for, so there’s a short feedback form at the end of the kit. If it’s missing the workflow you needed, that form is how it gets made. Tell me what to build next.