Running solo operations means your brain becomes a multi-tool by default. Task manager, follow-up tracker, notes app, mental calendar. A Redditor going by u/Professional-Rest138 had the same problem, and their fix replaced every separate workflow with a single pinned chat.
The insight is simple but easy to miss: the bottleneck isn’t that you’re missing the right automation. It’s that you’re storing too much in your head while your tools stay siloed. Building more workflows doesn’t solve that. One central operator does.
The old approach vs. what this replaces it with
The typical solo setup looks like this: a separate prompt for drafting email replies, a different automation for meeting notes, another tool for weekly reviews, and a to-do list that goes stale by Wednesday. Each piece is optimized. Nothing connects.
The author’s approach flips that logic entirely. One chat. One pinned system prompt at the top. Everything funnels in, nothing falls through the gap between tools. The AI doesn’t replace your judgment. It just holds the context so you don’t have to.
🛠️ The full four-step setup
Step 1: Give it a job (one-time setup)
Open a new chat and pin this exact prompt at the top:
You are my background business operator.
When I paste emails, messages, notes, meeting summaries, or ideas, you will:
Summarise each item clearly
Identify what needs action or follow-up
Suggest a simple next step
Flag what can wait
Group items by urgency
Keep everything short and practical.
Focus on helping work move forward, not on creating plans.
Why it works: you’re giving the model a consistent operating context instead of re-explaining what you need on every single visit. The system prompt front-loads the work so you don’t have to re-set the frame each time you open the chat.
Step 2: Feed it messy input
No structure needed. The author just dumps in whatever is piling up:
- 📧 Emails sitting unanswered for two days
- Client DMs that need a real response
- Raw notes from a meeting that ended 20 minutes ago
- Half-formed ideas saved to the Notes app on your phone
- Random checklists from three different projects
Paste everything in, unformatted, and move on. The operator handles the sorting. This is the friction-removal that matters. Most people don’t use capture systems because they require formatting before you even get the information in. This one accepts chaos.
Step 3: Use it like a check-in, not a task list
Once or twice a day, query the operator directly:
- What needs attention right now?
- Turn everything into an action list.
- What can I reply to quickly?
- What’s blocking progress?
This distinction matters more than it looks. You’re not checking off boxes. You’re asking the operator for its read on the situation. It keeps you in decision mode instead of maintenance mode, which is where most of the actual work happens.
Step 4: End-of-week reset
At the end of each week, paste this:
Give me a weekly ops snapshot:
What moved forward
What stalled
What needs follow-up next week
What can be archived
I’ve read a lot of weekly review templates, and most of them collapse because they require too much manual input to fill in. This one works because the chat already has the context. You’re not filling a template. You’re pulling a summary from accumulated information the model already holds.
What actually goes away when you use this
According to the original post, this setup replaced five specific pain points:
- Rewriting to-do lists that go stale before you finish them
- Missed follow-ups on client messages buried in the inbox
- Post-meeting brain fog, where you remember the vibe but not the action items
- That specific dread of realizing three days later you forgot to reply
- Constant switching between tools that don’t talk to each other
That last one is worth focusing on. Tool-switching isn’t just annoying. It fragments attention across context boundaries, and every switch costs real cognitive overhead. Collapsing everything into one chat eliminates that entirely.
One practical limit worth knowing
A commenter in the original thread raised the obvious question: what happens when the chat gets too long and starts losing earlier context? The author didn’t address it directly, but the fix is straightforward. Use ChatGPT Projects and store the system prompt in the project-level instructions. When a chat fills up, open a new one inside the same project. The operating context stays persistent without any re-setup.
Who gets the most out of this
This setup clicks best for people who run client work without dedicated ops support, manage multiple threads with no central tracking system, or find themselves rebuilding to-do lists more often than executing them. If you already have a project management stack maintained by a team, you probably have lower friction elsewhere. But if you’re the person doing everything, this takes a real and measurable amount of pressure off.
The original post, including the thread discussion on managing chat context over time, is live on r/PromptEngineering.
Frequently Asked Questions
Q: What happens when the chat gets too long?
That’s where the weekly snapshot comes in. After creating your Friday wrap-up, archive that chat and start fresh Monday with a new one. The weekly reset is your natural breakpoint, keeping each chat focused and preventing the AI from getting bogged down by months of history.
Q: How do you keep the next chat operating the same way?
Save your system prompt somewhere accessible, notes, a doc, or ChatGPT Projects. When you start a new chat, paste it back in and pin it. Projects do this automatically across conversations, while the manual approach works just fine if you don’t mind the copy-paste.
Q: Is ChatGPT Projects the right tool for this?
Projects remove setup friction by keeping your instructions persistent, but they’re optional. The simple pinned-prompt approach in the post works great too. Pick Projects if you want zero overhead; stick with manual if you prefer keeping things simple and straightforward.
Q: Can you actually reference things from previous weeks?
Yes, through your weekly snapshots. Save them somewhere (or keep them in your archived chats), and when you need context from past weeks, paste the relevant snapshot back in. It’s not perfect, but it’s way better than scrolling through months of messages.
I stopped building 10 different prompts and just made ChatGPT my background operator
by u/Professional-Rest138 in PromptEngineering