Impact studiesACYCLIC / IMPACT STUDIES
Software in
the field.
Representative engagements across operations, finance, and applied AI. Client identities and outcomes are withheld in this draft.
Each study describes the situation, the constraint, and what we built.
INDEX / 08 ENGAGEMENTSANONYMIZED
01 / 08FIELD OPERATIONS
Regional wastewater operator
Situation
Route plans, dispatch decisions, service evidence, and billing were connected by manual handoffs.
Constraint
Field work had to remain usable for crews while producing dependable office records.
What we built
We built route planning, dispatch, service records, and billing in one operating flow.
02 / 08OPERATING LAYER
Field service business
Situation
Calendar commitments, estimates, jobs, and follow-up lived in separate tools.
Constraint
The office needed a reliable view of what had been promised and what still required action.
What we built
We built an operating layer connecting calendars, estimates, jobs, and office follow-up.
03 / 08FIELD OPERATIONS
Pest-control operator
Situation
A completed route did not automatically become a complete invoice trail.
Constraint
Route changes and service details had to survive the handoff to billing.
What we built
We built route-to-invoice software for pest-control operations.
04 / 08SHOP OPERATIONS
Automotive service shops
Situation
Repair work, labor, parts, and margin decisions needed a common record.
Constraint
Shop teams needed controls that matched the pace and detail of repair orders.
What we built
We built repair orders with labor, parts, and profitability controls.
05 / 08WORKFORCE OPERATIONS
Field team operator
Situation
Crew attendance and work records were collected before payroll preparation.
Constraint
The records had to be ready for review without replacing human approval.
What we built
We built crew check-in and payroll-readiness software for field teams.
06 / 08FINANCIAL OPERATIONS
Financial operations team
Situation
Payment events and the books needed a traceable connection.
Constraint
Exceptions and reconciliation had to be visible to the people responsible for the close.
What we built
We built payment, reconciliation, and financial operations software.
07 / 08DECISION SUPPORT
Operating leadership team
Situation
Acquisition, retention, and coverage data were spread across operating views.
Constraint
Leaders needed to see the same definitions across those decisions.
What we built
We built executive dashboards for acquisition, retention, and operational coverage.
08 / 08APPLIED AI
Professional chess coaching team
Situation
Analysis and coaching required time-consuming review of positions and decisions.
Constraint
Agent output needed to support a coach’s judgment rather than stand in for it.
What we built
We built AI agent-assisted analysis and coaching software for professional chess.
NEXT STEPHave an operating constraint like these?
Tell us the system, the constraint, and the deadline. We will tell you if we can take responsibility for the result.
Discuss an engagement ↗