How to Set Up OpenClaw for Your Small Business in a Weekend (No Terminal Experience Needed)

You do not need to be technical to set up OpenClaw.

You just need a calm hour, a checklist, and the willingness to start small.

This guide is intentionally practical. It focuses on the setup steps that matter for SMB owners, plus the first tests to confirm everything is working.

1) Before you start (prerequisites)

Where OpenClaw runs

OpenClaw needs to run on a machine that can stay on.

Think of it like installing a phone system:
- If the phone system is unplugged, nobody answers calls.

Common options:
- a small server at your office
- a home mini-PC
- a VPS (a rented server)

Simple rule: if you want OpenClaw to help every day, it needs to be running every day.

What you need

- Admin access to the machine where OpenClaw will run - A chat app account you will use (start with Telegram or WhatsApp, not both) - 60 minutes of quiet time

Also: decide your safety policy now.

For most SMBs, the correct policy is:
- draft only
- approval before sending

You can loosen it later.

Before vs After (what “set up” actually changes)

Before:
- A missed call sits for hours.
- You reply to leads when you remember.
- You keep customer details in your head or scattered across texts.
- You retype the same explanations about pricing, time windows, and policies.

After:
- Missed calls get a text-back draft in under 2 minutes.
- Every lead gets a fast first reply and a follow-up draft.
- Business facts live in USER.md so you stop repeating yourself.
- Open loops get written to memory so fewer things fall through.

If you are a plumber, this is the difference between “I will call you back” and “We can help. What’s the address and what’s the issue? Here are two appointment windows.”

If you are a bakery, it is the difference between scrambling for custom cake details and collecting them consistently in one clean checklist.

2) Step 1 — Install OpenClaw (high-level)

“Install” just means: get the OpenClaw software running on your machine.

Most official paths use commands like openclaw setup and an onboarding wizard.

You do not need to memorize commands. The key is the outcome:
- the Gateway is installed
- the service runs reliably
- you can send a test message and get a response

Screenshot description you can include in your blog CMS later:
- “Terminal window showing openclaw setup completed successfully.”

If you get stuck during install, your first troubleshooting move is:
- run an “OpenClaw doctor/status” style check
- confirm the Gateway service is running

Quick install checklist (owner-friendly)

• [ ] I can log into the machine (admin access)
• [ ] OpenClaw is installed
• [ ] The Gateway service is running
• [ ] OpenClaw auto-starts after a reboot (or you have a clear start command)
• [ ] I have a place to store API keys and channel tokens safely

If you can check those boxes, you are 80 percent done.

3) Step 2 — Confirm your workspace exists (your filing cabinet)

OpenClaw uses a workspace folder as your agent’s office.

Officially: the workspace is the agent’s home and default working directory for file tools and workspace context.

Typical default location:
- ~/.openclaw/workspace (or ~/.openclaw/workspace-<profile>)

Inside, you should see key files like:
- AGENTS.md
- SOUL.md
- USER.md
- TOOLS.md
- IDENTITY.md
- HEARTBEAT.md
- memory/ (folder)

Screenshot description:
- “File explorer showing AGENTS.md, SOUL.md, USER.md, HEARTBEAT.md, memory/.”

Why this matters (in plain English)

Most AI tools forget things because they live in chat history.

OpenClaw is different. Your important business facts are stored in files.

That means:
- you can fix issues once (edit a file)
- the assistant becomes consistent
- you can hand it off to a team member without losing context

4) Step 3 — Fill in the 3 files that make it “yours”

If you only do three things, do these.

A) USER.md (about your business)

USER.md tells the agent who you are and what you do.

Put in:
- business name
- services
- service area
- hours
- pricing rules (if any)
- policies (no quotes by text, cancellation policy, etc.)
- what you want the assistant to do every day

Example:

# USER.md

Business: BrightSide Cleaning
Location: Phoenix, AZ
Services: residential deep clean, move-out clean
Hours: Mon–Sat 9am–6pm

Pricing:
- We do not promise exact pricing by text.
- We provide ranges when we have photos.

Policies:
- We confirm scope with photos or a quick call.
- 24-hour cancellation notice.

