BENALI
Superintendent Operations Map

Make the superintendent role teachable.

A two-week proof of concept: map the traveling superintendent role in new construction from end to end, and turn what your best people already know into checklists and SOPs the whole field team can follow.

Prepared for
O'Hara's Son Roofing
From
Benali
Date
July 8, 2026
BENALI Superintendent Operations Map · Proof of Concept
The problem

The knowledge is there. The standard isn't.

OSR has grown fast, and the way work gets done in the field has outpaced the way it's documented. The SOPs exist. They just live where the field doesn't.

SOPs on a shelf
Guru holds years of SOP work, but 5% of users touch it daily and field superintendents don't go in at all. Printed binders fill the gap, with no way to know what's been read or whether it's current.
Training by memory
Onboarding is hasty and unstandardized. There's no playbook for what a new superintendent gets trained on, in what order. People discover a year in that they were never shown a required task.
A moving target
The company changes every couple of months. A dozen SOPs get revised by hand in a single month, and it's hard to know which version is current, or where it lives.
The proof of concept

One role, mapped end to end.

Step 01
Interview the experts

2 to 4 hours with your strongest field expertise, plus short follow-ups. We capture how the work actually happens, not the idealized version.

Step 02
Map the workflow

The full path a new-construction traveling superintendent takes through a project, phase by phase, in a structure built for exactly this.

Step 03
Go deep where it hurts

2 to 3 priority workflows mapped in detail, daily reporting is the leading candidate, each with a clear trigger and end state.

Step 04
Deliver the standard

Checklists of 10 items or fewer in plain English, and SOPs where the process is durable enough to deserve one, formatted to live where the role already works.

This phase is mapping and documentation only. Nothing connects to your systems, no API access is required, and your team keeps every judgment call. The map is also what makes any future automation safe to build.

Benali × O'Hara's Son Roofing01
BENALI Superintendent Operations Map · Proof of Concept
How we work

Map, connect, deploy. With your team.

01 · Map
Define the work

Interviews, existing SOPs, and the tools the role lives in become one clear operations map. This proposal is this step.

02 · Connect
Give AI the context

Once work is mapped, AI gets the approved context and tool access it needs to help, scoped the way you'd scope any user's login.

03 · Deploy
Put it into real jobs

Specific workflows get AI working inside them with clear ownership, like drafting a complete report from a voice note.

This proof of concept is the Map step for one role. Connect and Deploy happen only if the map earns it.

Investment

A contained first project.

Fixed price
$10,000

Fixed. No travel, no new software to buy, no system access required.

What's included
  • End-to-end operations map of the new-construction traveling superintendent role
  • Detailed maps of 2 to 3 priority workflows, daily reporting first
  • Checklists with clear triggers and end states, 10 items or fewer each
  • SOPs where the process is durable enough to deserve one
  • A working session with Amina, Matt, and Jessica to hand off the map and agree what comes next
Timeline 2 weeks

Two weeks from the first interview. We'll need 2 to 4 hours with Tony across a couple of sessions, the existing Guru SOPs for the role, and a walkthrough of how the role uses Job Tread. Jessica is welcome in every session.

Where this goes next. Your superintendents write the same daily report twice: once in Job Tread, again in the GC's platform. Once the role is mapped, that's the first deployment we'd propose: a short voice note in, a complete draft report in Job Tread plus the GC copy out, reviewed and sent by the superintendent. We'll scope and price that build after the map confirms the details.

Benali × O'Hara's Son Roofing02