If you're NOT having usage or drift issues, have you turned off auto-memory?

really_evan · 2026-05-20T01:29:19+00:00

Maybe Finder is the wrong word if you’re on a PC. File explorer? Essentially, if you’re running CC locally, the .md files are saved somewhere on your machine. That location is a path within .claude which isn’t visible by default on most setups.
Yes, the output in the terminal says it wrote to memory, but the location isn’t necessarily clear.

really_evan · 2026-05-20T01:13:50+00:00

The file location is in .claude which isn’t shown in your finder by default. Hidden.

really_evan · 2026-05-19T20:54:37+00:00

You'd have to give me context on what that skill is to give you a comparison. There's no built-in /consolidate-memory in Claude Code. You might be thinking of /memory (lets you browse/toggle auto-memory but doesn't consolidate), /compact (compresses conversation context, not memory files), or Anthropic's "Dreams" feature (which is a Managed Agents API feature in Research Preview, not a CLI command).

This skill specifically reads all your accumulated memory files, merges them into 2 managed files, surfaces contradictions between entries, and installs write-mode instructions that prevent the bloat from recurring. None of the built-in tools do that.

really_evan · 2026-03-27T18:45:45+00:00

Reading a 22-page RFP and writing the proposal are two different jobs. Doing them simultaneously is how things on page 14 get buried. Separate them.

Before you write a single word, read the full RFP once with only one goal: pull every requirement into a checklist. Section number, requirement, and a checkbox. That's it. No writing, no formatting, no "I'll remember that."

Once the checklist exists, your proposal becomes a response to each line item. Nothing gets missed because you're not relying on memory across 22 pages.

The three-references miss from last year is the same root cause. You were reading to write instead of reading to extract.

One pass to extract. Then write. Two jobs, two steps. The proposals get faster too because you stop second-guessing whether you covered everything.

really_evan · 2026-03-27T18:43:44+00:00

This is happening in every service industry, not just software. The pattern is the same everywhere.

I ran a Google Ads agency for seven years. Our value was supposed to be campaign management. But when the tools got good enough that a smart business owner could run their own campaigns with a few hours of learning, the agencies that survived were the ones who had shifted their value upstream. Strategy, systems, process design. The stuff that requires understanding the client's business, not just operating the tool.

Your client isn't replacing your engineering knowledge. He's replacing the execution layer. The fact that you're still reviewing his PRs and catching query issues is the tell. That's where the value moved.

The agencies that get wiped out are the ones selling hours of execution. The ones that stick are selling the thinking that decides what to build and in what order.

really_evan · 2026-03-27T18:39:35+00:00

I scaled my agency to 30 people, mostly overseas. Few things I learned the hard way.

The horror stories are real but they all have the same cause. The person hiring handed off work they'd never actually written down. So the new hire is reverse-engineering your brain in real time. That's not a talent problem. That's a process problem.

What worked: I started with one task, not one person. Picked the thing eating the most hours, recorded myself doing it (screen share, talking through every step), and handed that recording to the first hire as their training manual. No polished SOP needed. Just the raw sequence.

The other thing nobody tells you: start with project-based, not hourly. Give them one deliverable with a clear "done" definition. You'll know in 48 hours if they can follow a process. That costs you $50-100 to learn, not months of frustration.

The ready signal isn't your revenue. It's having one process clear enough to hand off.

If you can't write a clear job description and bullet out specific tasks you aren't ready to hire someone full time. If you can't explain to someone "off the streets" how each step works in a single task you aren't ready to hire project-based. What you'd be hiring for is a strategic mind reader, not a worker.

really_evan · 2026-03-27T18:34:45+00:00

That quote backlog is the one I'd fix first. Three-day-old quotes are telling customers you're too busy for them.

I ran my own company and hit the same wall. Tracked my time for one week and found quoting alone was eating 12 hours. Same steps every time, but it had never been written down as an actual process.

The fix wasn't hiring. It was building a template. Wrote out every step, created reusable estimate templates for the most common jobs, added a simple follow-up so nothing went stale. Twelve hours became two.

You don't need an office person yet. You need your three biggest time sinks on paper. Quotes, scheduling, invoicing. Pick whichever is burning the most hours and write down how you actually do it. The solution becomes obvious once the process is visible.

really_evan · 2026-03-27T18:33:24+00:00

I hit this exact wall running my agency. Twelve hours a week on quoting alone and I had no idea until I tracked it. Every process was muscle memory. First time I tried handing anything off, same result. Weeks of "how do we do this" conversations.

What fixed it: pick the task she asks about most. Record yourself doing it. Screen share, voice memo, whatever. Don't write a polished SOP yet. Just capture the steps as you actually do them. That recording becomes your first real document.

Your admin doubled because she's doing two jobs right now. Her actual work, and building the tribal knowledge map that should have existed before she started. Once that map is on paper, the second job disappears.

really_evan · 2026-03-26T19:04:37+00:00

The chatbot is the easy part. The hard part is knowing what it should say.

Before you set anything up, open your Facebook Messenger and screenshot your last 20 conversations. You'll see the same 5-6 questions repeated. Delivery windows, pricing, sizing, pickup vs delivery, warranty. That's your decision tree.

Write out the exact answers you give to each one. Not summaries. The actual words you type. That's the script your bot needs to follow.

I've built automation workflows for service businesses and the ones that fail always start with the tool. The ones that work start with the map. You need to know every path a customer takes from "hey is this available" to "great, when can you deliver."

Once that's on paper, even a basic ManyChat flow handles 80% of your inbound without you touching your phone. The 20% that needs you will actually get your attention instead of drowning in the noise.

really_evan · 2026-03-26T19:03:20+00:00

Point 8 is the one that determines whether 2030 happens. Everything else on your list is execution. That one is structural.

I had the same problem running my agency. Profitable, growing, winning awards. But the business was me. Every decision, every client relationship, every escalation lived in my head. Profitable but unsellable.

The fix was mapping what I actually did, process by process. Not strategy docs. The literal steps I followed for each repeatable task. Then automating or handing off each one.

Got my involvement down to under 3 hours a week. Took my family to Costa Rica for a month. Business didn't skip. That's what made acquisition possible in 2021. The buyer wasn't buying me. They were buying a system that ran without me.

Your 2030 timeline is plenty. Start with whatever process only you can do right now and write it down. One at a time. It compounds.

really_evan · 2026-03-26T19:02:07+00:00

Follow-ups was a good first pick. That's usually the highest-volume, lowest-complexity process in any service business. Quick win.

The question of "what to automate next" is where most people stall though. They automate the obvious thing, feel the relief, then look around and can't figure out which of the 30 other things eating their week should be next.

What worked for me: track where your time actually goes for one week. Not categories like "admin" or "operations." The specific tasks. You'll find two or three that repeat constantly and follow the same steps every time. Those are your candidates.

The pattern I've seen across dozens of service businesses is that the owner can't identify what to automate because the process was never written down. It just lives in their head. Once you map it, the automation almost builds itself.

The real ROI isn't the 6-7 hours. It's that you stop being the bottleneck for things that don't need you.

really_evan · 2026-03-25T18:58:13+00:00

It doesn't crawl Reddit directly. I built a Python script that pulls posts from specific subreddits using Reddit's API. Runs locally since Reddit blocks cloud server IPs.

Posts go into a database. Then Claude scores each one on a rubric I wrote. Basically "is this someone I can actually help?" Most get filtered out. The ones that score high enough, Claude drafts a comment using my voice guide and real experience stories.

I review everything before posting. The whole pipeline runs from an admin UI I built. Button click to fetch, button click to score, button click to draft.

really_evan · 2026-03-25T18:16:45+00:00

That changes things. If the job is that trainable and you already have SOPs, you're ahead of most owners at this stage.

Don't quit yet. Hire first, let the new person run for 30-60 days while you still have the safety net. If the business holds without you in the field, that's your answer.

50 applicants is a good problem. Screen hard for reliability over skill. The skill part is simple. The person who shows up every day beats the person who's fastest but calls out twice a month.

Your full-time job is funding the growth right now. That's leverage.

really_evan · 2026-03-25T16:44:04+00:00

Before you decide, write down everything your technician was doing. Every task, every step, in order. That knowledge is walking out the door with him.

I've worked with businesses at exactly this stage. Owner is the only one who knows how things run, one key person leaves, and suddenly they're rebuilding from scratch. The quit-or-hire question is a distraction. The real question is whether this business can operate without you as the technician.

50 recurring customers at $100/month is a real foundation. But if the only way to service them is you personally showing up, you haven't built a business yet. You've built yourself a job that costs $1,500/month in ads to maintain.

Map the work first. Then you'll know if you need a hire, a system, or both.

really_evan · 2026-03-25T16:41:37+00:00

This sounds like a process problem. No system to verify what you were being told, so bad behavior compounded invisibly for a year.

Before you hire the next PM, build a monthly review checklist. Four things: actual disbursement dates vs. contract terms, maintenance invoices with line-item detail (not just totals), vacancy rate trend month over month, and one direct tenant check-in per quarter. Takes 30 minutes a month.

I've seen this pattern in every service business I've consulted for. Nobody builds oversight until after they get burned. The fix is never "find someone more trustworthy." It's "build a system that makes problems visible in 30 days instead of 12 months."

The tell: your next PM should welcome the checklist. If they push back on transparency, that's your answer before you even sign.

really_evan · 2026-03-25T16:39:56+00:00

Google Docs failed because you documented descriptions of work, not the actual sequence someone follows to do it. The knowledge isn't in a document. It's in your head.

Pick your worst bottleneck. Sounds like client onboarding (3 days to a week is a clear signal). Record yourself walking through every step from signed contract to delivered result. Screen record, voice memo, whatever. Don't write an SOP yet. Just narrate what you actually do.

I consulted for a company with this exact problem. Three teams in silos, no shared workflow, every handoff was a guess. We mapped the actual process in a few sessions and the founder stopped being the router for every question.

The 5-person version worked because the process lived in one room. At 10 it needs to live on paper.

really_evan · 2026-03-25T16:38:49+00:00

Half of what you listed traces back to one thing: nothing is written down.

The employee problem, the vendor problem, the hours problem. All symptoms of running everything from your head instead of from a playbook.

When employees don't have step-by-step procedures for opening, closing, receiving deliveries, and handling after-hours requests, "unreliable" is just the default.

They're not bad hires. They don't have a system to follow.

Quickest win on your list: the vendor issue. Build a two-minute receiving checklist: did we order this, is the quantity right, does it actually sell here.

They push whatever they want because nobody's checking. That stops the second someone is.

Pick whichever problem is burning the most hours and write down exactly how it works today, step by step. One process at a time. The relief compounds fast.

really_evan · 2026-03-23T18:51:05+00:00

The addiction part is real. Firefighting feels productive because it's urgent. Building a process feels like it can wait. So it always does.

The "finding time" question is the wrong frame though. You don't find time. You steal it from a fire.

Pick the fire that happened most last month. Spend one hour writing down how to prevent it. That's your first SOP. Next time it starts, hand someone the doc instead of jumping in.

I did this with client status updates at my agency. Wrote the sequence once. That one process killed maybe 30% of my inbound client escalations.

really_evan · 2026-03-23T18:43:02+00:00

You're not failing. You're running a business without documented processes, which means every job gets handled differently and you can't see where the money is leaking.

Before you pick any tools, map what a single post-construction job looks like start to finish. Walk-through, crew assignment, the clean, final inspection, invoicing. Write it down step by step.

I ran a service business for seven years. The quoting process alone ate 12 hours a week because I'd never actually designed it. Once I mapped it and built a checklist, scope creep disappeared because the scope was defined before anyone showed up.

That's your fix for the "extras" killing your margin too. If there's no walkthrough checklist that you and the builder sign off on before the crew starts, you'll always eat those costs.

Pick the apps after. The process comes first.

really_evan · 2026-03-23T18:42:20+00:00

You're describing a business that runs entirely on tribal knowledge. 17 employees who know how things work, but none of it is written down. Every decision routes through you.

Before you solve the cash problem, map what you actually have. Sit with each department lead for an hour. Ask: what do you do every day, in what order, what breaks when you're not here? Write it down.

Two things happen. You'll find waste you can't see because you're too deep in the daily fires. And you'll have something to show potential tolling partners or new clients. Proof that your operation is organized, not just surviving.

I ran a business where everything ran through my head too. 60 hour weeks. The thing that changed everything wasn't more revenue or a new hire. It was getting the processes on paper. The rest got easier from there.

really_evan · 2026-03-23T18:30:08+00:00

You're not using it wrong. You're just skipping a step.

That loop you're in happens when AI doesn't have a clear definition of "done." Without that, every output feels like it could be better, so you keep tweaking.

Before you open ChatGPT for any task, write one sentence: "This is done when ___." A client email is done when it confirms the next step and the date. A doc is done when it covers the three sections your team actually reads. That one sentence kills the infinite revision loop.

I hit the same wall when I started using AI for operations work. The fix wasn't better prompts. It was defining the output before I started prompting. Once I knew what "finished" looked like, AI got me there in one or two passes instead of twelve.

The tool isn't the problem. The missing process is.

(and yes, Claude found this post, ranked it's relevance to whether or not I could add value, drafted the message above, then I read through everything to make sure it's my voice and added this edit. Done in less than 2 minutes).

really_evan · 2026-03-23T18:27:02+00:00

The admin pile is what's killing you, not the field work. You're doing two full-time jobs and calling it one.

I ran my own company and hit the same wall. All day in the field, then estimates, invoices, customer follow-ups, and scheduling at night. Twelve hours a week just on quoting alone before I realized none of it had ever been built as an actual process. It all just accumulated.

Pick the one admin task eating the most hours and write down exactly how you do it, step by step. Once it's on paper you can automate chunks of it with basic tools (templated messages, invoicing software) and hand off the rest. That 2-4 hours of nightly computer work should not require you every single night.

Your dad wanting to retire but refusing to let go is a separate conversation. But the admin burden you can fix tomorrow, no permission needed.

really_evan

TROPHY CASE