What I want from you:
- Draft replies to new leads
- Create a daily priorities list
- Keep a daily log of decisions

SMB examples (copy and adjust)

Plumber:
- Emergency policy: “If active leak, shut off main water and text a photo.”
- Service area and after-hours rules.

Bakery:
- Lead time for custom orders.
- Allergens policy.
- Pickup windows.

Real estate agent:
- Coverage area.
- Preferred showing windows.
- Pre-qual questions.

Fitness coach:
- Session packages.
- Cancellation policy.
- Intake questions and contraindications.

Content creator:
- Sponsorship rules.
- Rates as ranges.
- Deliverables and revision limits.

B) SOUL.md (voice + boundaries)

SOUL.md sets tone and guardrails.

For SMBs, this is a safe default:

# SOUL.md

Tone:
- Warm, professional, plain English
- Short paragraphs

Boundaries:
- Draft only. Never send externally without approval.
- No promises on price or timing.

Format:
- Start with a 1-line summary.
- Then bullets.
- End with a question for approval.

Tip: if you have two “modes,” spell them out.

Example:
- “SMS mode: under 120 words, very human.”
- “Email mode: slightly more detail, still short.”

C) AGENTS.md (rules + how to operate)

AGENTS.md is your employee handbook.

Add the rules you will enforce.

# AGENTS.md

Priorities:
1) Protect customer trust
2) Save owner time
3) Keep outputs short and actionable

Rules:
- Never message customers/vendors without approval.
- Ask 1–2 questions max if info is missing.
- Log commitments and follow-ups to memory/YYYY-MM-DD.md.

Screenshot description:
- “Editing USER.md with business name + hours + policies.”

Step-by-step: fill these files in 25 minutes

• [ ] USER.md: paste your business name, services, service area, hours
• [ ] USER.md: add top 5 customer questions you answer all the time
• [ ] USER.md: add 3 hard boundaries (pricing, timelines, refunds, etc.)
• [ ] SOUL.md: choose tone, message length, and formatting rules
• [ ] SOUL.md: add the draft-only rule
• [ ] AGENTS.md: add approval and overpromising guardrails
• [ ] AGENTS.md: add a note-taking rule (memory)

If you do not know what to write, start with messy bullets. Clarity comes from use.

5) Step 4 — Send your first message (the handshake test)

Now you do the simplest test.

Send a message like:

Summarize what you know about my business from USER.md.
Then ask me 3 questions to fill any gaps.

You are looking for two signals:
- it correctly reflects what you wrote in USER.md
- it asks sensible questions

Once this works, you have a real foundation.

What a “good” handshake looks like (fast check)

A good response:
- uses your exact services and service area
- does not invent policies you did not write
- asks missing details like hours, service radius, intake questions

A bad response:
- claims you offer services you do not offer
- promises fast arrival times
- asks 10 questions in one message

If the response is bad, do not “argue” with the agent. Edit the files.

OpenClaw is file-driven. Fix the source.

If you want to skip the “what should I write in these files?” part, the OpenClawCrew Starter Kit ($49) gives you copy/paste workspace files and a weekend checklist. You still customize it, but you start from a working baseline.

6) Step 5 — Connect Telegram/WhatsApp (choose one first)

Channels are just “phone lines.”

You can add many later, but start with one.

Your goal:
- you can message the agent in Telegram/WhatsApp
- it replies in the same place
- it uses the same workspace files

Screenshot description:
- “Telegram chat showing the agent responding to the handshake test.”

Quick channel checklist

• [ ] I can message the agent from my phone
• [ ] The agent replies in the same thread
• [ ] The agent is using my workspace files (not a blank/default profile)
• [ ] I know how to disable the channel if needed

For a local business, Telegram is often the easiest first channel because it is clean, fast, and reliable.

7) Step 6 — Add your first ‘skill’ or automation

Pick one workflow that saves time weekly.

Two great starters:

Option A: Lead follow-up drafts

Inputs: - a lead message

Outputs:
- reply draft
- follow-up draft
- 1–2 clarifying questions

Measurable time saved:
- If you get 10 leads/week and each reply takes 4 minutes, that is 40 minutes.
- If OpenClaw drafts in 30 seconds and you approve in 30 seconds, you cut that to about 10 minutes.
- That is 30 minutes back every week, and the speed usually boosts close rate.

