Top Work About Our story Contact

OKFINE

We build software for people who run things


AuditFlow

Irrigation audit platform

app.auditflowtech.com
Riverside Parks Department
IA Standard Municipal In Progress
+ Generate Report
Overall DU
74%
Zones
3
Findings
5
Est. Savings
$2.4k/yr
Zone 1 - Front Lawn Rotors
Fair
DU: 72% PR: 1.24 in/hr PSI: 52
Zone 2 - Parking Median Drip
Good
DU: 85% PR: 0.92 in/hr PSI: 48
Zone 3 - Athletic Field East
Poor
DU: 67% PR: 1.41 in/hr PSI: 55
Field to report in under 45 minutes
IA Standard, CLCA, and System Health audits
PDF reports that write themselves
Client portal for digital sign-off
Teams, roles, tenant isolation
Water meter tracking and budgets
Irrigation auditors were doing math by hand, building reports in Word, and emailing PDFs at midnight. We thought that was fixable.

AuditFlow handles five audit types: System Health, IA Standard, CLCA, Golf Course, and Metered Flow. Each has its own data model, scoring logic, and compliance output. You walk the property, enter the data, and the system does the rest. Report is done before you leave the site.

Built for the auditors doing 20 to 50 audits a year, not the ones doing two. Deployed in California first, where CLCA compliance is not optional. Try AuditFlow

Audit Types
System Health
Walk-through inspection. Broken heads, leaks, pressure issues.
IA Standard
Catch-can testing. DU calculation. Zone-by-zone analysis.
CLCA
MAWA and ETWU calculations. California compliance built in.
Metered Flow
Water budgets from meter data. Multiple watering scenarios.
Four audit types, one platform
Before & Now
BEFORE
Spreadsheet with 47 tabs
NOW
One screen per zone
BEFORE
Manual DU calculation
NOW
Calculated as you type
BEFORE
Copy-paste into Word
NOW
PDF generated in seconds
BEFORE
No water savings data
NOW
Gallons + dollars, auto-calculated
What changes for auditors

PestMetrics

Daily KPI dashboard for pest control

PestMetrics Daily KPI Austin HQ
LIVE
Revenue
$7,225
▲ +12%
Hours
32.6
RPH
$222
▲ +$8
Stops
45
▲ +3
Technician Stops Hours Revenue RPH
Marcus Johnson 12 8.5 $1,840 $216
Elena Reyes 10 7.3 $1,595 $218
Chris Miller 14 9 $2,310 $257
Jay Patel 9 7.8 $1,480 $190
One number that matters: Revenue Per Hour
Nightly sync from FieldRoutes, ServiceTitan, payroll
Technician scorecards with performance tiers
Alerts when something looks off
7, 30, 90-day rolling trend lines
Daily email digests so you never have to log in
A pest control operator told us: "I have 14 technicians and I don't know which ones are making me money." He was cross-referencing FieldRoutes with Everee payroll in a Google Sheet every morning. We built PestMetrics so he could stop.

It connects to FieldRoutes, ServiceTitan, PestPac, Jobber, Everee, Gusto, ADP, and QuickBooks. Data syncs every night. By morning you know who is performing, who is struggling, and where the money is going.

Built for the operator who runs multiple branches and is tired of guessing. If RPH drops or cancellations spike, you hear about it before it compounds.

7-Day Trends
RPH 7-DAY +$6
$218
STOPS 7-DAY +2.1
42.3
REVENUE 7-DAY +8%
$6.8k
CANCEL RATE -0.3%
2.1%
Rolling trend lines and forecasting
Live Alerts
RPH ALERT
Jay Patel RPH dropped to $165, 22% below 30-day average
2 min ago
CANCEL SPIKE
Austin HQ cancellations up 40% this week vs. last
1 hr ago
GOAL HIT
Elena Reyes hit $220 RPH target, 3rd consecutive week
3 hrs ago
SYNC
Nightly sync complete. 4 branches, 127 stops, 0 errors
6 hrs ago
Threshold alerts and anomaly detection

Agent APIs

Your business logic, callable by any LLM

Terminal: POST /v1/tools/schedule-audit
$ curl -X POST https://api.okfine.dev/v1/tools/schedule-audit \
  -H "Authorization: Bearer sk-okf_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "property_id": "prop_8x2k",
    "type": "system_health",
    "assign_to": "john@riverparks.gov",
    "notes": "Front lawn rotors underperforming, schedule follow-up"
  }'
// 200 OK, 142ms
{
  "status": "scheduled",
  "audit_id": "aud_m4f9",
  "assigned": "John P.",
  "property": "Riverside Parks Department",
  "type": "system_health",
  "starts": "2026-04-14T09:00:00Z",
  "tools_available": [
    "schedule-audit", "get-zone-data", "generate-report",
    "create-proposal", "lookup-property", "get-rph"
  ]
}
Your business logic, callable by any LLM
REST endpoints with auth, validation, rate limiting
OpenAPI specs that drop into any agent framework
Structured JSON, not chat completions
Audit trail for every action the agent takes
Your data stays in your infrastructure
Every platform we build ships with an API. Some teams want to go further. They want agents that can schedule audits, pull technician data, and generate reports without a human clicking buttons. So we build that too.

Not a chatbot bolted onto your dashboard. Not a prompt wrapper. These are real API endpoints with authentication, input validation, and audit logging. The agent calls a tool, the tool does the work, and you get a record of exactly what happened.

If a person does the same workflow the same way every time, an agent should be able to do it too. We make that possible.

# OpenAPI tool definition. Drop into any agent.
name: schedule-audit
description: Schedule a new irrigation audit
parameters:
  property_id: string # required
  type: enum # system_health | ia_standard | clca
  assign_to: string # email of auditor
  notes: string # optional context
Plugs into Claude, GPT, or any agent framework
# Audit log. Every agent action is recorded.
2026-04-12 18:04:32 agent schedule-audit
  caller: agent_claude_7xk
  result: aud_m4f9 created 142ms
2026-04-12 18:04:33 agent get-zone-data
  caller: agent_claude_7xk
  result: 3 zones returned 89ms
2026-04-12 18:04:35 agent generate-report
  caller: agent_claude_7xk
  result: report_pdf_9a2.pdf 2.1s
Full audit trail. Who called what, when.

OKFINE

Est. 2021, San Antonio TX. We pick an industry, learn how people actually work, and build the tool that should already exist.

How we work

One industry at a time Learn the workflow first
Then write the code
  • Talk to the people doing the work
  • Build for the real workflow, not the ideal one
  • Ship fast, iterate with real users
  • Every platform gets an API
  • If it can be automated, it should be

The short version

We started in 2021 building internal tools for a local irrigation company. Auditors were doing math by hand, pasting data into Word docs, and emailing PDFs. That felt fixable. So we fixed it.

Then a pest control operator asked if we could do the same thing for their KPIs. Same problem, different industry. People running real operations on spreadsheets and gut feel. We keep finding these.

Read the full story