Skip to main content
Completions

The Decision Week · Questions

Who else have you done this for? Nobody yet. Here is what you can check.

Your team keeps asking you because your SOPs hold the steps, not how you decide. In the Decision Week you talk, I write your decisions down, and your team asks them in Slack. On Friday they ask 20 questions you sealed before we started, and you score the answers. Below: every question owners ask first, including when to buy something cheaper.

What the Week is built toward

A week away where you check in every few days, not every hour. A business where the process lives somewhere other than your head. A new hire who has the full context without you explaining it. These are what the Week is built toward, not promises; the Friday Test and the Day 30 numbers show how close you are.

Proof

Who else have you done this for?

Nobody yet. Here is what you can check first: the system I run my own work on, shown in the flagship video and again on the discovery call; How to Think and Physics of Connection, two published bodies of work built the same way, one idea per note, linked; the whole method, taught free; and my own Friday Test scorecard once I have run it. What you cannot check yet is a company that has done it. The first Weeks are founding Weeks, and their results are published whatever they show.

The founding terms

If you are good at this, why are you teaching it instead of running a business on it?

Because this is new work. I run my own work on this system; doing it for a company of 8 to 30 people is what the founding Weeks are for, and they are how I find out whether it holds for yours. That is also why the result is measured on Friday, Day 30 and Day 90, and published either way.

Can I see your own system?

Yes. The flagship video walks through it: the inbox, the 15-minute morning, the notes and an AI answering from them. On the discovery call I show it again, and you can ask it anything.

Can I talk to someone who has worked with you?

Not yet; there is no past client to call. Once a founding Week finishes, that client may agree to take a call, and that will be their choice, never a condition of their price. Until then, if your business partner, spouse or ops lead wants to hear it from me, I will walk them through it on a separate 20-minute call.

What exactly do you promise?(Draft, Jay decides)

Two things are in the contract. If Map Day does not convince you, stop; you owe nothing more. If fewer than 15 of your 20 sealed questions are answered your way on the first try on Friday, you get $5,000 back and up to 10 business days of extra work. That is the cap: $5,000 and 10 business days. Before you hire anyone to build this, me included, ask them to take the Friday Test.

The guarantee in full

If it does not work, what do we get back?(Draft, Jay decides)

Your money at risk: $6,000 if you stop after Map Day, and you keep the map, the ranked list of decisions to write down, three of your decisions written up and a written recommendation. After that, the most you get back is $5,000, if the Friday Test first pass falls under 15. The rest of the protection is my time, capped at 10 business days. Everything built is yours to keep either way.

What happens if you get sick, or your day job gets in the way?

I also have a full-time day job, which is why there is one Week a month. Everything after Friday runs in writing or in the evening: for 30 days, a reply within one business day in a shared Slack channel plus two scheduled evening calls; from Day 31 to Day 90, a reply within two business days. If I am unavailable for more than three business days, the support period extends by the same number of days. The system does not depend on me: every account is yours, and you get a written guide to running it and to switching to the backup route.

Will it work for us?

My judgment cannot be written down.

In the abstract, no. But you can answer one question at a time, out loud, and say why, and on Day 3 that is all you do. The decisions your own Question Log shows reaching you each become a short note: the rule, where the line is, the exceptions, the reason, and who may decide without asking you. The calls that should stay yours are marked "owner only", so your team at least knows which ones those are.

What if the person who replaces me is not as good as I am?

Then they need your reasons, not only your steps. A Decision note holds the reason, so the next person decides the way you would, or knows when to ask. One of the Week’s extras, the Key-Person Capture, does the same for the team member whose leaving would hurt most: a two-hour interview within 30 days of Friday, their decisions written up and checked by them and by you.

I point them to the SOP and they still call me. Why would this be different?

Because they do not have to find anything. They ask in a Slack channel they already use, in their own words, and the reply quotes your rule and names the note it came from. When the system does not know, they ask you once, your answer becomes a note, and nobody asks you that again. Friday tests it: your team, not me, asks the 20 sealed questions. In week 4 they log the questions that still reach you, with a column for "asked the system first?", and we compare it with the first log on Day 30.

