Product Definition: The Client Context Project — DFY Claude Project
Rewyse Phase 1 (product-idea). Cole, 2026-08-10. Working name — final name is Kathryn's.
Model: Structured like OTO2 — "DFY Claude Project — Practice Operating System" (the delivery mold that already builds cleanly). Done-for-you Claude Project the buyer stands up themselves: Project Instructions + a curated skill bundle + a conversational intake, delivered as a Notion setup page. NOT a browsable database product.
Type: DFY Claude Project (Project Instructions + skill bundle + intake that builds the buyer's client files)
Niche: Horizontal — any owner who does client work. No vertical in the product, the copy, or the name.
ICP: Solo and very small service operators who carry every client in their head. Coaches, consultants, creative and professional service providers. They are the bottleneck; the work is fine, the context is scattered across email, notes, call recordings and memory.
Value Proposition: Every client you have, held in one place, so you walk into any call already prepared — and never rebuild the context from scratch again.
Funnel Position: OTO2-tier (~$97) or a standalone front-end. Kathryn's call — see Open.
Why this product and not another one
Four hundred people raised their hand for exactly this. The Client Intelligence Brief opt-in is the single largest group on the list — 400 of 645 — and what it offered was take a pile of client correspondence and give me something I can walk into a call with. That is the largest verified statement of demand anyone on this list has made.
CIB is a one-shot. This is the standing version. The brief is something they run once, on one client, when they're already behind. The product holds every client permanently, so the brief is on tap instead of reassembled under pressure. Same buyer, same pain, next rung.
It matches who actually bought. Across ~90 buyer and opt-in records read on 2026-08-10, the identifiable business domains are mostly solo coaches, consultants and small service operators. Accounting and tax practices are 4–5 of them. A product built on advisory or CPA workflow would be aimed at the wrong audience; this one is aimed at the audience that converted.
It reuses a proven mold. The OTO2 DFY Claude Project builds cleanly and delivers cleanly. The failure of the Advisory Onboarding build was scope and finishing, not the format.
The 3 pieces (mirrors the OTO2 DFY model)
| Piece | What it is | Where it goes in Claude |
|---|---|---|
| Project Instructions | How the Project thinks about client work — what a client file holds, what it never invents, how it reports what it doesn't know | Pasted into Project settings |
| The skill bundle | The recurring jobs, below | Uploaded to Project Knowledge |
| The intake | A conversational build that turns whatever the buyer already has — emails, notes, transcripts, a CRM export — into one client file per client | Run in the Project on day one |
The skill bundle — the recurring jobs
- Build a client file — the intake, run once per client, and re-runnable as things change.
- Brief me before this call — the CIB, now standing: pulls that client's file plus anything new and returns what changed, what's open, what they last asked for.
- Catch me up — after time away, per client or across the book.
- What did I commit to — surfaces promises made across correspondence, which is where trust gets lost.
- Draft the follow-up — the post-call note, from what was actually said, in the owner's voice.
Five skills. Small enough to finish, big enough to be worth $97.
What the buyer receives
- A Notion setup page: create your Project → paste the Instructions → upload the skills → run the intake on your first client.
- The five skill files.
- One worked example so they can see the output before doing the work.
Assumptions, stated rather than resolved
These are the places this brief is running ahead of confirmed data. None of them block the build; all of them are cheap to correct later.
- The audience read comes from a partial sample. ~90 of 645 records, and over half the list uses personal email so no domain signal exists at all. The read is directional. The product is deliberately horizontal so that a wrong vertical guess costs nothing.
- CIB opt-in intent is inferred from what they opted into, not from asking them. It is the strongest signal available and it is still an inference.
- Price is assumed at the OTO2 tier because that mold exists and converted 16 buyers. Not validated for this product.
- The buyer has material to load. Someone with no written client correspondence gets less from day one. The intake is built to work from thin inputs and say so rather than invent.
What would sharpen it, without blocking it
One question to the list — what kind of work do you do — writing to a new subscriber field. It does not gate this build. It sharpens the copy, the examples, and every product after this one.
Build plan — Rewyse
| Phase | Status |
|---|---|
| 1. product-idea | This document. Awaiting Kathryn's greenlight. |
| 2–7. expert-profile → content-blueprint → write-prompt → test-content → generate-content | Not started |
| 8. design-product (Notion setup page, OTO2 mold) | Not started |
| 9–10. product-qa → expand | Not started |
Estimate: the five skills and the setup page are one build cycle. The mold is known and the source pattern exists.
Open — Kathryn's call, and only these
- Price and slot. OTO2-tier (~$97) or a standalone front-end.
- The name. "The Client Context Project" is a working name from Cole. Naming is Reid's lane with Kathryn.
Everything else is decided in this document and does not need her.