not sure how to explain this
but sometimes nothing crashes
things just become inconsistent
need manual fixing
don’t run properly
feels harder than actual errors
not sure how to explain this
but sometimes nothing crashes
things just become inconsistent
need manual fixing
don’t run properly
feels harder than actual errors

I've been helping people fix their OpenCLAW setups for weeks now. 50+ configs, DMs, reddit threads, discord. and the pattern is always the same: people break things in their first week that take 5 minutes to prevent but 5 hours to fix later.
This is everything I wish someone told me on day one. in order. do this before you build anything.
Step 1: Change your default model right now
If you haven't touched this setting, there's a good chance you're running opus. Opus is the most expensive model available. it's incredible for complex work. it's also complete overkill for 90% of what you'll ask your agent to do this week.
Switch to sonnet. you will not notice the difference for normal tasks. you will notice the difference on your bill.
json
{
"ai": {
"model": "claude-sonnet-4-5-20250929"
}
}One person I helped was spending $47/week without realizing it. we changed this one setting. next week cost $6. same agent, same tasks, same everything.
Step 2: lock your gateway before you connect anything
If you're running openclaw on a VPS, check this immediately:
bash
openclaw config get | grep host
If it says 0.0.0.0 or you don't see a host setting at all, your agent is accessible to anyone on the internet who finds your IP. that means a stranger could message your agent. your agent that's about to have access to your email and calendar.
fix it:
json
{
"gateway": {
"host": "127.0.0.1"
}
}
Access it through SSH tunnel: ssh -L 18789:localhost:18789 user@your-vps
Takes 2 minutes. do it now. not after you set up telegram. now.
Step 3: set up your SOUL.md before anything else
Your first message to your agent should NOT be a real task. it should be:
"Read BOOTSTRAP.md and walk me through it"
This sets up your agent's identity. if you skip this (most people do because they're excited and just start asking questions), your agent has zero personality and zero context about who you are. everything will feel generic and robotic and you'll think openclaw sucks when actually it just doesn't know you yet.
If you already skipped it, create a SOUL.md manually. start with this:
markdown
you are [agent name]. you assist [your name]. be direct. no filler. match my tone. if I ask a question, answer it first. then elaborate only if needed. never say "absolutely", "great question", or "I'd be happy to." if you don't know something, say so. don't guess. if a task will cost significant tokens, tell me before doing it.
That's it. 6 lines. edit it over the next week whenever your agent does something annoying. "never do X" lines work better than "try to be Y" lines. your SOUL.md is built through irritation, not planning.
Step 4: don't install any skills yet
I know. clawhub has 13,000 skills and they all look cool. do not install any of them this week.
Here's why:
Some of them loop silently and burn tokens in the background. you won't know until you check your bill.
Some of them inject into every conversation and bloat your context window.
Virustotal flagged hundreds as actively malicious. infostealers, backdoors, the works.
You don't know what your agent can do without skills yet. learn the stock capabilities first. you'll be surprised how much it handles on its own.
After week 1, when your agent feels stable and your costs are predictable, add ONE skill. test it for a few days. then add another. never more than one at a time.
Step 5: don't create a second agent
Every new user thinks they need multiple agents. one for personal stuff, one for work, one for coding. you don't. not yet.
Every agent you create is an independent token consumer. every agent needs its own channel binding. every agent complicates debugging. I have seen so many people create a second agent to "fix" problems with the first one. now they have two broken agents instead of one.
Get one agent working perfectly for 2 weeks. then decide if you actually need a second one. Most people don't.
Step 6: learn the /new command
This is the single most important thing nobody tells beginners.
Every message you send in a session gets included in every future API call. after a week of chatting, you're sending thousands of tokens of old conversation with every new message. that costs money and makes your agent slower and more confused.
Type /new to start a fresh session. your agent doesn't forget anything. it still has all its memory files, SOUL.md, everything. you're just clearing the conversation buffer.
Use /new:
before any big task (research, writing, analysis)
when your agent starts acting weird or confused
at least once a day as a habit
Step 7: check your costs daily for the first 2 weeks
Run openclaw status or check your API provider's dashboard directly. know what you're spending before it surprises you.
If you're on sonnet with one agent and no skills, you should be spending $3-8/month for moderate daily use. if you're spending more than that in your first week, something is wrong, and it's fixable.
What your first week should actually look like:
day 1-2: set up SOUL.md, have normal conversations, ask it stupid questions, get comfortable
day 3-4: start using it for real tasks. calendar, reminders, web searches, summarizing articles. the boring stuff.
day 5-7: refine your SOUL.md based on what annoyed you. check your costs. get a feel for your daily usage.
That's it. no skills. no second agent. no multi-agent orchestrator. no cron jobs. just one agent that knows who you are and does basic tasks reliably.
If that feels underwhelming, good. the people who are still using openclaw two months from now all started exactly like this. the people who quit started with 8 agents and 20 skills on day one.
After week 1:
if your agent feels useful, your costs are under $10, and nothing is randomly breaking, you're ready to start experimenting. add web search if you haven't. then a daily briefing skill. then maybe calendar integration if you want proactive reminders.
Build slowly. Earn each new capability by making sure the last one is stable first.
The people who survive month one are the ones who started boring. Trust the boring.
I want to write this because when I was trying to figure out what to do after getting laid off I could not find anyone laying out the real economics of a solo service business. Not revenue or actual costs, hours, the take home after taxes. So here's mine down to the dollar
Six startups pay me a monthly retainer. Before they submit an app update I run all their user flows through automated tests and send a report showing what passed and what broke with screenshots for every step. They fix the broken stuff before anyone downloads it. Thats the whole service. But I didnt start here
I was a PM at a funded startup. Got cut with about 30% of the company in a restructure. Spent two months applying to PM roles and getting ghosted after final rounds. I needed money coming in so I started messaging everyone I knew on linkedin. Not pitching a service, just telling people I was available and asking if they knew anyone who needed product help. Most people said "ill keep you in mind" which means no. But three people actually came back with something. Two were one off strategy projects, one was a longer engagement helping a founder figure out their roadmap. None of it was stable. I was making about $4,500-5,000/month across whatever I could piece together but every engagement had a defined end date. No recurring anything. Every month I was basically reinterviewing for the next one
Five months in one of those linkedin conversations turned into a launch prep gig for a seed stage startup. Social fitness app, small team, about $1.2M raised. The founder needed someone to own the launch plan, the metrics framework, the app store listing, all the product side stuff his engineers didnt want to think about. Part of that was doing my own walkthrough of the app before submission to make sure everything worked from a user perspective. Two days before they were supposed to submit, the dev pushed a build and the signup flow was broken on any Android device with the font size set above default. He had tested on his Pixel with everything default. Worked fine for him. I caught it because I happened to be doing my walkthrough on a Samsung with the text bumped up. Pure luck
The founder asked if there was a way to prevent that from happening again. I spent a week trying to figure that out. Looked into appium first because thats what comes up when you google mobile test automation. I am not a developer. Three days in I still hadnt gotten a single test to actually run. The setup needs android SDK, java, specific environment variables, a bunch of dependencies that all have to be the exact right version or nothing works. Every tutorial assumed I already knew what a gradle build was. I dont. So that was a dead end
Then I looked at some of the newer no code testing tools and most of them still wanted me to identify elements in the app by their technical IDs which I also dont have access to because im not part of the engineering team and I dont touch the codebase. I almost gave up and just told the founder id do manual walkthroughs before every release which is basically what I was already doing for free as part of the consulting gig
Eventually I found something where I just type what should happen and it figures out the rest by looking at the screen. Thats what I use now and ill get into that but it let me write 25 test scenarios for that clients app in one afternoon and when I ran them against the broken build 4 of them failed with screenshots showing exactly where. I charged the founder $1,200/month to maintain those tests and run them before every release. He was already budgeting $3,500 for a part time QA contractor to do the same thing by hand so it was an easy yes.
That first client changed how I thought about the consulting work I was doing. I was still taking product strategy gigs on the side but the testing retainer was the only thing that paid me the same amount every month without me having to pitch anyone again. The founder mentioned what I was doing in a group chat with other YC founders and someone reached out. Thats how client 2 happened at $900/month. I didnt do any outreach for my first three clients, they all came through the first founder talking about it. By month 5 I had 4 clients at $4,400 and I stopped taking consulting gigs entirely because the retainer income was more predictable and the work took less time
It wasnt clean though. Month 4 I missed a real bug on one of the ecommerce clients because I had only written tests for the straight path through checkout. Didnt cover what happens when someone removes an item mid purchase and goes back. A customer found it before my tests did and that was a rough call with the founder. Rewrote his entire suite that weekend to cover the backwards paths and the skip ahead paths. Most of my suites now have more weird path flows than linear ones because thats where the real bugs hide. Month 6 one clients CTO pushed to replace me with an engineer writing coded scripts. I showed 14 bugs caught in 3 months and asked how long it would take to rebuild that coverage in appium. He said 6-8 weeks full time. They kept me
Current state is 6 clients between $900 and $1,600/month. Total $7,800. A couple came from twitter where I post about specific ways mobile apps break, not general testing advice. Things like how most onboarding tests use a fresh install every time but real users are upgrading from 2.3 to 2.4 with months of cached data and nobody tests that upgrade path. Founders read that and DM me. I offer to test their 5 most critical flows for free. Every trial has caught at least one real issue. After that the pricing conversation is short.
Costs. The platform runs about $150/month for a plan I need across 6 clients. It includes the devices and the test runs so theres no separate infrastructure to pay for. On top of that I pay about $95 for a real device subscription. Rest is maybe $40 in random stuff. Everything together comes to about $285 on a normal month, some months closer to $350 if I need extra test runs during a clients launch week.
Revenue $7,800. Costs about $350. Profit roughly $7,450. I set aside 30% for quarterly taxes and pay $380/month for health insurance which I didnt have for the first three months because I kept putting it off. Actual take home after taxes and insurance is about $4,800. Thats for maybe 25 hours a week. My consulting was paying about the same but with 3x hours and no idea where next months money was coming from
All my clients are funded startups between seed and series B. I charge based on complexity and platforms. $900 for a productivity app with 20 flows on one platform. $1,600 for a fintech app with 55 flows across iOS and Android where I need to test permission states and biometric fallbacks. Average is about $1,300. The sweet spot is teams with 5-15 engineers. Complex enough app to need real testing. Small enough that nobody on the team owns quality full time. Thats me now for $1,300/month instead of the $6-8k a junior QA hire would cost them
Zero churn in 9 months. Once the tests are catching stuff before releases nobody turns them off. The first time I catch something that would have shipped broken the conversation about whether they still need me just stops happening
For someone thinking about this you need to understand mobile apps well enough to know which flows matter and which edge cases break things. You need to be comfortable talking to founders about their product. And you need patience because writing test instructions that work reliably takes a couple months of getting it wrong first. That’s it.
Happy answer whatever u want to know about this. The pricing; setup details or any thing