Engagement options
Pick the starting point that matches where your content is today.
Some teams need a full system built from nothing. Others already have a calendar and just need help with writers or attribution. Below are the four ways engagements are typically scoped; most conversations start by figuring out which one fits.
Before choosing
Pricing depends on scope, not a fixed package
The figures below are directional starting ranges based on typical engagements, not fixed quotes. A first call establishes the actual scope: how many articles per month, how much internal review capacity you have, and whether writer sourcing is included or you already have a bench.
Four ways to start
Engagement options
Audit & Roadmap
from $2,400
One-time engagement, typically 2 to 3 weeks
A review of your current content output, distribution habits, and available tracking, ending in a written roadmap for what to build next.
- Content and channel audit
- Gap analysis against funnel stages
- Prioritized roadmap document
- 90-minute walkthrough call
Foundations Build
from $6,800
One-time engagement, typically 5 to 7 weeks
The full system build: calendar, brief templates, style guide, and quality checklist, plus support sourcing your first two or three freelance writers.
- Editorial calendar architecture
- Brief templates & style guide
- Quality control checklist
- Writer sourcing support
- Distribution plan for owned channels
Ongoing Engine Retainer
from $2,900 / mo
Monthly, minimum 3-month term
Continued oversight of the system after launch: calendar upkeep, writer management, QC review, and monthly attribution reporting.
- Monthly calendar review
- Writer feedback & QC oversight
- Distribution scheduling support
- Monthly pipeline attribution report
Writer Network Setup
from $3,100
One-time engagement, typically 3 to 4 weeks
For teams that already have a calendar and process but need help finding and vetting freelance writers who fit their subject matter and voice.
- Role scoping & candidate sourcing
- Paid trial-piece process
- Onboarding documentation
- Rate & scope guidance
What happens after
Every build ends with a handoff, not a dependency
The intent behind each engagement is to leave your team able to run the system without ongoing help, should you choose not to continue with a retainer. Documentation is written for your internal team to use directly, not just for us to reference.
Teams that do continue into a retainer generally do so because managing a freelance bench and monthly attribution reporting takes more recurring hours than expected, not because the initial system was incomplete.
Not sure which option fits?
Describe your current setup and we'll suggest a starting point during the first conversation, no obligation to proceed further.