LotsBlog
The agency operator's onboarding moment is familiar: a new client signed yesterday, and the clock is already running. The old process — gather brand assets, set up a domain, write a strategy doc, build an editorial calendar, configure approval flows — takes a full day at best. The system version takes 30 minutes from contract to first draft queued.
Every hour spent setting up a blog is an hour not spent growing the client's archive. For agencies running 5, 10, or 30 client blogs, the setup workflow is the bottleneck that determines whether the program compounds or stalls before it starts. Here is the 30-minute version.
Step 1 — Capture client strategy as a template (5 minutes)
Do not write a custom strategy doc for every client. Send a 4-question brief that captures everything the agent needs to operate:
- Who is the target reader? Industry, role, primary pain point.
- What is the topic territory? The 3-5 subject areas the blog should own.
- What is the publishing cadence? Three posts per week is the strong default, but some clients need one per week or two per week.
- What is the brand voice reference? One example post they love, plus any words to avoid.
The client answers in a shared doc or a 5-minute call. Paste the answers into the blog strategy fields inside the workspace. The agent now has context. It knows who to write for, what to write about, how often to publish, and how to sound.
Agencies that scale this step turn the four questions into a template that never changes. The guide to running 30 client blogs from one workspace walks through how the same template scales from client one to client thirty.
Step 2 — Configure the agent (5 minutes)
Every blog in the workspace gets its own agent. The setup is the same regardless of blog number:
- Name the blog
- Connect the custom domain if the client has one
- Set the default post type (article is the default; switch to listicle, poll, or video post if the client's format calls for it)
- Confirm the publishing cadence
The agent inherits the strategy from Step 1. It does not need re-training per client. The first draft lands in the queue within minutes of the setup being complete.
Step 3 — Connect brand assets (5 minutes)
The public surface needs to look like the client, not the agency. Upload:
- Logo (light and dark variants if available)
- Brand colors (primary and secondary)
- Custom domain (CNAME or A-record setup — most DNS providers handle this in under 5 minutes)
- Social profiles (for the newsletter and social distribution hooks)
Once the assets are in, the blog is publicly ready. The client can preview it before any content goes live. Adjustments at this stage are cheap. Adjustments after 20 published posts are not.
Step 4 — Set cadence and approval flow (10 minutes)
This step determines whether the program runs smoothly or bottlenecks. Set three things:
- Publishing cadence. Three posts per week is the default for agency clients. It builds a cluster of 8-15 posts per quarter, which is the minimum for topical authority to start compounding. One post per week is the floor.
- Approval chain. Agent drafts → agency editor reviews (quality, voice, claims) → client approves → publish. Each tier can have its own SLA. A 24-hour SLA for client review keeps the cadence moving.
- Notification preferences. The agency editor gets notified when a draft is ready. The client gets notified when a draft needs approval. Email, web, or Telegram — each role chooses.
The approval chain is configurable per client. Some clients want to see every draft. Others delegate approval to the agency after the first month. The agency content approval guide covers how to adjust the flow without breaking the cadence.
Step 5 — Invite the client (5 minutes)
Add the client as a blog member with the appropriate role. They see:
- The blog's strategy and upcoming content queue
- Drafts awaiting their approval
- Published posts and analytics
- A clean review surface where they can approve, request changes, or reject
No training needed. The client does not need to learn a CMS, an editor, or a dashboard flow. They see drafts inline with the brief, click approve or suggest changes, and the agent cycles the post back if needed. The same surface works for the agency's internal editor review.
Where the system multiplies
The 30-minute workflow works the same for blog number 1 and blog number 30. The agency's playbook gets faster with each onboarding because the template, the agent configuration, the approval chain, and the client invitation steps are identical. The only variable is the client's strategy answers.
Agencies that treat onboarding as a repeatable system instead of a per-client project scale their content operations without scaling their team. The 30-minute clock starts the moment the strategy answers land. Everything else is the system.
FAQ
How do I customize the workflow per client without breaking the template?
The strategy template captures the customization — audience, topic territory, voice. Everything downstream inherits from those answers. If a client needs a different cadence or a custom CTA library, those are configurable fields, not workflow overrides.
What happens if a client wants to change the cadence mid-contract?
Update the cadence in the blog settings. The agent adjusts the planning queue and the draft schedule automatically. No migraines.
How does the approval notification loop work for different roles?
The agency editor gets notified when a draft needs quality review. The client gets notified when a draft is ready for final approval. Each role's notification preference (email, web, Telegram) is independent. If a client prefers Telegram approvals and the agency prefers email, both work.
See how agencies run client blogs at scale. → lots.blog/for-agencies