Pricing
You are not outsourcing tasks. You are installing leverage that compounds. We build code-first systems that make AI reliable, repeatable, and safe to run at scale.
Choose a focused workflow build or a full Content OS install. Both start with a scope definition and a fixed price proposal.
Built from the same playbook that powered Statsig’s marketing engine.
Package A
Workflow build
Automate a specific growth or content bottleneck.
From $22,000
Typical timeline: 2–3 weeks
Includes
- 2 production-ready workflows (AirOps)
- Input→output contract defined up front
- Prompt + logic design (not templates)
- QA pass + edge-case handling
- Handoff docs + walkthrough
Best for
- Competitive content
- SEO briefs/drafts
- Research synthesis
- Transcript→publishable output
Package B
Content OS install
A code-first content system that AI can safely execute.
From $50,000
Typical timeline: 4–6 weeks
Includes
- Code-based site or docs hub (no CMS)
- Markdown as the source of truth (git-backed)
- Content schemas + folder conventions
- Guardrails: validation, linting, and safe execution patterns
- AI execution hooks for Codex/Claude Code (documented)
- Example modules for SEO + competitive + internal context
Note: Content OS replaces your website.
Best for
- Teams that want compounding leverage
- Teams avoiding tool lock-in
- Teams with lots of institutional knowledge
Which option should I choose?
If you want…
Fix one bottleneck fast
Minimal internal change
Tool-centric automation
Targeted workflow outcomes
Short-term speed with clear ROI
Choose workflow build
If you want…
Build a reusable foundation
Standardize the whole content pipeline
System-centric operations
Compounding leverage over time
Long-term operational control
Choose content OS install
Ongoing support
For teams that want iteration after launch.
$6,000–$12,000 / month
- New workflows/content types
- Prompt and schema iteration
- Model/tooling/integration upgrades
- Quarterly system cleanup and refactors
Not required—most teams start with a build, then add support once it’s live.
FAQ
What’s the difference between a workflow and a content OS?
A workflow build transforms your growth content creation workflow into an automated, AI-powered system. A Content OS install changes how content is stored, governed, and executed so multiple workflows can run safely. One is a sharp tool. The other is the system that makes tools compounding.
Do you work with existing tools like Notion, GA4, Search Console, HubSpot?
Yes, as inputs or reporting surfaces. We prioritize code-first sources of truth, but we can integrate common tools where they already hold real data. We’ll map the workflow boundaries during the scoping call.
What do you need from us to start?
A point person, access to the relevant source content, and a clear business outcome. We start with a scoping call and leave you with a written scope + fixed price proposal.
Who owns the system?
You do. The code, content, and documentation live in your repo and your tooling. Our job is to leave you with a system you can run without us. As much as we love the collaboration, we set your team up to be self-sufficient experts.
Can my team maintain this after handoff?
Yes. We provide documentation, conventions, and a walkthrough. If you want ongoing support, we can stay involved, but the system is designed for self-sufficiency.
What if we don’t know the exact scope yet?
That is normal. The scoping call exists to clarify the inputs, outputs, and constraints. You will receive a written scope and fixed price proposal before any build starts.
Do you do hourly work?
No. We work on fixed scopes with outcome-oriented pricing. That keeps incentives aligned and delivery predictable.
Install leverage
If your bottleneck is speed or consistency, this is designed for you.
Most builds start within 2–3 weeks depending on availability.