OperatorIQ
Menu

Built with your crew, not handed to you.

Custom Builds.

Your own tools, built around how your company already runs. Every tool I build has one first job: give your people time back in their week. If it isn’t doing that, it’s failing, and I want to know.

Design-build, not plan-and-spec.

Nothing gets drawn up somewhere far off and handed over. I build a piece, your people use it, they tell me where to adjust it, and I improve it. The tool gets its shape from the people who have to live with it.

We meet about once a week. We look at what got built, what your people tried, what needs adjusting, and what you want next. The rest of the week, you’re running your business.

Between meetings, you tell me from inside the tool. The tools I build for you carry a place right there to send a comment, a question, an idea or a bug. It gets filed, it gets read, and it gets answered. You don’t have to save it up and hope you remember it at the meeting.

No two jobs run the same.

Your company isn’t anyone else’s. Some work is one tool, built and finished. Some runs for seasons and keeps going deeper. How far it goes and how fast depends on what the work shows us, and on you.

What a custom build can look like. Drawn from builds we’ve made; the names and times are examples.

bilingual voice routing

Said in Spanish at the stop. Read in English at the office.

Field report · 7:42 AM

Heard · ES
“Faltan dos yardas de mulch en la calle Oak, cama del frente.”
Filed · EN
2 cu yd mulch short · Oak St, front bed
Routed
Materials list · crew lead

Nobody retypes it, and nothing gets lost between the truck and the office.

information that comes to you

The morning brief shows up. You don’t go looking for it.

Today · 6:00 AM

Crews
Crew 2 is one person short
Weather
Rain Thursday: two installs to move
Money
Two invoices past 30 days
Else
Nothing else needs you today

Built from what your people already entered, sorted by what needs you first.

automations on a cadence

The week runs on a schedule, so you stop carrying it.

Every week

Mon 6:00
Schedule to every crew lead
Wed 12:00
Materials checked against the week’s jobs
Fri 15:00
Unpaid invoices, listed
1st
Equipment service due

The things you’d otherwise have to remember, on a clock you set.

the schedule

Rain moves the day. The day moves with it.

Tuesday · rain after 10

Moved
Oak St bed install → Thursday, first stop
Pulled up
Maple Ave cleanup → Crew 2, before the rain
Told
Crew leads · in Spanish and English
Waiting
3 jobs on the shared list
Your call
Crew 3’s truck is in the shop · who covers Pine Ct?

Stops go to the crews, the day gets put in order, and rain or a breakdown gets worked from one shared list of waiting jobs.

start with your own week

  1. What gets typed twice?
  2. What do you check first thing every morning?
  3. What do you carry in your head because nothing else will?
  4. What would you hand off tomorrow if you trusted it to get done right?

Bring the answers. That’s where a build starts.

What I look for.

A team that reads how work really moves through your company, from the first call to the last invoice, and names where it sticks. It reads the work, never the books, and nothing of yours is read until we’ve agreed in writing who holds it. These are the snags it listens for.

  1. “It lives in one person’s head.”
  2. “Nobody owns it.”
  3. “Nobody’s counting.”
  4. “It was never written down.”
  5. “Everything rides on one person or one tool.”
  6. “Always putting out fires.”
  7. “Five places to check, and none of them right.”
  8. “Everything waits on one signature.”
  9. “How it’s supposed to work isn’t how it works.”
  10. “The office finds out last.”
  11. “Everything’s urgent.”
  12. “Somebody types it in twice.”

Why I build.

Custom software used to belong to companies big enough to hire a tech firm. Everyone else bought what was on the shelf and made their people fit it. That’s changed. Tools built around how your company actually runs are within reach now, for a business your size.

what software used to ask of you

Your people bent to the tool.

It showed up finished. Then came the training videos, the quizzes, the lectures, the seminars to sign up for, and the onboarding consultant sent in to get it back on track.

what I build instead

The tool bends to your people.

Your team sits in the seat of influence. They use it, tell me where to adjust it, and steer it toward the value they helped find. It works for them because they shaped it.

when something needs adjusting

Discuss. Design. Deploy. Test.

I talk it through with the person who raised it, design the change, put it in, and test it with them. The person who spoke up is the one who sees it land.

Start from one that works.

You don’t have to start from a blank page. BidScan, SpecScout and Pace each run as they are, and each can be built into your own version, shaped around how you bid, the markets you watch, the way your crews run. I design what it puts out with you, so it lines up with your strategy and the things you’re already tracking.

Reads for what your estimators always check.

BidScan, your way

It reads the whole bid package and hands back the read in the shape your team prices from. Every answer comes with the page it came from, and what it couldn’t read, it tells you.

See BidScan Custom →
Answer
Liquidated damages apply after the substantial completion date.
Source
Addendum 3 · p. 12 · §2.1
Couldn’t read
Geotech report: a scanned image, flagged for you

An example of the kind of answer BidScan gives. The document names are made up.

Follows the specs and markets you care about.

SpecScout, your way

It watches the specs, products and markets that matter to how you sell, and flags where you stand, cited to the section.

specscout.ai →

Your schedule, your crews, your paperwork.

Pace, your way

The day, the crews and the office in one place, in the words your people already use, in Spanish or English.

See Pace →

BidScan and Pace already run in versions built for individual companies.

How every build is made.

Yes, it’s AI. Here’s how it’s kept honest.

  1. 01
    Its own space.Built apart from every other customer, and moved into your accounts when you say so.
  2. 02
    The AI reads. Plain code keeps the record.The math, the totals and the record are ordinary code you can check.
  3. 03
    It shows its sources.It lays out the evidence, with where it came from. The call is yours.
  4. 04
    Some doors were never built.What it shouldn’t do, it can’t do, because that part doesn’t exist.
you
The judgmentAnything that commits money, a customer or a crew waits for you.

What time back makes room for.

I start with your week. Where do the hours go? The office on Sunday night. The bid due Friday. The same numbers typed into three places. We pick one and build for it first.

Once time comes back, the next thing has room. A workflow gets cleaned up. Something done by hand gets done for you. Later, maybe, a build that helps you take on more work and keep more of what you earn.

What I learn gets written down. Say I build a tool for the office, and the crew leads start using it from the truck. I follow them, and the next build starts from there.

Something you mention in passing in week two might be what I build next spring. I keep it.

Who brings what

What I bring.

  • I’ll tell you what I don’t know yet.
  • I’ll build it, not just talk about it.
  • Every note you send gets read and answered, even when the answer is no.
  • I’ll say so when something isn’t working, before you have to.
  • If something off the shelf would serve you better, I’ll tell you.

What you bring.

  • How the work really gets done, not how it’s written down.
  • Your people using it, and telling me where to adjust it.
  • Saying so when the crew stops using it, not only when it breaks.
  • Saying so when it isn’t saving time.
  • Your judgment. It’s your business.

What you own

I don’t rent it back to you or sit between you and your customer list.

  • Your data, your seat. Built in its own space, apart from every other customer, and moved into your accounts when you say so. No hostage data, no vendor dependency created on purpose.
  • Transferable to your team. What gets built is documented and walked through. Your team learns what was built, why, and how to extend it.
  • Month-to-month. No annual contracts. If it stops earning its keep, you stop.

Who this is for

Contractors, tradespeople and the owners who run the work, from one truck to full multi-crew operations, who want tools built around how they already work, and the know-how to keep them running.

Start with your week.

Where does your week go? Tell me the one step nobody on your crew would miss. Site visit first. Quote follows.