Drawing the lot
Drawing the lot
It needs a current browser with 3D graphics turned on. Everything else is one tap away.
Who builds it
I was a trim carpenter before I sold roofs, and a sales rep and manager before I built software.
The job was drowning in paper. Nothing to organize it with, nothing to schedule with, no way to see two things at once. Ten-plus tools to get one job done, none of them talking to each other.
So I built one that did all of it — every lead, job, document, photo and dollar in one place. Not a sales tool with add-ons: one system that runs the enterprise. It ran a real company — crews, money and permissions in it, every day, with real work moving through it.
I came out of finish carpentry, where the part people see is the part you get judged on. That is why this is built the way it is: the screens your team stares at all day get the same attention as the plumbing behind them.
If there's a process I believe can be improved with technology, I'll build the thing that improves it.
I'm not an agency and I don't have a process deck. I had your problem. I know what it costs, because it cost me.
Most businesses this size don't have a software problem. They have ten small ones that nobody owns — a spreadsheet somebody maintains by hand, a folder of photos nobody can find, a schedule that lives in one person's head, numbers that have to be rebuilt every month before anyone can read them.
Each one is survivable on its own. Together they set a ceiling on how big the company can get, because every new job adds more of them. Getting off paper is not a software purchase. It is the thing that lets a company grow without adding a filing cabinet and somebody to mind it.
That's the work. One system that runs the operation, built around how the business actually runs rather than how software wishes it did.
No two of these come out the same, on purpose.
In person or on a video call. You talk about how the business runs today and where it hurts.
An ERP (one system that runs the enterprise end to end — leads, jobs, scheduling, documents, invoicing and the reporting on top). A CRM. Your website, Google and social. Connecting what you already have instead of replacing it. What fits, and what doesn't need touching.
What you want built, and the end goal it has to hit. A demo first, if seeing it helps. The scope goes in writing before anything starts.
A lot of it. How the work really moves, who touches what, where the paper and the spreadsheets live. This is where it gets shaped around you.
One piece at a time, in the order we agree on. You see it as it comes together.
It goes live and I stay on it — fixes, changes, and the next piece when you're ready for it. Your data is backed up on a schedule to more than one place, encrypted, and the restores are tested rather than assumed.
| Business | Blair Standard LLC, a Kansas limited liability company |
|---|---|
| Based | Wichita, Kansas. Works with businesses anywhere. |
| What I am | An independent consultant and software builder. Not a contractor, not an agency. |
| Background | Finish carpentry, running jobs and crews, then operations and sales, then building the systems that run them |
| The software | Registered with the United States Copyright Office — the application and the database design as one work |
| Clients | Not named publicly. Ever. Who you are is as private as what is inside your system. |
You'll get a reply within two business days, and most within one.