siteOS
The story What it replaced Both sides The numbers
Admin
Alexander Grading · South Carolina

It just wasn't
working anymore.

I wasn't angry so much as fed up. A dozen logins, none of them talking, and half of how we ran the company living in somebody's head. Every month was a square peg in a round hole. So I picked the thing I hated most — onboarding — and built a portal for it. That portal turned into the software that runs the whole place.

One console in the office · fifty phones in the dirt
Built in-house. Not for sale.
In my own words
”
Cole Farlow, Alexander Grading

I couldn't believe nobody had made an app that did all of this in one place. So I started small. I picked something I didn't love — onboarding — and thought, I wonder if I can build a portal. The rest was history.

As the business grew, the processes got more complex. How we ran things needed to be more organized, more streamlined, and above all easy to use.

If we can make all of this simpler, I think we can win.

Everything below is evidence for that one line.

What it replaced

Every one of these used to be a mess.

Group texts. Spreadsheets nobody could find. Paper in a folder on somebody's desk. Three of these were never a system at all — just a process that lived in two people's memory. Now every one of them is one screen.

NowBefore
Schedule board
Group textsNo system
Equipment board
Two people's memory, and maybe a spreadsheet somewhereNo system
Pre-Construction pipeline
Random spreadsheets, texts, no process whatsoeverNo system
Time & Pay register
WorkMax — old, outdated, not user friendly
Onboarding portal
Paper, random folders on a computer or the drive, no process
For every person

From someone's first day to their last.

A person shows up as an applicant and leaves as a record of everything they did here. Hiring, onboarding, hours, time off, reviews and pay all sit on one record, so nobody has to remember which spreadsheet held the answer.

01
Applied
Application lands in the queue.
02
Day one
Paperwork done on their own phone, not a folder.
03
On the clock
Punches, schedule, daily tasks.
04
Time off
Requested and approved in the app.
05
Reviewed
60-day and annual, on the record.
06
Paid
Hours approved, stub delivered.
For every job

From an email to the last hour in the dirt.

A multi-million dollar project starts life as an invitation to bid sitting in an inbox. It ends as a closed job with every hour, photo and document still attached to it. Different people own different steps; the job carries its own history between them.

01
Invited
An email from a GC lands on the board.
02
Bid
Takeoff, estimate, proposal.
03
Won
Budget uploaded, contract signed.
04
Scheduled
Crews and machines placed on the day.
05
Logged
Hours, quantities, photos from the field.
06
Costed
Every hour lands against a code.
The bridge

The same second, from both sides.

An estimator at a desk and an operator in a cab need different tools, so they get different apps. They are still one company, because they are reading the same job at the same moment. Nothing is exported, and nothing waits for a sync window.

Schedule
The office places crews and machines on a day. The crew opens their phone and sees where to be, who is running it, and how to get there.
siteOS Admin siteOS Admin siteOS on iPhone siteOS on iPhone
Equipment
Every machine tracked from the yard to the job and back. Before this it was two people's memory. The operator sees what he has and where it goes next.
siteOS Admin siteOS Admin siteOS on iPhone siteOS on iPhone
Time & Pay
This is the biggest thing siteOS does. A man taps Clock in on his own phone, the office reviews the punch before it becomes money, and the same hour shows up on his stub. A punch made in a dead zone is written to the phone and drains when signal returns — 648 of 1,161 punches came straight off a phone, and none were lost.
Tap Clock in
siteOS Admin — Field time review siteOS Admin — Field time review siteOS on iPhone — Pay siteOS on iPhone — Pay
The seams

One hour, approved once, lands in five places.

Most construction software owns a department and hands the rest to spreadsheets. The seams between them are where the money leaks. An hour approved here isn't re-keyed into anything — it is the same record in payroll, in the job's cost, in the crew roll-up and on the man's phone.

The decision · Field Review
One tap
Bryce Reeves · Foreman
8.19 h
Sun 7/26 · Church Avenue Utilities · REG
Approve this hour
0 rooms updated
Tap approve and watch where that single hour goes.
The seam
5 rooms move the second a superintendent taps approve.
Nobody types an hour into a spreadsheet. That handoff is where the money used to leak.
Where it lands
No re-keying
Timesheets
Sun 7/26 approved · ready to export
8.00 h
Job costing
Church Avenue Utilities · labour to date
+8.00 h
Payroll close
This pay period · awaiting export
8.00 h
Crew status
Pipe crew · week roll-up
+8.00 h
The employee’s phone
Hours today · visible to him
8.00 h
Verified against production

Months of real payroll.

29
people paid through it
7,353
hours worked and recorded
1,161
punches, 648 straight off a phone
28
jobs charged through siteOS
First real punch from the iPhone app: 18 April 2026. Every figure above is checked against production, not a demo tenant.
Craft

Designed against a written law.

siteOS has an actual design statute. Surfaces, strokes, type and colour are specified, and every screen is audited against it. That's why a fifty-room application still reads as one thing.

Surfaces slope, they never step.
Adjacent surfaces differ by a murmur, two to four units, so depth is felt rather than seen.
A border must earn its existence.
Cards carry the only stroke, at well under a tenth of an ink. Everything else is separated by fill and radius alone.
Never say the same thing twice.
One mechanism per edge, one expression per fact. Colour is scarce and always semantic, so no tint is ever decorative.
Alexander Grading
”

Two apps.
One company.

The office bids the work. The field moves the dirt. siteOS is the bridge between them, so both sides are looking at the same job on the same second. It goes with a person from their first day to their last, and with a job from its first day to its last.

Open siteOS Admin siteOS for employees
siteOS
siteOS for employees siteOS Admin
Built for Alexander Grading · South Carolina