Three decades of building systems
where failure wasn't an option.
That experience shapes how I think about every project, including yours.
The Story
From high-stakes systems to high-performance websites
Before I ever touched a website, I spent close to thirty years in environments where software failures had real consequences, and where the systems I worked on had one thing in common: money.
At the Department of Defense, I helped build pay and benefits disbursement and accounting systems. At the State of Oregon, I built budget planning and tracking tools for state government. Inside a regional bank, I supported the infrastructure and check imaging hardware that kept operations running across Oregon and Washington. And as QA manager at Parametric Portfolio Associates, I was responsible for the platforms handling over $600 billion in client assets.
That's not a resume that wandered into financial services. That's a career built inside financial systems, at every level, from military payroll to institutional investment management.
That kind of work rewires how you think. You stop guessing. You measure. You test for what breaks before it breaks, and you build with a discipline that sticks with you long after you move on.
Your website gets all of that. Not because a marketing site carries the same stakes as defense systems or financial infrastructure, but because cutting corners was never something I learned how to do.
Dustin Cole
Founder, Badger Mountain Digital
Walla Walla, WA
What Drives the Work
Principles, not buzzwords
Measure everything
You'll see actual numbers. Before-and-after scores, load times, real data. Not vague promises about "improved performance."
Test ruthlessly
Nothing ships to your site untested. Speed, accessibility, functionality - all verified before every deployment. Every single one.
Tell the truth
Sometimes your site needs a rebuild. Sometimes just a tuneup. Either way, you get a straight answer, not an upsell.
Plan for failure
Traffic spikes, browser quirks, third-party scripts that misbehave. I think about what can go wrong with your site so you don't have to.
Why It Matters
What this means for your project
Most developers learn on the job. Your job. They ship, cross their fingers, and fix what breaks. That's the norm in this industry. It's not how I work.
You won't deal with weeks of radio silence. Your site won't look polished on the surface and take eight seconds to load underneath. And there won't be a launch day followed by a punch list of things “we'll fix later.”
What you get instead is a website that's fast, accessible, and built to pull its weight. With the data to prove it.
Let's talk about your project.
No pressure. No jargon. Just a straight conversation about where your site stands and what's possible.
Schedule Your Consultation