The Setup That Changes How You Work With Claude
Every guide starts with the prompt. The one that worked for me started with the goal.
I did not set out to automate my social media content.
I opened a Claude cowork session in January with one goal written down: grow paid subscribers for the Clueless Clothing app. That was it. No prompt about social media. No instruction to connect any accounts. I just told Claude what I was trying to build and started working backwards from there.
What happened over the next two sessions is what I want to show you.
Claude started asking me questions. Not the questions I expected — not “what do you want to post?” — but questions about where my subscribers were coming from, what signals I had, what data it would need to actually help me move that number. It asked me to provide it access to sources I had not thought to connect. It mapped a growth loop I had not drawn yet. By the end of session two, it had proposed automating my social distribution as a subscriber acquisition channel — and built the workflow to do it.
I did not tell it to do that. It got there because I started with the goal.
That is goal-first setup. And it is the one thing no Claude guide I found told me to do first.
The Conventional Argument
Every guide I found ran the same sequence. Pick a model. Write better prompts. Use Projects for memory. Maybe add a custom system prompt. The advice is not wrong. It is just aimed at the wrong question.
Those guides assume you want Claude to write faster. What I wanted was for Claude to think with me — to hold context across sessions, to remember what I had already decided, to get closer over time instead of resetting.
That is a different tool. Same software. Different setup. One step separates them, and I did not find it in any guide.
The Dismantle
Here is what was happening before I rebuilt my setup: I was optimizing the prompt before I had clarity on the problem.
Each session, I opened a blank thread and started from scratch. Claude had no idea what we had worked through the session before. No idea what the constraint was. No idea what a bad recommendation looked like in my context. I was treating a thinking partner like a search engine with better grammar.
The result was clean output that did not accumulate. Every session produced something. Nothing compounded. I was doing the connective work manually — in my head, in a doc somewhere, in the friction between sessions — and calling it a workflow.
I stopped when I realized I was spending more time re-orienting Claude than I was spending on the actual work.
The Core Idea
Start with the goal, not the prompt. That one inversion turns Claude from a session tool into a compounding asset.
What I Changed
1. I wrote the goal before I opened Claude
Before I rebuilt my setup, I wrote one paragraph offline — in Notes, not in Claude — that answered three things: what am I trying to accomplish in the next 60 to 90 days, what does done actually look like, and what do I know that Claude does not.
For the subscriber growth goal: I needed paid subscribers for the Clueless Clothing app. Done meant a number — a specific acquisition target with a date attached. What Claude did not know: my list size, my current conversion rate, where my traffic was coming from, and the fact that social distribution was an untapped channel I had not systematized.
That paragraph took eight minutes to write. It changed what Claude asked me in the first session. It stopped generating output and started asking what it needed to actually help.
2. I built Projects around outcomes, not topics
My original Projects were organized like a filing cabinet. Writing. Strategy. Research. Useful for finding things. Useless for compounding work.
I rebuilt them around outcomes. App subscriber growth. Product roadmap for Q2. Distribution systems. Every conversation inside an outcome-scoped Project is already aimed at something that ends. Claude does not have to guess what matters. The sessions inherit direction automatically.
The subscriber growth Project is where Claude eventually proposed the social automation — because every session inside it was pointed at the same number. The proposal did not come from a prompt. It came from context accumulating until Claude had enough to make a connection I had not made myself.
3. I wrote instructions that named constraints, not just context
The old version of my Project instruction: I’m the founder of Clueless Clothing, a mobile app. Help me grow.
The new version: I’m the solo founder of Clueless Clothing, a mobile app. My goal is growing paid subscribers. My constraint is time — I have no team, so any system I build has to run without me. If a recommendation requires manual execution more than once a week, flag it. I want compounding distribution, not one-off campaigns.
The second version changed what Claude recommended. It stopped suggesting tactics that required daily attention. It started building systems. The social automation came out of that constraint — Claude understood that a workflow I had to run by hand every day was not a solution.
4. I loaded the artifact, not the summary
Before the first serious session on a Project, I paste in the actual document — the analytics export, the campaign brief, the current conversion data. Not a summary. The source.
Summaries introduce my interpretation. My interpretation introduces drift. Three sessions in, I am working from Claude’s model of my model of the situation. Loading the source document removes one layer of inference. The output quality difference is not subtle.
5. I close the loop once a week
Friday afternoon, five minutes in the active Project. One line: what changed this week. One line: whether the goal shifted. One line: what Claude got wrong that I corrected.
This is not journaling. It is calibration. Claude does not update its model of the project automatically. I have to push the new information in. Five minutes a week prevents months of accumulated drift. Without it, the Project becomes a transcript of what you used to be working on.
What Happened After
By the second week of running goal-first setup, the sessions were noticeably shorter. Not because Claude had gotten better. Because the Project already held the context. I was not re-anchoring. I was working.
The social automation workflow Claude proposed is now running. It pulls content signals, formats posts, and queues distribution — without me prompting it to do any of that on a given day. I did not ask for a social media automation tool. I asked Claude to help me grow subscribers. It got there on its own because the goal was loaded, the constraints were named, and the context had been accumulating for two weeks.
That is the thing no guide I found described. The Project does not just remember. It reasons forward. The work you do in session one changes what session eight looks like. That is different from a good prompt. That is a different tool.
The principle is free. The system I use to enforce it — the goal-framing worksheet, the Project instruction template, the Clueless Clothing worked example, and the /retro skill that keeps the whole thing from decaying — is below.
