Fox & SantiagoTechnology, applied.Call (877) 244-9687

How we work

We build what your people keep using.

No more chasing status. No more retyping the same work into three systems. No more late calls to find out what happened. We come in, see how your work really runs, and take the headaches off your team, with the systems you already have. Your people keep doing the work they are good at. The busywork between them goes away.

A pencil process sketch on a clipboard lying on a steel workbench

What we bring

We have run operations ourselves, and we have written down what we learned: our guides map where the systems businesses run actually break, with the vendor documentation and regulations cited. Every Spec starts from that, so what we build holds up when the work picks up, not just in the demo.

Built with your people, so they use it

Your people help design it. The people in the workflow are interviewed in the Spec, the Build is tested with them where they work before it goes live, and the first 30 days after launch are spent clearing whatever slows them down. We're not taking people out of the loop. We're taking out the retyping, the chasing and the second trips, so the same team gets more done.

After an acquisition or a change in ownership

New owners inherit an operation that runs on a few people's memory and a stack of software nobody fully mapped. That's where we do our best work: one Spec shows you where money is leaking between systems and hands, which steps only exist to make up for other steps, and what can be automated without breaking what your people do well. Then we fix the problem that's costing you the most, and keep going down the list.

The ladder

Engagement Price What it includes
Workflow Spec Varies by deployment, paid at signing Up to five business days. Observation on site or remotely where the work happens, up to 12 interviews, baseline measurement, the issues found and ranked by what they cost you, a workflow map, the business case, an adoption design, the build specification, a fixed Build proposal, and an approval brief your sponsor can forward.
Production Build Varies by deployment, fixed after the Spec Scoped in the Spec to the most pressing issues it found, for a named group of users, with up to two standard integrations, instrumentation, training, operating documentation, a handover pack and 30 days of stabilization. Six weeks from the access gate to release, then a 30-day live period with your team. Paid 50 percent at kickoff, 30 percent at technical acceptance and 20 percent at operational acceptance, when you sign that the tool is live with the agreed users at the end of the 30-day live period.
Embedded Adoption Set in the Spec conversation The next issue on the list, every month: one bounded improvement cycle each month, monitoring, business-hours support, a weekly operator review, a monthly executive review and a managed change queue. Six-month minimum.

The Spec is not credited against the Build: you keep the map, the business case and a fixed Build price either way, including a no-go.

The clock

The six weeks start at the access gate, when the four roles on your side are named and access is granted. The clock pauses while the work is blocked on your side, with the reason recorded, and ends at release to the agreed production environment with the agreed user group.

Before you buy

Everything here is answered in full elsewhere on the site; this is the short version, in one place.

  • The fit call and the Spec are two separate steps. The fit call is free and twenty minutes. The Workflow Spec is paid, priced by deployment, and you keep what it produces whether or not you build with us.
  • The Spec fee is not credited against the Build. It is priced to be worth its fee even when the answer is no. Why.
  • Travel. Anywhere in the United States, our team comes to your site, and travel is included in the Spec. Outside the United States, travel is billed at cost as its own line. How site visits work.
  • What you provide. An executive sponsor, the four roles on your side named at the access gate, access to the systems involved, the data, training time and the crew's part in the rollout.
  • What you own. The bespoke tool, your data and your production accounts, with the copyright assignment in writing. Who owns the tool.
  • The handover. 30 days of stabilization are included, then Embedded Adoption, a keep-the-lights-on arrangement or a formal handover with no ongoing obligation. Every Build ships with a handover pack: the architecture, a runbook, a credentials inventory, a data map, the models and providers used, and the documented paper or spreadsheet fallback your team switches to if the platform is ever unavailable. What happens after launch.
  • Security and AI. Where your data goes, which AI providers see it and on what terms: security and where does our data go.

How to start

The first step is a twenty-minute fit call. Book one here, or call (877) 244-9687. If the workflow, the sponsor and the path to access are real, the next step is the Workflow Spec.

Questions people ask

Why is the Spec paid instead of free?

Because a real specification is real work: on-site observation, up to twelve interviews, baseline measurement and a fixed proposal. A free estimate is a sales pitch; a paid Spec is a deliverable you keep, whether or not you build with us.

Is the Spec fee credited against the Build?

No. The Spec stands on its own and is priced to be worth its fee even when the answer is not to build.

How do you make sure your team uses what you build?

We build it with them. The Spec interviews the people in the workflow and includes an adoption design that names who uses the tool and when. The Build is tested with those people before go-live, 30 days of stabilization after launch fix whatever gets in their way, and Embedded Adoption keeps fixing the next issue.

Can a Spec end in a no?

Yes. Go, no-go and recommend-against are all valid outcomes. A no-go that saves a company from building the wrong thing is a successful Spec.

Do you work outside Idaho?

Yes. Service is across the United States, and any country can request a site visit. Anywhere in the United States, our team comes to your site, and travel is included in the Spec. Outside the United States, travel is billed at cost as its own line.

Who owns what you build?

You own your data, your production accounts and the bespoke tool after payment, with the copyright assignment in writing. We keep our reusable methods, templates and general components.