Skip to content
Brad Stancel

About Brad Stancel

Founder and CEO of ProcessFast. Engineer by training, builder by habit, based in Columbia, South Carolina.
Brad Stancel
Role
Founder and CEO, ProcessFast
Based in
Columbia, South Carolina
Building Ops Insights since
2015
Education
B.S., Computer Information Systems, University of South Carolina. M.Eng., Computer Science.
Daily driver
Ubuntu, a terminal, and several AI models, cloud and local

I'm Brad Stancel. I founded ProcessFast, a software company that designs, builds, and runs its own products, and I've spent more than a decade building its first and largest one, Ops Insights: reporting and business intelligence for title agents and underwriters.

Before ProcessFast, I spent years as a technical consultant in enterprise software. That work taught me where I'm most useful: in the gap between “the software” and “the business,” where someone has to understand both well enough to make the right call. ProcessFast is its own customer, and we've never taken outside investors, so every build, buy, and hire decision has been mine to live with.

Why my work doesn't fit one job title

The problems I like don't stay in one discipline. In a single week I might trace a production failure from an application through Kubernetes to a storage volume in the wrong AWS availability zone, write the SQL behind a report a title agency runs every morning, and tune how an AI agent checks its own work.

Most specialists live in one layer of the stack. I'm interested in the interfaces between them, because that's where modern systems tend to break, and increasingly where AI agents need the most help.

How I use AI

I use several AI systems every day, cloud-hosted and running on my own hardware, and I treat choosing between them as an engineering decision. A frontier model might write a detailed specification while a local model on my DGX Spark cluster implements it. Anything sensitive, or anything that has to keep working offline, runs on hardware I own.

Outside the office

I'm a voracious, self-taught learner, and I mostly learn by taking on a real project. I've become handy with HVAC diagnosing my own systems, built a solar and battery setup for the house, run a small off-grid radio network, and I'm working toward machining replacement parts that nobody makes anymore. The lab page has the details.

I also handle the technology behind my wife Shirly's embroidery business, Clever Orchid, and I rebuilt the website for a neighbor's dental practice, Complete Dental Care. Small businesses get stranded by technology vendors as badly as enterprises do, usually with less recourse, so I enjoy that work.

What I believe about technology

Own what you run

The systems a business depends on should keep working if a vendor disappears, changes its terms, or stops supporting a product. Open formats, data you can export, and nothing that has to phone home to function.

Evidence over confidence

A confident explanation can still be wrong. Logs, measurements, database results, and what the browser actually shows are harder to argue with.

Understand the layer below

Abstractions are useful until they fail. When they do, knowing the next layer down is the difference between guessing and debugging.

Documentation is part of the system

I write down intent, decisions, and the steps the manufacturer left out. Now that AI agents read project documentation too, that habit matters more than ever.

AI is leverage, not a reason to stop understanding

AI writes code, reads logs, and operates tools for me every day. That makes understanding the system around it more important, not less.

In the press

Title-industry coverage of Ops Insights and ProcessFast.

Working with me

  • I'm direct and data-driven. Show me the log line, the query plan, or the voltage reading.
  • I prefer simple, reliable, replaceable solutions over clever ones with hidden dependencies.
  • I'll tell you when a vendor's product is likely to strand you, even if it's the popular choice.
  • You get the write-up. Whatever I learn on your systems is documented for you.

Open source

  • ReStructuredText Preview for JetBrains IDEs

    Free and open source (Apache 2.0). I document everything from business processes to how-to guides in reStructuredText and Sphinx, and JetBrains IDEs could only preview it through the Python plugin, which PhpStorm doesn't offer. So I built a standalone live preview and published it for everyone else who relies on the format.

    Why I built itJetBrains MarketplaceSource on GitHub

  • Ansible playbook scaffolding and roles

    My most-starred repository, plus dozens of roles for server provisioning, backups, monitoring, and web stacks.

    GitHub

  • Yii2 SuiteCRM API client

    A PHP client for SuiteCRM and SugarCRM's REST API, published on Packagist.

    Packagist

More on GitHub

Tell me what's slowing the business down.

Describe the problem in plain terms. I read every message myself and reply when there's something I can genuinely help with.

Start a conversation