Skip to content
Brad Stancel

Founder and CEO of ProcessFast, in Columbia, South Carolina

Brad Stancel

I build the AI, automation, and data systems that give business owners their time back, and I make sure they actually work.

A title agency switches production software and still needs Monday's reports. I work out which reports survive the move, which get rebuilt, and what the migration really costs.

Ops Insights, since 2015See the details

Problems rarely fail where the error shows up. Pick a layer to see work I've done there.

A record you can check

More than a decade of building and running software businesses, with the press coverage and the code to back it up.

  1. 2015

    Started building Ops Insights, reporting and business intelligence for title agents and underwriters. It has run in production ever since. Details about 2015

  2. 2017

    Announced Ops Insights integrations with Adeptive's ResWare and with RamQuest, covered by ALTA and The Title Report. Details about 2017

  3. 2020

    Released a RamQuest-specific version of Ops Insights, covered by ALTA. Details about 2020

  4. 2023

    Rebuilt Ops Insights' infrastructure on Kubernetes in AWS, defined entirely as code. Details about 2023

  5. 2025

    Launched the Clever Orchid Embroidery site on a shared platform for small-business websites. Details about 2025

  6. 2026

    Rebuilt Complete Dental Care's site, shipped Client Hub and a booking package, published a free, open-source reStructuredText preview plugin for JetBrains IDEs, and brought a two-node NVIDIA DGX Spark cluster online for local AI. Details about 2026

How I work

A few rules I learned the expensive way.

“Working” is a claim that needs evidence.

A green checkmark, an exit code of zero, or an AI agent saying it's done is a clue, not proof. I check the result the way the customer will see it.

Fix it at the layer where it breaks.

The error usually shows up somewhere other than where it starts. Patching the symptom buys a week; finding the cause buys years.

Keep it simple enough to recover.

If a system can't be rebuilt from its code and documentation, it isn't finished. I leave the write-up behind.

Own what you run.

Your domain, your data, and your accounts stay yours. I don't build dependencies on me or on a vendor that can change its terms.

Brad Stancel smiling beside a bronze Yoda fountain
At the Yoda fountain on the Lucasfilm campus in San Francisco.

Always taking something apart

I learn by building. I taught myself HVAC well enough to diagnose the systems in my own house, then designed a solar and battery setup for it and measured the circuits until the numbers made sense. That's how I found heat strips running when they shouldn't have been, at hundreds of dollars a month.

The same habit runs my work. New hardware, new AI models, a customer's undocumented database: I want to know how it really behaves, then write down what I found so the next person doesn't have to rediscover it.

More about me

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