Pricing
Clear scope. Clear price. No mystery proposal.
Fox & Loom is a consulting and implementation company. The prices below are fixed, so you don't have to request a mysterious custom quote to know what things cost.
Start with understanding.
Before recommending that anything be built, we need to understand what's actually happening.
Company AI Readiness & Opportunity Assessment
A full-company assessment of how ready your organization is for AI and automation—and what may be worth pursuing.
Both are full-company assessments. The difference is depth and complexity, not company size.
Two engagement levels.
Every dimension below is covered by both levels. The only difference is depth and breadth.
| Standard | Comprehensive | |
|---|---|---|
| Price | $1,480 | $3,480 |
| Entire company | ✓ | ✓ |
| Operating environment | ✓ | ✓ |
| Workflow investigation | ✓ | ✓ |
| Systems review | ✓ | ✓ |
| Data readiness | ✓ | ✓ |
| People & process | ✓ | ✓ |
| Business value | ✓ | ✓ |
| Risk | ✓ | ✓ |
| Opportunity analysis | ✓ | ✓ |
| Prioritization | ✓ | ✓ |
| Depth / breadth | Standard | Expanded |
What's the difference?
Both options assess the entire company. The difference is the depth, breadth, and complexity of the assessment work required. We determine the appropriate level based on your operating environment—not simply your employee count.
Standard
$1,480
Best when the company has a relatively straightforward operating environment, a manageable number of core workflows and systems, and limited organizational complexity.
Comprehensive
$3,480
Best when the company has more complex or interconnected workflows, multiple operational areas, more systems/data dependencies, multiple locations, or greater organizational complexity requiring additional investigation.
Decide to build? 50% of your assessment fee is credited toward implementation.
If you proceed with an implementation package within the defined period, 50% of your assessment fee is applied toward the implementation.
If it's worth building, we build it.
Implementation is priced around the scope and outcome of the work—not an arbitrary number of systems or AI agents.
Single Workflow
$7,480
One defined business process automated from trigger to outcome. It can involve multiple steps and multiple systems working together to accomplish one defined business outcome.
Included
- One defined business workflow
- Workflow design
- Required integrations for that workflow
- AI and/or deterministic logic
- Testing
- Deployment
- Documentation
- Training
- Operations Diagnostic
- 60-Day Deployment Assurance
Not included
- A second unrelated workflow
- A new business process
- A new unrelated integration
- Business-process redesign outside the agreed workflow
- Additional features that change the agreed outcome
Connected Operations
$14,850
Multiple workflows that are directly related and operate together as part of the same operational process. The key word is connected—these are not simply several unrelated automations purchased together.
Included
- Multiple related workflows
- Multiple systems as reasonably required
- Required integrations
- Orchestration between workflows
- State management where required
- AI and/or deterministic logic
- Testing
- Deployment
- Documentation
- Training
- Operations Diagnostic
- 60-Day Deployment Assurance
Not included
- Completely unrelated business processes
- A separate workflow that has no meaningful relationship to the agreed operational chain
- Major expansion into another operational department
- New scope added after the project is defined
Operations Network
$24,800+
Multiple operational areas working together across a broader portion of the business. This is not simply 'more workflows'—it is a broader operational system involving multiple areas of the business.
Included
- Multiple workflows
- Multiple operational areas
- Multiple agents where appropriate
- Complex orchestration
- Multi-location support where applicable
- Broader architecture
- Multiple interconnected systems
- Testing
- Deployment
- Documentation
- Training
- Operations Diagnostic
- 60-Day Deployment Assurance
What determines the tier?
- Not the number of AI agents.
- Not the number of software subscriptions.
- Not the number of API calls.
We scope the work around the business outcome and workflow complexity.
A workflow is a repeatable business process that starts with a trigger and produces a defined outcome.
- When an estimate is sent, follow up with the customer until they respond or the opportunity is closed.
- When a job is completed, send the appropriate invoice and initiate the customer payment follow-up process.
What every implementation includes.
Design
We define how the workflow should work.
Integration
We connect the systems required for the workflow.
Build
We implement the appropriate AI and/or deterministic automation.
Testing
We test the workflow before deployment.
Deployment
We put it into operation.
Documentation & Training
Your team knows how it works and how to use it.
Operations Diagnostic
You receive the diagnostic artifact documenting the delivered system.
60-Day Deployment Assurance
We stand behind the deployed workflow for the defined assurance period.
How we define scope.
The tier names alone aren't enough. Here's exactly what we mean by the words we use, so you can tell which tier fits your project without speaking to anyone.
- What do we mean by "workflow"?
- A workflow is a repeatable business process that starts with a trigger and produces a defined outcome.
- When an estimate is sent, follow up with the customer until they respond or the opportunity is closed. That is one workflow.
- When a job is completed, send the appropriate invoice and initiate the customer payment follow-up process. That is one workflow.
- What is a system?
- A system is a software platform or service that participates in the workflow.
- CRM, estimating software, accounting software, email, SMS, payment systems, internal databases.
- From our architecture: ServiceTitan, Jobber, QuickBooks, Google Workspace, Microsoft 365, Twilio, Stripe, and a customer's internal database.
- What is an integration?
- An integration is the connection that allows the workflow to exchange information with another system.
- Estimate created in CRM → automation receives the event → customer receives SMS.
- What is an agent?
- An agent is an AI/software component that performs reasoning or actions within a workflow. Not every workflow requires an AI agent.
- Fox & Loom may use deterministic automation, traditional software logic, AI, AI agents, or a combination—based on what the workflow actually requires.
A workflow is about the business process being automated, not the number of software tools involved.
The number of integrations does not automatically determine the tier. A single workflow can require multiple integrations.
More agents does not mean a better solution.
What each tier really means.
Single Workflow · $7,480
Example
Estimate Follow-Up
- 01Estimate sent
- 02Customer receives follow-up
- 03Follow-up occurs according to defined rules
- 04Customer responds / declines / books / opportunity closes
That is one workflow, even if it touches CRM, email, SMS, calendar, and AI reasoning.
Other examples
Missed-call recovery · Estimate follow-up · Appointment reminders · Customer review requests · Invoice reminders
One workflow does not mean one software system. A Single Workflow can connect to multiple systems when those systems are necessary to accomplish the defined business outcome.
Connected Operations · $14,850
Lead → Estimate → Follow-Up → Booking
- Workflow 1: Lead captured
- Workflow 2: Estimate created/sent
- Workflow 3: Follow-up initiated
- Workflow 4: Customer books
Because these workflows are directly connected and form one operational chain, they can be treated as Connected Operations.
Completed Job → Invoice → Payment Follow-Up → Customer Communication
Again, multiple related workflows operating together.
- What does “Orchestration” mean?
- Coordinating multiple workflows or system actions so they operate together in the correct sequence. For example: lead created → estimate generated → estimate sent → follow-up begins → customer responds → booking workflow starts. The system coordinates the transitions rather than treating each automation as an isolated process.
- What does “State management” mean?
- Keeping track of where something currently is in a workflow. For example, a customer might be: Estimate Sent → Follow-Up 1 → Follow-Up 2 → Responded → Booked. The system needs to know the current state so it doesn't send the wrong message or repeat an action.
Connected Operations is about relatedness, not simply counting workflows. There is no rule such as 'three workflows equals Connected Operations.' The determining question is: are these workflows tightly connected and being designed as one operational system?
Operations Network · $24,800+
Example
Sales + Estimating + Dispatch + Customer Communication + Accounting
- 01Sales — lead capture and qualification
- 02Estimating — estimate creation and follow-up
- 03Dispatch — scheduling and job coordination
- 04Customer Communication — reminders, updates, follow-up
- 05Accounting — invoice and payment workflows
That is an Operations Network because multiple operational areas are connected.
- What does “Multi-location” mean?
- A workflow operating across multiple branches, offices, stores, service areas, or other distinct operating locations—for example, one workflow architecture supporting 20 service locations. Multi-location support does not automatically mean Operations Network; it is one factor considered when determining scope.
- What does “Multiple agents” mean?
- Multiple AI/software components performing different reasoning or action responsibilities within the broader operational system. Agents are not the unit of pricing—the business scope and complexity determine the tier.
The '+' applies when a project materially exceeds standard Operations Network scope. It is not an excuse for arbitrary pricing.
Which one is right for me?
Single Workflow
You have:
One defined business process you want to improve.
"We want to automate estimate follow-up."
Connected Operations
You have:
Several related processes that need to work together.
"We want to connect our lead, estimating, follow-up, and booking processes."
Operations Network
You have:
Multiple operational areas that need to work together.
"We want to connect sales, estimating, dispatch, customer communication, and accounting."
We don't price by the number of AI agents.
You shouldn't have to count agents to understand what you're buying.
We price based on:
- Business outcome
- Workflow scope
- Operational relationships
- Systems involved
- Integration requirements
- Complexity
- Risk
A simple comparison.
These are scope categories, not a feature-counting system. Nothing here is a hard numerical limit.
| Single Workflow | Connected Operations | Operations Network | |
|---|---|---|---|
| Defined workflows | One | Multiple related | Multiple |
| Business area | One | One or closely related | Multiple |
| Systems | As required | Multiple as required | Multiple / interconnected |
| Integrations | Required for workflow | Multiple as required | Multiple / interconnected |
| Orchestration | Simple | Yes | Complex |
| State management | When required | When required | As required |
| AI agents | When appropriate | When appropriate | Multiple when appropriate |
| Locations | Standard | Standard | Multi-location where applicable |
| Price | $7,480 | $14,850 | $24,800+ |
What happens if the project changes?
The price covers the agreed scope. New workflows, new integrations, unrelated business processes, or substantial changes to the agreed outcome are new scope.
- Can you also automate invoice reminders?
- If the original project was estimate follow-up, that is a new workflow.
- Can you also connect our new inventory system?
- That is a new integration if it wasn't part of the agreed implementation.
- Can you redesign this completely different business process?
- That is new scope.
We'd rather tell you not to build it.
Our job isn't to convince you that you need AI. If the evidence doesn't support an implementation, we'll tell you. If the problem is better solved through a process change, a simpler automation, better data, or nothing at all, that's a valid outcome.
Pricing FAQ.
- Is the assessment required?
- The assessment is the normal path when an opportunity needs investigation before implementation. Its purpose is to reduce uncertainty and determine what is actually worth building. It isn't a legal requirement, and it isn't universally mandatory—but when there's real uncertainty, it's how we avoid building the wrong thing.
- Is implementation fixed price?
- Yes. Implementation packages are defined around scope and outcome.
- What if my project doesn't fit one of the tiers?
- The Operations Network tier is designed for greater complexity. If the scope genuinely falls outside the standard packages, we'll discuss the engagement directly rather than pretending a standard tier applies. We won't slap a generic "custom pricing" label on everything.
- What happens if you decide AI isn't the answer?
- That's okay. The assessment is intended to help determine whether pursuing the opportunity makes sense. Sometimes the right answer is a process change, a simpler automation, better data, or nothing at all.
- What happens after implementation?
- Testing, deployment, documentation, training, the Operations Diagnostic, and 60-Day Deployment Assurance are all included in the implementation packages.
- Does the assessment fee apply to implementation?
- Yes. 50% of the assessment fee is credited toward implementation if you proceed within the defined period.
Not sure where to start?
Start with the Free AI Readiness Review.
We'll have a short conversation, look at your company, and help you understand whether there's something worth exploring.
Start Your Free AI Readiness ReviewFree. No obligation. No AI sales pitch.