About Blue Forge
Built by one person,on purpose
Blue Forge is a deliberate choice, not a lack of scale. Here's who's actually doing the work.
Hi, I'm Dillon
I'm the software developer behind Blue Forge. I build the systems, write the code, talk to the clients, and answer the emails.
Most custom software for small businesses gets built badly. Either it's built cheap by someone who disappears after launch, or it's built expensive by an agency that treats a small business like a junior account. Both leave the client worse off than when they started.
I built Blue Forge to do it differently. Direct work, honest scope, software you actually own when it's done.
Background
The depth to build it right
I grew up in Oklahoma and earned a Bachelor's and Master's in Computer Science from the University of Tulsa, along with SANS certifications in incident handling, penetration testing, and machine learning (GCIH, GPEN, GMLE). Over the past several years, I've worked across web development, database administration, cybersecurity, and full-stack engineering, building business-critical systems and production software for real teams that had to use them every day.
That range matters. Most contracting problems don't fit in a single category. A “website project” turns into a database problem. An “AI tool” turns into an integration problem. Having depth across the stack means solving the actual problem, not the one that fits a specialty.
The Name
Why Blue Forge?
The winter of 1777 at Valley Forge came closer to ending the American Revolution than any battle did. A collapsed supply system, shelter the men had to build themselves out of the woods, and an army that had every reason to quit. It's one of the lowest points in the country's founding, and also one of the most important. What came out of that winter was stronger than what went in.
That's the moment captured here: Washington on his knees in the snow beside his horse, Blueskin, praying. He was the commanding general of the entire Continental Army, the one man everyone looked to for certainty, and here he is on his knees with his hat on the ground and his eyes turned up, admitting he didn't have this handled on his own. That's not weakness. That's the rarest kind of strength a leader can show, and it's the whole reason the story stuck around for 250 years.
Humility like that is hard to find now. Most leadership today is built on the opposite instinct: project total confidence, never admit uncertainty, never let anyone see you on your knees. What Washington actually did that winter is on the record. He wrote to Congress in plain language that his army would starve, dissolve, or disperse without help, at the exact moment a commander is most tempted to manage the story instead. Two thousand of his men died at Valley Forge, most of them of disease, and the army that marched out in June was better drilled and better organized than the one that marched in. Humility wasn't the thing standing between him and success. It was the thing that got him there.
That's where the name Blue Forge comes from. Blueskin, the horse. Valley Forge, the place. Put together, they point at something I believe about building anything worth building: the pressure isn't the enemy, and neither is admitting you don't have all the answers. The hardest stretches are usually the ones doing the actual forging, and the leaders who make it through are the ones humble enough to stay honest inside them.
I named the company after that because it's the standard I hold my own work to. Show up, do the work with integrity even when it's hard, stay honest about what I don't know, and trust that consistency in the difficult seasons is what produces something durable.
How I Work
Fewer layers, better work
Every project starts with a conversation. Not a sales call, not a discovery phase that costs money. A real conversation about what's broken, what you've tried, and what a good outcome actually looks like.
From there, I scope the work honestly, commit to a timeline I can keep, and build. You talk to me, not a project manager. You see the work in progress, not a six-month reveal. When it's done, you own the code, the accounts, and the documentation to run it.
I take on the work I can do well. If a project needs something outside my depth, I say so. The point isn't to maximize client count. It's to do right by the clients I take on.
The Work
What a good project looks like
Blue Forge works best when the client has a real problem they want solved well. Maybe the current system is a patchwork of tools and spreadsheets that should have been a real application two years ago. Maybe there's a manual process eating hours every week. Maybe there's an idea for a product that needs to actually get built.
If that sounds like your situation, we should talk.