What to remember
- Client workspaces should separate data, authors, access, drafts, schedules, and reporting.
- Voice needs evidence, examples, an avoid-list, and author approval—not a generic tone label.
- The workflow should expose blockers before they threaten the publishing calendar.
- Analytics should produce a client decision and next brief, not only a branded dashboard.
01Keep every client's context cleanly separated
Client separation is more than a folder name. Each workspace should have its own members, roles, source records, author profiles, strategy, draft board, LinkedIn connections, calendar, analytics, billing context, and audit history.
That separation reduces accidental publishing, voice contamination, and unauthorized access. It also makes offboarding possible: the agency can identify which assets, sources, drafts, and records belong to the client without reconstructing the account from messages and personal documents.
Access
Invite only the team members and client reviewers who need the workspace.
Publishing identities
Make the intended LinkedIn profile or Page visible on each scheduled item.
Content context
Keep client pillars, audience, offers, proof, and prohibited claims out of other client workflows.
Auditability
Retain a history of important role, draft, approval, publishing, and integration actions.
02Turn voice from intuition into an editable system
A useful voice profile contains the author's audience, positioning, content pillars, tone descriptors, phrase bank, avoid-list, and examples of past writing. It should evolve when the client rejects language or explains a nuance the agency missed.
Connect every draft to the intended author and source. That prevents a ghostwriter from carrying one founder's cadence, stories, or claims into another founder's content simply because both clients operate in the same industry.
- 1
Collect evidence
Use past posts, interviews, calls, emails, talks, and edited drafts—not adjectives alone.
- 2
Define the boundaries
Record claims the author will not make, phrases they dislike, and topics that require approval.
- 3
Draft from sources
Tie the content to client-approved evidence instead of asking AI to invent expertise.
- 4
Learn from edits
Update the voice profile when repeated client changes reveal a durable preference.
03Run one repeatable pipeline across every account
The agency operating model should stay consistent even when strategy and voice differ. Capture sources, create ideas, assign a draft, complete internal editing, request client review, record explicit approval, schedule the final version, and attach the published result.
Use board and calendar views for different questions. The board shows where work is blocked. The calendar shows whether the approved pipeline can support the promised cadence. Neither should require a status meeting to interpret.
- 1
Source ready
The account has enough approved evidence to develop a substantive angle.
- 2
Draft assigned
One writer owns the deadline and knows the intended author, format, and goal.
- 3
Internal edit
The agency resolves structure, truth, voice, and risk before using client attention.
- 4
Client review
The client sees one coherent version and a deadline for explicit approval.
- 5
Scheduled and learned
The exact approved post is queued, then its result informs the next content brief.
04Report the decision the content produced
Clients do not need a screenshot of every metric. They need to know whether the program reached the intended audience, which subjects and formats created useful response, what the agency learned, and what will change next month.
Connect impressions, reactions, comments, and other available platform metrics with profile movement and qualified business signals. Group the results by author, pillar, format, hook, and source type. Then assign the next experiment in the same workspace.
Goal: build credibility with operations leaders
Learning: specific process teardowns drove the highest-quality comments
Decision: interview the client about two operating workflows next month
Owner: account strategist • Draft deadline: August 8
05Evaluate agency software with a live client workflow
During a trial, create two client workspaces with two different author voices. Invite a reviewer, create a source-backed draft, request changes, approve the final version, schedule it to the correct identity, and locate the record afterward. This exposes separation and permission problems before the agency migrates its entire client base.
Workspace limits
Confirm how many client workspaces, author profiles, team members, and LinkedIn connections the plan supports.
Role boundaries
Verify who can view sources, edit drafts, approve, publish, manage integrations, and change billing.
Failure handling
Test how a failed scheduled publish is surfaced, retried, and recorded without duplicate posting.
Data portability
Confirm how clients receive content and reporting data when the relationship ends.
What an agency content system should control
| Decision factor | Minimum requirement | Why it matters |
|---|---|---|
| Client separation | Distinct workspaces, members, sources, authors, connections, calendars, and analytics | Prevents access errors, voice contamination, and accidental publishing |
| Voice and source | Evidence-backed author profiles and traceable source material | Protects authenticity and reduces invented or cross-client claims |
| Approval | Named owner, reviewer, deadline, comments, versions, and explicit final approval | Reduces rework and proves which copy the client accepted |
| Publishing | Visible identity, date, time zone, state, failure handling, and final URL | Makes the calendar operationally trustworthy |
| Learning | Metrics connected to pillars, formats, hooks, sources, and next actions | Turns reporting into better briefs and stronger retention |
Frequently asked questions
Can an agency manage multiple clients in Forgo?
Forgo's agency model is designed around multiple workspaces so client sources, voices, members, drafts, connections, schedules, analytics, and audit context can remain separated. Confirm current plan limits during purchase.
Can clients approve posts without editing everything?
A clear workflow can give client reviewers visibility into the draft, comments, and approval state while reserving broader workspace and integration controls for the agency team.
How should an agency store a client's voice?
Use approved examples, past writing, audience and positioning context, tone descriptors, phrases, an avoid-list, content pillars, and a record of repeated edits. Keep it client- and author-specific.
What should happen when a scheduled post fails?
The system should preserve the draft, show a clear failure state, record the attempt, notify the right owner, and support an intentional retry without creating a duplicate post.