We tried Notion, SOPs and Loom. Nobody used any of it.

Those attempts fail in one of three places: nobody writes the owner’s answers down, nobody keeps them current, or the team does not look. The Week puts a named step on each. You talk and I write. Fifteen minutes each morning, and a person on your team who keeps it tidy, keep it current. Your team asks in Slack instead of searching. The method is called the Seedling System: Capture, Garden, Connect, Delegate, where Delegate means your team asks the system, not you.

Is this just another system I will abandon in three weeks?

It can be, and the Week is built around that risk. The upkeep is written down and assigned before I leave: your 15-minute morning, the tidy-keeper’s 30 minutes a week, and review-by dates on every decision. Then 90 days of Garden Check are included: once a month I audit what has gone stale and re-run the Friday Test on 20 new questions from that month, so you see a slip as a number while it is still small.

Who keeps it up to date? It cannot be a second full-time job.

It is not. Your part is 15 minutes each morning: sort what came in, file it, fill the gaps, and sign off any decision. One person on your team keeps it tidy (we call them the Garden Keeper) for about 30 minutes a week, working from lists the AI produces: notes not touched in 60 days, empty fields, suggested links. If even 15 minutes a day is more than you will give it, do not buy the Week.

Will this work in my kind of business?

It is built for owner-led agencies, consultancies and expert-led coaching or course businesses at $1–2M with 8 to 30 people, where the work happens at desks, in documents and Slack. It is a poor fit for home and field services and for e-commerce, where the knowledge lives in the van or the ad account; the course may still help there.

How it works for your team

How does someone on my team ask it? From Slack? From a phone?

In a Slack channel, usually called #ask-the-vault. They type @Claude and the question in plain words, on the desktop app or their phone. Nothing to install, no new login. The reply comes back in the thread, quotes your rule and names the note it came from. If the notes do not cover it, the reply says "Not in the vault yet: ask [owner], then forward the answer", and that answer becomes the next note. If your company is not on Slack, the same notes sit in a shared project in the Claude app, on a laptop or phone.

What does that cost per person?

In Slack, the people asking do not need their own Claude seat. You pay for seats only for the people who run it, you and the person who keeps it tidy at minimum: $20 a seat a month billed annually, $25 monthly. Questions in the channel are billed by usage from a prepaid balance, under a spend limit you set; Anthropic does not publish a per-question cost. On the Claude-app route, everyone who asks needs a seat at the same price. Claude in Slack is in public beta, so features may change; the switch to the app route takes under an hour and is written into your guide.

Does every laptop now hold all our client notes? What happens when someone leaves?

No. Only the people who write notes, usually 2 to 5, hold a copy, on company-managed laptops. Everyone else asks in Slack and holds nothing. When a writer leaves, you remove them from the shared vault and wipe the laptop. Anything in the vault can be read by anyone in the ask channel, so it holds only what everyone in that channel may see.

Do we now have two places to look, Notion and the vault?

No. Your team asks in one Slack channel. The vault holds your decisions and links to where everything else lives, and Notion, Drive and the project tool stay where they are. Up to 50 key documents are brought in on Day 4; the rest stays put, and the notes point to it.

Am I the Garden Keeper? How many hours is this on top of my job?

For the ops lead.

Probably, or you name who is. By my count of the schedule, about 12 to 15 hours across the four weeks of preparation and the Week: the kickoff call, one to two hours of account setup, parts of Days 2, 4 and 5, and 45 minutes of training on Friday. After that, about 30 minutes a week, plus a daily glance that the machine which publishes changes is switched on.

Who fixes it when Obsidian, Slack or Claude changes something?

First, the written guide you receive on Friday: every account and setting recorded, a symptom-to-fix table, and the switch to the backup route. Through Day 90, I do, within the support reply times. After Day 90, your own admins with that guide, or an optional monthly plan with me.

Money

$30,000 is a big share of my profit.

At $1.5M revenue and a 15% margin, it is about an eighth, so the price only makes sense if the problem costs you more. The calculator uses your numbers: the questions that reach you, what an hour of your time is worth (using profit, not revenue), your team’s waiting, and what the last week away or resignation cost you. It subtracts what the system costs to run, including your morning. On time savings alone, an agency like our worked example is close to break-even in year one; the Week earns its price when a week away, a resignation or a hiring wave is close. Founding clients net $22,500 (below).

