This directory connects every published playbook to its service and market. Start with the problem you are evaluating, then choose a state and a brief. Market labels identify the intended audience; they do not establish local offices, customer results, or local research. Use the guidance to define questions and evidence for your own operation.
Search by topic or business role · Read the enterprise AI guides · Understand our evidence standards
Modeled scenarios
Market labels in this library identify the intended audience. They do not show local results. These examples use assumed inputs to show how a brief turns into a plan.
Picture a vehicle wrap shop serving contractors.Contractors use trucks as moving signs. The plan sells wraps by showing the design and the owner's own route, not by claiming leads.
Assumed inputs, run through the formula of our calculator: “revenue per month” goes from $21,773 to $27,216 when “leads per month” moves from 24 to 30. A modeled scenario, not a client result.
Picture a company with an internal platform nobody outside the team understands.The platform works, but buyers and new hires cannot see how. A clear technical write-up explains the design, the limits, and the decisions.
Assumed inputs, run through the formula of our calculator: “payroll recovered per month” goes from $15,588 to $20,264 when “share automated” moves from 50% to 65%. A modeled scenario, not a client result.
Picture a practice adopting new scheduling software.Staff need a plain write-up of how the system works, what data it holds, and who can see it. It also serves as a record for audits.
Assumed inputs, run through the formula of our calculator: “payroll recovered per month” goes from $5,846 to $11,691 when “hours per person per day” moves from 1 hours to 2 hours. A modeled scenario, not a client result.
Checkable
Everything below is a fact you can check in this site's own files or documents. Nothing here is a client result.
Method
Each modeled scenario on a service page reuses the formula of a calculator on the tools pages. The formula is written under the scenario, so you can type your own numbers into the matching calculator and compare.
Limit: The formulas are arithmetic. They do not know your market, and the inputs in a scenario are assumptions.
Source: Free tools (src/components/tools/)
Policy
The site's governance document says a claim about performance, cost cuts, or business outcomes must link to evidence, be written as guidance with limits, or be removed. A location page may say a service is available in a place, not that it was deployed there unless a case study proves it.
Limit: A policy is a promise about how we write. It is not a result.
Source: Authority source governance (docs/authority-source-governance.md)
Verified revenue control planes tailored to the regulatory, market density, and unit economic constraints of active regional metropolitan markets.
Engineered revenue infrastructure for scaling operators in Salt Lake County. Deploying sub-second routing and closed-loop attribution near Temple Square.
Engineered revenue infrastructure for scaling operators in Charleston County. Deploying sub-second routing and closed-loop attribution near Rainbow Row.
Engineered revenue infrastructure for scaling operators in Polk County. Deploying sub-second routing and closed-loop attribution near Iowa State Capitol.
Engineered revenue infrastructure for scaling operators in Wayne County. Deploying sub-second routing and closed-loop attribution near Motown Museum.
Engineered revenue infrastructure for scaling operators in Baltimore City. Deploying sub-second routing and closed-loop attribution near Fort McHenry.
Engineered revenue infrastructure for scaling operators in District of Columbia. Deploying sub-second routing and closed-loop attribution near Lincoln Memorial.
Autonomous workflows, vector intelligence, and memory-safe systems built to scale business operations without fragility.
Bespoke web portals, client dashboards, and automated intake engines.
Problem Addressed
Your team spends hours on manual data entry or copy-paste tasks.
Refactor fragile prototypes into production-grade, typed architectures.
HNSW vector indexes and multi-tenant collection clustering at scale.
Problem Addressed
Search results feel random even though embeddings are being stored.
Dense + sparse hybrid search with cross-encoder reranking and payload filters.
Problem Addressed
The model answers confidently but pulls the wrong context.
Production multi-agent runtime environments with structured output guards.
Scalar quantization, on-disk payload storage, and SIMD hardware acceleration.
Problem Addressed
Search latency changes unpredictably.
Deterministic Architecture Discovery: Showing specialized subsystems suited to your active workflow context.
In motion
A six-second look at a growth system in motion.