Origin

Built by the team that runs Rental King.

My brother runs a 24/7 oilfield rental operation in the Permian Basin. When the phone rings at 2 a.m., there is no waiting until morning.

Before EquipFlow.

He ran on a combination of whiteboards, Excel files, and a legacy rental system that hadn’t been meaningfully updated in years. That setup worked until it didn’t.

In oilfield rental, “until it doesn’t” usually means 2 a.m. when a unit didn’t come back and nobody knows where the driver is. The whiteboard doesn’t update itself. The spreadsheet doesn’t know which dispatcher made the last call. The legacy software can tell you what left the yard two weeks ago, but it can’t tell you what your mechanic found on inspection this morning.

He’d tried the big names — Point-of-Rental, Wynne, others. Every one of them was built for a different kind of operation: companies with IT departments, multiple locations, and tolerance for six-month implementations. None of them fit the way a single yard with 24/7 oilfield contracts actually moves.

Rental King yard along West Interstate 20 in Odessa, Texas — manlifts, telehandlers, light towers, and compressors lined up under a Permian Basin sky.

Rental King, Odessa & Midland, TX — the yard EquipFlow was built for.

What we built.

Dispatch first.

Dispatch is where the day either works or it doesn’t. When a driver calls in sick or a unit doesn’t come back on time, that problem shows up in dispatch before it shows up anywhere else.

We spent time at the yard watching how jobs were assigned, how the whiteboard got updated, and how the dispatcher communicated with the counter when a customer called asking where their equipment was. We built the dispatch screen around that workflow.

Then billing.

An invoice that doesn’t match what the dispatcher recorded is how trust breaks between a yard and a customer.

Billing rules had to handle hourly, daily, weekly, monthly, standby rates, and MSA overrides — set once, applied everywhere, reconciled against the job record.

Then maintenance and inspections.

A unit that goes out with a deferred service item is a liability that shows up at the worst possible time. Each piece was shaped by what the yard actually does, not what a product manager thinks it should do.

Our accountability system.

Our first customer is our brother’s yard. If the software breaks, he calls. That’s not a marketing line — that’s our accountability system.

Rental King is our design partner in the literal sense: every feature we ship has been tested against the problems a real 24/7 oilfield operation faces. We know what it costs when a delivery fails at 2 a.m. We know what it takes to get a unit back on the road by 6 a.m. The brother who calls when it breaks keeps us honest.

What we will not build.

EquipFlow is the operations layer underneath your storefront — the screen your dispatcher, counter staff, and yard crew use to run the day. We do not build customer-facing rental sites, point-of-sale systems, or marketplaces.

If a full online booking flow is your biggest problem today, we are not the right call yet. That scope decision is deliberate: building a narrow thing well beats building a broad thing badly. The yards we work with already have a counter, a phone, and a website. They need the back end to work.

Who it fits.

Right now, EquipFlow fits single-location yards running roughly 50 to 400 units. We are Texas-first — not because we plan to stop at the state line, but because that’s where Rental King is, and that proximity keeps feedback fast.

We are not chasing every rental segment on earth — aerial, party, AV, consumer. Single-location heavy equipment yards in oilfield, construction, and general industrial rental are where we build, where we test, and where we earn the right to go further.

Book a demo →