Run your numbers

What are the founding terms?

Founding clients pay $30,000 and receive a $7,500 credit at Day 90 for completing the measurement data and two interviews, whatever the results. Net cost: $22,500. The case study is published whatever the result, checked by you for accuracy, named or anonymised as you choose. A testimonial and a referral are optional and never tied to price.

Can we try a smaller piece first?

Yes, three ways. Free: keep the Question Log for five days; it shows you how many questions reach you and which are decisions. Free, about four a month: send me the log, and I return a short written read of which questions are decisions, which are steps, and the three decisions that would stop the most interruptions. Paid: Map Day, $6,000. One day that maps where your answers live, then writes up three of your decisions and has your ops lead ask the AI about them, so you see your own judgment come back before you commit. The $6,000 counts in full toward the Week if you book within 30 days.

Map Day

How do I pay?

Map Day, $6,000, in full when you book it. Days 2–5, $24,000, in full on signing, at least five business days before Day 2. Software is paid by you directly to the vendors: in Slack, about $65 a month plus usage for a 15-person team on monthly billing; on the Claude-app route with 10 people asking, about $265 a month.

What else is included beyond the build?

Four extras, each written into the contract with a date. The Away Plan: what each lead may decide while you are out, what waits and who gets what. The Key-Person Capture: one key team member’s decisions, written up the same way. New-hire reading paths: the first five days in the vault for up to three roles. And 90 days of Garden Check: a monthly audit and a fresh Friday Test on that month’s questions.

Are there costs after the Week?

Your software, and your time: 15 minutes a morning for you and 30 minutes a week for the tidy-keeper. Support, the Day 7 check-in, the Day 30 review and Garden Check through Day 90 are included. After Day 90, help is optional, priced at the Day 90 review. If your Day 90 numbers say you do not need it, I will say so.

Compared with the alternatives

Is this not all online for free?

Yes, the method is. The free video teaches it, and Obsidian is free. Doing it yourself costs your evenings, and you still have to write it, keep it current and get your team to use it. The Week is for owners who want that finished in five days, with someone else doing the writing and training the team.

Can I not just put our documents into Claude or ChatGPT myself?

You can, and for some firms that is enough. A shared Claude project on a Team plan costs $20 to $25 a seat a month, and it answers from whatever you put in it. It is the same tool the Week uses as its backup route. The catch is the first word, "documents": if your decisions are not written down, there is nothing true for it to find. The Week is mostly the writing-down, checked by you, and the habits that keep it current.

Why not hire an admin to pull it out of my head?

That works for some owners, and if you need the role anyway, hire them. Two things to weigh: the knowledge moves into a second head unless it is written somewhere, and they still have to learn which questions to ask you. The Week writes it down in five days, and the admin you hire is a natural person to keep it tidy afterwards.

How is this different from EOS?

EOS runs your leadership team: goals, meetings and issues, over about ten facilitated days across two years, at roughly $36,000 to $52,000 in year one with an implementer. It does not write down how you decide or give your team a place to ask. The two can run side by side; if your problem is a leadership team that is not aligned, start with EOS.

How is this different from SYSTEMology?

SYSTEMology names the same bottleneck, the owner, and documents your core processes, self-led on its platform ($195 a month) or through a 90-day done-with-you programme, priced by quote. The Week starts from the questions that reach you, writes down your decisions and reasons as well as steps, and finishes in five days. If you want a full process library, SYSTEMology is built for that.

Why not Trainual or another SOP tool?

SOP software is a good home for click-by-click training; Trainual’s one-time implementation fee is $1,000, plus seats. Someone still writes the content, and SOP tools hold steps, not the judgment behind them. If your team asks "how do I do this task", an SOP tool may be enough; if they ask "what would the owner decide", it will not be.

Why not hire a VA or writer to document our SOPs?

A writer documents steps well and costs far less than the Week. A writer cannot draw out judgment you have never put into words, or set up the upkeep and the Slack channel that keep it used. If most of your questions are steps, hire the writer.

