AGENCY PRICING & RETENTION
SITETRAIL CERTIFIED
Your learning path: 22 lessons.
Module 04 / Lesson 13 · Read, apply, check
Design onboarding that turns the signed promise into a shared operating system for the account.
Before the kickoff, compare the signed scope with the sales notes and any promises made during negotiation. Identify differences while they are still easy to resolve. The delivery lead should know the client’s priority, why the chosen package fits, what was excluded and which assumptions remain untested. Do not ask the client to repeat every discovery answer because internal teams failed to share information. Prepare a concise account brief and use the kickoff to confirm or correct it. This shows continuity and prevents the first delivery meeting from quietly replacing the service the client thought they had purchased.
Name the agency owner, client decision maker, technical reviewer and backup contacts. Agree the communication channel, meeting rhythm, response windows and escalation route. Specify where current documents and approvals will be stored and how versions will be identified. Keep the system simple enough that people will actually use it. A large folder structure does not compensate for uncertainty about who can approve a claim. Record the supplier and media-route responsibilities as well, especially when the client controls publication selection through the Marketplace while the agency coordinates preparation and reporting. Everyone should understand which decisions belong to whom.
Request the minimum information needed for the first agreed stage: product facts, customer permissions, spokesperson availability, existing research and relevant commercial context. Explain how each input will be used and who will see it. Avoid collecting sensitive records simply because a generic intake form has space for them. Create a claim register that distinguishes approved facts, unverified assertions and material requiring permission. If evidence is missing, update the plan rather than filling the gap with confident language. Onboarding should improve the quality of the campaign’s starting assumptions, not merely complete an administrative checklist before production begins.
Choose an early output that demonstrates the working relationship: a corrected message brief, a usable evidence map or an agreed campaign calendar. It should connect directly to the client’s priority and create a decision, not be a decorative welcome document. Review the onboarding process after the first cycle. Check whether the named approver is responsive, whether the team has the required access and whether the scope still fits the evidence. Resolve small operating problems before they become a pattern of delay. A strong start makes expectations observable and gives the account team a practical basis for later reviews.
Fictional Meridian onboarding workspace. Named responsibilities prevent vague commitments.
| Owner | Responsibility | Required input |
|---|---|---|
| Account lead | Campaign coordination | Signed scope and agreed milestones |
| Technical reviewer | Accuracy of product claims | Evidence and corrections |
| Commercial approver | Final client decisions | Three-day review window |
| Client source lead | Customer permissions | Specific permission status, not a bulk data dump |
Resolve the second-market conversation before the team begins.
Show where missing permissions affect the schedule.
Agree any spokesperson substitution and update ownership.
Reconcile scope, sales promises and assumptions.
Name owners, reviewers and approval channels.
Build an evidence and permission register.
Create an early output that supports a decision.
Fictional agency Meridian signs a regional technology client for a focused campaign. Before kickoff, the account lead discovers that sales discussed a possible second market but the signed package covers one. She marks the second market as a future option and confirms that distinction with the client. The kickoff names one technical reviewer and one commercial approver, sets a three-day review window and creates a shared claim register. The first input request asks for product evidence and customer permissions, not a bulk export of confidential customer records. Within a week, the agency delivers an approved message brief and a calendar showing where missing permissions affect the launch sequence. At the first review, it replaces an unavailable spokesperson with another qualified expert by agreement. The client sees progress and a clear decision process before the campaign begins to generate external results.
Another agency sends a generic welcome pack, then lets three team members request the same documents separately. Nobody checks the sales discussion, so the client assumes the second market is included. The writer uses an unverified claim from an old presentation because no approved source register exists. These problems later appear as scope disputes and quality failures, but their roots are in an onboarding process that collected files without establishing authority or evidence.
A fast kickoff is not necessarily a strong start. Speed matters when it creates usable clarity; it becomes costly when the team skips the distinction between signed scope, informal possibilities and verified facts. A short operating map and a meaningful first deliverable can do more for trust than an elaborate onboarding presentation.
Use appropriate access controls and client permissions for shared material. Collect only information needed for the work, and follow the agreed handling requirements. Onboarding does not authorize new media purchases, broader data sharing or extra markets unless the relevant client decision and scope change have been recorded.
Do this today · 30 minutes
Build Meridian’s kickoff checklist and first-week deliverable.
Use a document or spreadsheet and the fictional case in this lesson. Work with synthetic information; no purchase, real client records or actual transaction is required.
Before: Reconcile scope, sales promises and assumptions.
After: Create an early output that supports a decision.
Notes stay in this browser. Download a copy to keep them.
Ask a colleague to challenge the assumptions. Record the decision, the evidence still needed, its owner and a review date before applying the plan to a real agency.
Before you move on
Your new client remembers a second market discussed during sales, but the signed package covers one. Several people will review technical claims, and the writer has an old presentation with unverified figures. What should onboarding establish before campaign production starts?
Next lesson →Sitetrail Guest Post Marketplace: current inventory
Lesson edition 1.0 · References reviewed 16 October 2026 · Practical exercise reviewed 16 October 2026. Examples are illustrative teaching scenarios.
Sitetrail service · Guest Post Marketplace
Choose from thousands of publications in the Sitetrail Guest Post Marketplace. Compare audience fit, relevance and budget, then select the opportunities that support your client’s campaign.
Build opportunities for relevant referral traffic, credible media presence and useful discovery. Your agency chooses the mix. Use the marketplace to support a deliberate outreach strategy, and explain the nature and terms of each selected opportunity clearly to your client.
Publication availability and terms vary. Evaluate each opportunity on its own merits; no ranking, coverage or AI citation outcome is guaranteed.
Clear scope. Healthy margins. Lasting client value.
Use the worksheets to turn each lesson into a real decision. Improve the business as you learn from delivery costs, client decisions and reliable account evidence.
Course outline · Free assessment · Privacy
No account is required. Progress, first-attempt lesson answers, worksheets and assessment results are stored in this browser when storage is available. They do not sync across devices. Download copies to retain them; clearing browser data removes local records.
Your free trial starts automatically. No license key is needed yet.
