You build the network. Blue runs the field office. Blue is an AI field-coordination employee that lives on a box at your shop and works over plain text messages. It keeps the 811 book current, builds the daily production sheet, answers spec and safety questions to the page, and remembers every date that bites — so your superintendents run crews instead of spreadsheets. No app. No login. No network integration.
Precision started in 2016 with a truck and a set of tools and is now the 2026 Telecom Contractor of the Year — two offices, Bargersville and Terre Haute; turnkey HDD, aerial, blowing, splicing and activation; REMC fiber builds and carrier work across the Midwest; 24/7/365 call-outs; a DOT fleet of ~30 power units; four OSP superintendents; a CFO, an HR/Safety director, a fleet manager. And a sister company on the way — Precision Utility Services — for water, sewer, gas, power and private locating.
A turnkey fiber shop generates coordination faster than any office can absorb it. Indiana 811 tickets live 20 days, need two full working days' notice, and every crew has a stack of them with staggered update-by dates. The daily production report your REMC and carrier clients expect gets built the same way every morning: text every foreman, wait, nudge, retype. A drill operator with a depth or clearance question calls the super, who calls the office, who finds the standard. Meanwhile a three-person crew is standing.
A locate status, a spec, a go/no-go — every round trip through the super idles a crew you're already paying. That's the line closest to real money, and it's the one we measure.
Telecom work causes roughly 60% of all HDD utility strikes nationally, and an expired or never-updated ticket is the classic root cause. Your clients and your insurer know that number too.
Where is everyone, what are they doing, which WR, which client, radio number, underground or aerial. The superintendent's first hour goes to a spreadsheet instead of the work.
Text a work order and prints; Blue proposes the tickets, draws each dig corridor on a map, and publishes a review page the super approves from the truck. Filing is human-approved, every time. Then Blue runs the clock: a Monday digest per ticket owner — reply ALL and the whole book refreshes. Status by ticket number, positive-response read-back, and a hard warning before a crew breaks ground on a dead ticket.
7:15 ask to every foreman, nudge only the ones who haven't answered, compile one sheet (xlsx or PDF) with WR, client, location, crew, UG/OH — released by a named superintendent and emailed to the client's distribution list. "Same as yesterday" is a valid answer.
Load your safety manual, each client's construction standards, splice specs and equipment manuals. Any roster member texts a question and gets the answer with the source page attached — document, section, page. If Blue can't cite it, it says so and routes to the super.
Start-minus-N-day reminders for ROW and county permits, railroad crossings, inspection windows; DOT annual inspections and driver-file dates; service intervals on the drills and plows keyed to hours or dates. The per-unit maintenance scheduler is next on our build list — the reminders themselves run today.
A storm call at 2am gets logged the moment it lands: who called, where, what's down, who's rolling, when they arrived. The super gets the alert; the office gets the record in the morning; the client gets a response time you can prove.
Crews move between superintendents; Blue's roster moves with them by text, no admin screen. Each person only gets what their role should see — a foreman never sees pricing; a client's prints only reach the unit working them. English or Spanish, per person.
Every scenario below is a workflow that exists today — running daily at our utility-contractor customer — reframed for fiber construction. Nothing here is a mockup of what we hope to build.
Blue texts every foreman for today's location, WR, client and crew. By 7:50 it has compiled one sheet, named who hasn't answered, and sent it to the superintendent to release.
Every WR whose tickets hit their update-by date this week, grouped by whoever filed them. One text, one reply. Blue refreshes the book and records every new ticket number before it moves to the next.
A drill operator asks by text. Blue answers from the client's construction standard — with the page attached — instead of a phone tree.
Blue reads the ticket's positive response and says exactly which utilities have marked and which haven't. Date-valid and actually-marked are different questions; Blue keeps them separate.
Text Blue the work-order packet. It reads the prints, proposes the tickets, derives each dig corridor, draws it on a map, and sends the super a review page. He approves from the truck; filing is human-approved per ticket.
County ROW permit for the 135 crossing: 4 weeks out. Two drills due for service by hours. Unit 14's DOT annual is next month. Blue reminds the right person, once, at the right time.
Friday's cut asks who's working Saturday and Sunday, compiles the weekend sheet, and the superintendent releases it — so dispatch and the client know before anyone leaves.
Joink's NOC texts a fiber cut. Blue logs it, alerts the on-call super, and keeps the timeline — acknowledged, dispatched, on site, restored — so Monday's report is a record, not a memory.
This is the whole interface. No dashboard, no portal — the same thread a foreman uses to text his super.
DEMO CONTENT IS ILLUSTRATIVE · A REAL DEPLOYMENT ANSWERS FROM PRECISION'S ACTUAL TICKETS, STANDARDS & ROSTER
Every roster member carries a permission set. Blue answers what that person is allowed to know and does what they're allowed to ask for — and nothing customer-facing or money-touching happens without a named approver. Client prints are scoped to the unit working them and audited on every send.
| Role | Blue will… | Blue won't… |
|---|---|---|
| Superintendent | Release the daily sheet · approve 811 proposals · answer the refresh digest · get call-out alerts · change the roster by text | Touch the books · file a ticket without his approve |
| Foreman / operator | Report for the sheet · ask spec & safety questions (cited) · check a ticket's status · log a locate ticket he filed himself | See pricing, finance, or another unit's prints |
| HR / Safety | Load and update safety manuals · audit any answer against the source · get DOT and driver-file reminders | Make a safety decision — Blue cites the standard; the qualified person decides |
| Fleet | Get service and inspection reminders keyed to units, hours and dates | Order parts or schedule vendors on its own |
| Office / CFO | Get permit reminders · receive clean job-done and receipt signals if invited | Enter, send, or pay anything in accounting |
Blue runs on a Mac mini we install at the Bargersville shop. Your roster, your 811 ledger, your clients' standards and prints stay on hardware you can point at. We maintain it remotely over a private tunnel; encrypted off-site backup covers theft, fire, or a dead drive.
One superintendent and his crews. Two weeks to baseline how things actually run today, ten weeks live and instrumented, then a scorecard reported as measured — including anything that underperforms.
Documents loaded, unit configured, foremen onboarded by text. We measure today's sheet build time, lookup frequency, and locate round-trips before Blue changes anything.
Every question, answer, citation, sheet and ticket is logged with a timestamp. No self-reported numbers.
Hours returned, tickets that lapsed with a crew still on the job, sheet build time, citation rate, adoption. Delivered as-is. If the numbers aren't there, we'll say so and pull the box.
| Metric | Target | Why it matters |
|---|---|---|
| Tickets lapsed with a crew still on the WR | 0 | The strike-risk number your clients care about |
| 811 round-trips through the super | −60% | The most visible daily friction |
| Daily sheet build time | 45 min → < 10 min | Measurable every working day |
| Spec/safety answers cited to the page | 100% — or Blue declines | Your safety director can audit any answer in seconds |
| Foreman adoption | ≥ 75% texting Blue weekly | An unused tool returns nothing |
For scale: a three-person crew standing 20 minutes twice a day waiting on a locate answer is about $2,000 a month at a $100/hr burdened crew rate — before counting a single lapsed ticket, a missed permit window, or the superintendent's first hour back. We'll put your actual rates in the model, not ours.
It's early. Forge is a young Bargersville company with two customers live — a concrete contractor and a utility-line contractor's Indianapolis unit. You'd be the third, and the first fiber shop. You get founder-level attention on your setup, and you'll occasionally see a rough edge before we sand it.
The 811 filing itself stays human-approved. Blue proposes, draws, publishes the review page, and runs the refresh clock. A person hits approve on every filing. We think that's the right posture for a long time, and it's how our current customer runs it.
Blue doesn't make safety decisions. It surfaces the cited standard from your own manual or the client's, and routes to the super when it can't cite one. The qualified worker decides, every time.
It won't do your books, your hours, or your bids. Deliberately. It runs the field-coordination layer around the work — and hands the office clean inputs if you ever want them.
We're a family company a few miles down the road, built for operators who came up through the work. The three phones above aren't a storyboard — that's the product doing the job the way it does it every day. Starting is the same motion: a text. Say the word and inside two weeks Blue is on a box at the shop, your standards loaded, one unit's crews texting it — with 90 days to prove it's the best field hire you never had to make.