Plumber example:
- “What’s the address and what’s happening? Any active leak? Please send a photo.”

Real estate agent example:
- “What neighborhood, price range, and timeline? Are you already pre-approved?”

Option B: Daily summary

Inputs: - calendar, tasks, recent messages

Outputs:
- top priorities
- follow-ups
- short end-of-day summary

Measurable time saved:
- 10 minutes of “what was I doing” every morning is 50 minutes/week.
- A daily brief cuts that down to 2 minutes.

Keep everything in draft mode at first.

8) Step 7 — Add a HEARTBEAT checklist

HEARTBEAT.md is a tiny checklist the agent reads during heartbeat runs.

The official guidance is: keep it short.

Here is a safe starter:

# HEARTBEAT.md

1) Draft replies to any new leads from the last 24 hours. Do not send.
2) Draft “Today’s priorities” (max 5 bullets).
3) Append decisions + open loops to memory/YYYY-MM-DD.md.

If nothing needs action, reply HEARTBEAT_OK.

This turns OpenClaw into a routine.

HEARTBEAT examples by business type

Plumber:
1) Draft missed-call text backs.
2) Summarize today’s jobs and parts needed.
3) Log any follow-ups (estimates, warranty, photos).

Bakery:
1) Draft replies to custom order inquiries.
2) List tomorrow’s pickups and prep list.
3) Log any supply issues or customer changes.

Fitness coach:
1) Draft replies to new inquiries.
2) List today’s sessions and prep notes.
3) Log client follow-ups and renewals.

9) Troubleshooting (non-technical)

“It’s not responding”

- Is the Gateway running? - Are you messaging the right channel/account? - Did you change anything recently?

“The tone is wrong”

Fix SOUL.md first. - shorten it - add examples - add formatting rules

“It forgets important details”

Fix USER.md and memory habits. - add stable business facts to USER.md - log decisions and follow-ups daily in memory/YYYY-MM-DD.md

“I’m worried about it messaging customers”

Good instinct.

Add or repeat this rule in AGENTS.md and SOUL.md:

- Draft only.
- Never send externally without approval.

Common mistakes (and how to avoid them)

1) Trying to automate everything on day one
- Fix: set up one customer-facing automation and one internal automation.

2) Leaving USER.md too vague
- Fix: add hours, service area, and “what we do not do.”

3) Allowing the assistant to promise pricing
- Fix: put the “no price promises” rule in SOUL.md and AGENTS.md.

4) Making HEARTBEAT.md a long to-do list
- Fix: keep it to 3 items. Make it repeatable.

5) Not logging decisions
- Fix: add one rule: “write open loops to memory every day.”

10) Your 7-day rollout plan

You do not need a perfect setup. You need a useful assistant next week.

• Day 1: Fill USER.md, SOUL.md, AGENTS.md.
• Day 2: Add one automation (lead drafts or daily summary).
• Day 3: Start the memory habit (daily logs).
• Day 4: Add a better template for customer replies.
• Day 5: Add a weekly summary.
• Day 7: Consider a second agent (receptionist vs ops).

Your goal isn’t a perfect setup. It’s a working assistant that saves you time next week.

If you want pre-built templates for all of this, check out the OpenClawCrew Starter Kit ($49). It’s the fastest way to start from a clean, SMB-ready setup instead of building everything from scratch.

Mini-FAQ

Do I need to code?
No. If you can edit a text file and follow a checklist, you can run OpenClaw.

Can it send messages automatically?
Yes, but do not start there. Start with drafts and approvals.

What if my business info changes?
Edit USER.md. That is the source of truth.

What if I have a team?
Start with one owner workspace, then create a second agent later for “reception” or “ops.”

How long until it saves time?
Usually the first week, if you use one workflow daily.

---

Related Guides

- What Is OpenClaw? /guides/01-what-is-openclaw - Workspace Files Explained: /guides/02-workspace-files - HEARTBEAT.md Deep Dive: /guides/03-heartbeat-md - OpenClaw Skills Explained: /guides/06-skills