Why not an AI knowledge-base company for €4,900?

If your documents are already accurate and you want search over them, that is a reasonable buy: BinarCode (€4,900) and Cognio (from about $8,000) install AI over what you have. The Week costs more because most of the work is getting your decisions out of your head and checked by you before anything is searched, then training your team and testing it on your own questions.

What is the course, and what does it cost?

Out of Your Head teaches the whole method for you to build yourself, with templates. It is in founding pre-sale; the full price will be $497, with a 30-day refund. It is the right choice if you are under $1M, under 8 people, or would rather spend time than money.

How the Week runs

How much of my time does it take?

About 20 hours across Map Day and the four build days, heaviest on Day 3, when you talk and I write. Before that: a 60-minute kickoff call, five days of logging the questions that reach you (about a minute each), 60 to 90 minutes of intake, and 20 minutes to seal your 20 questions. Each team lead gives about 25 minutes on Map Day and a few hours across the Week; everyone who will ask gives 90 minutes of training on Friday. After: 15 minutes each morning.

Remote or on-site?

Remote by default, over video with screen share. On-site on request, with travel at cost up to a cap set in the proposal; if only some days, Day 3 and Day 5 matter most.

What exactly do we have at the end of Day 5?

A list in the contract of items that either exist on Friday afternoon or do not, in four groups. The system: your vault, with at least 20 decisions written up and signed off by you, at least 10 processes, and notes for clients, projects and people. The Slack channel your team asks, its written guide and the data rules. The habits: your morning, a trained tidy-keeper, ways to drop things in. The record: the map, the Friday Test scorecard, recordings and a 30-day plan. Plus the Away Plan and new-hire reading paths.

What happens after the Week?

A check-in on Day 7, and a 90-minute review on Day 30, when your team re-runs the Question Log and answers 20 fresh questions. Garden Check repeats the fresh test at Day 60 and Day 90. Support runs on the reply times above. After Day 90 the system is yours to run, with or without me.

We are busy delivering. Can this wait?

It can, and if nothing is forcing it, waiting costs you little. If you have a date in the next six months, such as a planned leave, someone on notice, a hiring wave or a second office, that date is your deadline, because intake takes four weeks.

How many Weeks do you run?

One a month, because I run each one myself alongside a day job, and I am choosing too. Weeks are booked four weeks ahead because intake takes four weeks.

Data and ownership

Is this an ad for a software company?

No. Obsidian is free and stores plain files on your machines. I resell nothing and take no commission. The software you pay for (Claude seats, Obsidian Sync for the writers) you buy directly from the vendors, in your company’s name, and you can cancel either without losing a note.

Who owns what we build?

You do: every note, template and recording, in plain text files you can open in any text editor. Every account is in your name. My access is removed at Day 90 unless you keep me on a follow-on plan.

Will an AI read our confidential client data?

Only what you decide. On Day 2 you write the data rules: what never enters the vault, for example HR files, pay, client passwords and anything a client contract keeps away from AI services. I build to your rules; I do not give legal or compliance advice, so you decide whether the AI vendor’s terms meet your obligations. Claude in Slack is not available to organisations on zero data retention, customer-managed encryption or the HIPAA configuration. If your client contracts forbid AI entirely, the Week is not for you; tell me on the call.

Do we have to use Obsidian?

For founding Weeks, yes, and only the 2 to 5 people who write notes use it. Your team never opens it; they ask in Slack. It is the default because it is free, keeps your files as plain text you own, and holds the fields each decision needs.

How do I ask for a refund, or reach you?

Through the contact form on completions.io; there is no public email address. A Friday Test refund needs no request: the contract pays it within 10 business days of Day 5. A course refund within 30 days is requested through the same form.

Still deciding?

Run your numbers first. If they say the Week pays for itself on your figures, apply. Mostly multiple choice, three short answers, and it asks for your revenue, team size, and the date that makes this urgent.

Apply for a founding Week

Not ready? Keep the Question Log for five days. It is free, it shows you the count, and it is where the Week starts.

If you apply and we are not a fit, I will say so on the call and point you to the cheaper route that is.