How pricing works
Pricing is based on scope. Each project has clear deliverables and an agreed price before work begins. Most teams start with one project. Ongoing support is available if the work calls for it.
Pricing at a glance
On smaller screens, scroll horizontally to compare all five columns.
| Engagement type | Typical range | Typical timeline | Best fit when | Learn more |
|---|---|---|---|---|
| Diagnostic offers | $5,000-$7,500 | About 2-3 weeks | You need a fast read on where trust is breaking before committing to a bigger project | Diagnostic Audits |
| Translate the Ask sprint | $2,500-$5,000 | About 1-2 weeks | The business need is urgent but the request is still too fuzzy to scope cleanly | Translate the Ask |
| Core service engagements | Starts at $5,000 | Scoped to the service | The problem is clear enough for senior judgment and hands-on execution through the appropriate service line | Services |
| GTM Metric-Certification & Governance Sprint | $40,000-$150,000 | About 4-10 weeks | Marketing, ad-platform, product, revenue, and finance teams need one certified semantic layer for the metrics that dashboards, copilots, board reports, and AI agents will answer from | Data Foundation |
| Predictive GTM Models with Lift Proof | $25,000-$150,000 | About 4-12 weeks | The team is ready to operationalize lead, churn, expansion, budget, or lifecycle models and prove whether they changed revenue behavior with holdout/lift evidence | Predictive GTM Models |
| AI-Ready Data Diagnostic | $5,000-$7,500 entry / $12,000-$20,000 flagship | About 2-4 weeks | Leadership has a specific AI-readiness question, but the underlying marketing, ad, product, and revenue data may produce wrong answers | AI-Ready Data Diagnostic |
| Optional Managed Run + Measure | $5,000-$25,000/mo | Month-to-month after proof | A shipped diagnostic, semantic layer, model, or measurement system is valuable enough to keep governed, monitored, evaluated, and re-proven | Managed Run + Measure |
What affects price
Pricing depends on the scope and complexity of the work. A focused problem with clear ownership is usually easier to scope. Work that spans multiple systems, teams, or business rules takes more time and coordination.
The scope also grows when the work needs to support reporting, workflows, or multiple teams. We account for that before the project begins.
Questions about pricing
Can we start with a diagnostic before a larger engagement?
Yes. A diagnostic helps identify the next step and how much work may be needed.
What makes a project more expensive?
Price increases with scope and complexity.
Do we need a clean warehouse or mature data team before working with Domain Methods?
No. Many engagements start because the underlying data, systems, or ownership are part of the problem.
Do you need system access before we start?
No. Screenshots and exports are usually enough to start. Direct system access comes later and stays client-controlled and limited to the scope of the work.