Founding-stage pricing
These introductory prices are intentionally low while Bates Operations builds its first body of work. Scope is agreed before any paid work begins, and no outcome is guaranteed.
Current starting point
Start with a real 15-minute diagnosis conversation about one workflow, handoff, vendor exception, or follow-up problem. Any follow-on engagement is discussed only if there is a clear mutual fit.
Tier 1
Free
A focused 15-minute conversation to identify the strongest operational leak and the next thing worth testing.
Founding-stage offer: no obligation to buy anything. Availability is limited while the diagnosis is being refined.
Tier 2
Starting at $300
A focused 1–2 week project for documenting and improving one operational leak, with a written next-step plan and one follow-up check-in.
The exact scope and timeline are agreed before work starts. The introductory price covers one workflow focus.
Tier 3
Starting at $500 / month
Limited month-to-month support after a focused project proves useful: recurring operating conversations, prioritization, and light async questions.
Only discussed after a fit conversation. Cadence, boundaries, and the monthly scope are agreed in advance.
What is not assumed
The conversation is not an audit, forecast, or promise of a particular project. If there is a clear mutual fit for follow-on work, we can discuss a focused workflow sprint or recurring operating support, with scope and price agreed before it begins.
Founding client opportunity
I'm currently offering a small number of free founding-client conversations to STR/MTR teams while I refine the framework. Availability may change as those conversations are scheduled.
Honest feedback after the conversation and, only with permission, the ability to describe what we learned in a future case study.
Possible areas to discuss
These are examples of operating problems that may come up in a conversation, not an established service catalog.
Design a repeatable process for assigning, confirming, quality-checking, and escalating cleaning, maintenance, and turnover work across a growing portfolio.
Create consistent inspection, exception logging, rework, and sign-off steps so issues are caught before guests, owners, or team members feel the impact.
Standardize how damage, maintenance needs, photos, priorities, owners, and next steps are reported so issues move quickly from discovery to resolution.
Clarify the standard way work gets done, who owns each step, and when an issue should be handed off or escalated.
Create a simple system for capturing inquiries, assigning next steps, tracking response status, and keeping opportunities from going quiet.
Before a possible sprint
This illustrative scenario is hypothetical and not client work.