For commercial plumbing contractors

We find the office work your team repeats, like retyping backflow results into the utility's report, and help your team automate it. Our AI agent only reads.

A free 30-minute call. No data or access needed.

Our agent is ready for testing.

Example map of a fictional plumbing contractor’s appsA line drawing of six of a fictional plumbing contractor’s apps: Outlook, BuildOps, Teams, Excel, BSI Online and QuickBooks. A line shows test results moving from Outlook through Excel into BSI Online. Three markers show repetitive work the agent would find: Test results typed in again, Failed tests quoted by hand and Test invoices billed one by one. Fictional example.Example map of a fictional plumbing contractor’s appsA line drawing of six of a fictional plumbing contractor’s apps: Outlook, BuildOps, Teams, Excel, BSI Online and QuickBooks. A line shows test results moving from Outlook through Excel into BSI Online. Three markers show repetitive work the agent would find: Test results typed in again, Failed tests quoted by hand and Test invoices billed one by one. Fictional example.

A fictional plumbing contractor’s software, as we would map it with your team.

  • Test results
  • Repetitive work

Where we start

Your software already knows how your shop works.

Every test report, repair quote and filing leaves a trail in your tools. We start there, with the people who do the work.

Examples of the software commercial plumbing contractors run, not a list of integrations: ServiceTitan, BuildOps, ServiceTrade, Simpro, Jonas Construction Software, QuickBooks, Sage Intacct, Procore, Outlook, Gmail, Excel, Google Sheets, Microsoft Teams, OneDrive, SharePoint, Google Drive, BSI Online, SwiftComply, Syncta, ServiceChannel, Corrigo, Bluebeam, McCormick, GPS Insight, and in-house tools.

Follow a backflow test

Tested on site. Typed in again for the utility.

With the automation on, each test is mapped from your field form to the water utility's report fields, and a failed assembly becomes a repair quote and a retest inside the filing window. Your certified tester files.

  1. Today

    One test, typed into four places.

  2. Map

    Every reading, mapped once.

  3. Draft

    Assembly B failed. The clock is running.

  4. Review

    Your tester files, under their own login.

Illustrative workflow. Buildings, assemblies and numbers are fictional.

The automation prepares.
Your team decides.

Kestrel is meant for the paperwork around a test, never the test itself.

The automation

  • Reads field test forms and readings
  • Maps them to the utility’s report fields
  • Flags serial, confirmation number and calibration mismatches
  • Drafts repair quotes and retest tasks

Your team

  • Testing and certifying assemblies
  • Filing under the tester’s own login
  • Repair scope and price
  • Anything sent to the building owner

A good fit if

  • You test commercial backflow assemblies for building owners every year
  • Results are typed again from field forms into utility portals
  • Failed assemblies need a quote, a repair and a retest before a deadline

Probably not yet if

  • You test a handful of assemblies a year
  • Your field app already files with every utility you work with
  • Most of your work is residential
Bom PattanapaisalAndre Romero-Carey

You work with Bom and Andre.

They run your call, the walkthrough and the build.

Practical questions.

Start with
your workflow.

How do your backflow tests reach the utility today?

  1. You tell us where the repetitive work is.
  2. We say honestly whether we can help.
  3. If we can, we plan a free walkthrough at your site.

Next open times

Send us a note.

The founders read every note and reply by email.

Example viewed: Backflow test filing and retests.
You can tell us about a different workflow in your note.

Which tools does your team use? (optional)

We’ll use these details to reply to your note.
Read our privacy notice.