I build software, design processes, and make art.
A showcase of what I've shipped, what I'm working on, and how I get things done.
Hey, I'm Ben.
I'm Ben Bishop. I'm a father of three, a husband, a combat veteran, and a builder.
I build software, make art, and design systems that help people move faster and waste less time. I care deeply about integrity — it's the core of who I am, and everything else flows from it.
None of this would be possible without my wife Gianna. She's my partner in everything. Her support is what allows me to take risks, build things, and keep pushing forward. I don't do any of this alone.
Service
I served as Infantry in the US Army and did one tour in Iraq. That experience shaped how I handle problems. I stay calm when things get messy, I move quickly when decisions matter, and I take ownership when something breaks. That way of operating stuck with me.
How I Learn
I've always been a jack of all trades. I was homeschooled my whole life before the Army, which meant I learned early how to teach myself. When I want to learn something, I go find the knowledge and figure it out. I learn by doing, by messing it up, and by getting back up until it works.
Background
My background is in HVAC, construction, sales, and logistics. Before tech, I ran a renovation company. I learned how to plan work, sequence steps, and ship projects under real constraints. That kind of environment makes you respect systems that actually hold up when things get busy.
Sales
I've excelled at selling in both startups and large companies — HVAC and refrigeration systems and maintenance, SaaS, off-grid buildings, and complex services. At Comfort Systems USA, a $7B company, I ranked top five nationally for eight years straight. I know how to listen, build trust, and close. Sales is problem-solving with people.
Creative Work
Creativity has always been part of how I work, and it started young. I got a book on BattleBots as a kid and never looked back — from taking apart toasters to building computers, the urge to build and create always stuck with me. I build with my hands as much as I build with software: I run a 130-watt CO2 laser, 3D print, and work with mixed materials, LED systems, and digital art. Making physical things keeps me grounded. It reminds me that ideas only matter once you take action to make them.
How I Think
I have an engineer's mindset, even if that wasn't always my title. I work from first principles — I break a problem down to what's actually true, surface the assumptions everyone's relying on, and pressure-test the ones most likely to fail. I think in systems and failure modes: not just how something works, but how it breaks, where it leaks, and what happens at the edges. I'd rather build it complete than build it fast, and I own the outcome — when something breaks, I fix it and turn the lesson into a rule so it can't happen twice.
What I Believe
I believe we were created, and that I was put on this planet to make it better for my children and their children's children. Our actions ripple — through the people closest to us and down through generations we'll never meet — so being a force for good isn't just an opportunity, it's an obligation. I will be someone who builds up, not one who tears down. I believe strongly in self-ownership and responsibility: if something needs to be done, I take responsibility for making it happen; if something fails, I own it, learn from it, and fix it. That applies to work, family, and life. I care about people, and I believe success means bringing others up with you. I believe honesty builds trust faster than polish, and I try to leave every place and person better than I found them.
Projects
Active ventures, past builds, and ongoing experiments across software and physical creation.
Eventzy
AI-native event planning marketplace
VulcansForge
My Forge methodology, productized: an AI-native development platform that takes a product from idea to production — autonomous agents, 10 C-suite strategic lenses, machine-verified outcomes, and a self-improving learning loop.
Vault
Local-first AI memory and knowledge-graph system — semantic and graph search, automatic entity and relationship extraction, contradiction detection, and point-in-time recall over everything I build.
Superbrain
My digital twin — captured preference pairs, a decision-making layer, and a self-consolidating learning loop that answers “what would I do?” the way I actually would.
E-MANTIS
Ethical AI-augmented offensive-security platform — a complete engagement-lifecycle system built on one premise: AI agents should be constrained by infrastructure, not instructions. Hook-enforced scope and ethics, a formal engagement state machine, per-session isolation, hash-chained audit logging, and deep-research tooling. AI safety as infrastructure, not policy.
CerberusWard
Zero-dependency supply-chain scanner that catches nation-state attacks before they run — obfuscation, blockchain C2, credential theft, CI/CD exploitation.
Omen
Autonomous prediction-market trading engine across Polymarket and Kalshi — research, signal, and execution as one agent system.
C2Monitor
Real-time C2 beacon detection for Windows — DGA, DNS tunneling, and blockchain-C2 (Lazarus TTPs) that antivirus misses.
SKOPOS
Multi-tenant commercial-HVAC prospecting, outreach, and estimating platform — row-level security, PII encryption, Next.js and Postgres.
DirtyHandSites
Web design studio building fast, mobile-friendly, SEO-ready sites for tradespeople and small businesses.
The Project Ripple
Empowering people through meaningful connection, resources, and community-driven impact
You Deserve to Be More
A book about ownership, discipline, and rebuilding your life when things fall apart
How I Build
I build by doing the work. I ship, test, fix, and repeat. Everything here is based on things I've actually built and maintained.
Product & Systems
I turn messy problems into working systems people can actually use.
- Defining what matters and cutting the rest
- Designing workflows that reduce friction
- Building dashboards that drive decisions
- Shipping fast and iterating in the open
- Making things understandable for non-technical users
AI Systems & Agents
I build AI that does real work inside hard guardrails.
- Multi-agent orchestration, idea to production
- Local-first AI memory + knowledge graphs
- Digital twins and taste modeling
- LLM tool-use and workflow design
- Self-improving learning loops
- Machine-enforced agent guardrails
Security & Supply-Chain Engineering
I build the tools that catch attacks before they land.
- Supply-chain integrity scanning (npm, lockfiles, IOCs)
- C2 beacon, DGA, and DNS-tunneling detection
- Threat-intel detection rules (YARA, campaign IOCs)
- Offensive security — CTFs and bug bounty
- Ethical guardrails enforced by infrastructure
Sales & Business Development
15 years of closing deals, from cold outreach to contract signed.
- Full sales cycle ownership
- Prospecting and pipeline building
- Discovery, demos, and proposals
- Negotiation and closing
- Account management and expansion
GTM & Marketing
I build distribution systems that create pipeline.
- Positioning and offer design
- SEO and content that compounds
- Outbound that's targeted and human
- Simple funnels that convert
- Partner and referral loops
Operations & Execution
I've run projects where timelines and outcomes mattered.
- Planning and sequencing work
- Coordinating vendors and contributors
- Creating SOPs that people actually follow
- Fixing broken processes
- Scaling without breaking everything
Platforms & Marketplaces
I build platforms where people, money, and work move.
- Two-sided marketplace flows
- Vendor onboarding and management
- Payments, pricing, and basic trust mechanics
- Admin tools and internal visibility
- Iterating based on real usage
Automation (AI + non-AI)
I use automation to remove busywork and compress time.
- AI-assisted workflows
- Simple orchestration and routing
- Internal tools for ops and GTM
- Content and research automation
- Human-in-the-loop systems (on purpose)
Creative & Physical Builds
I design and fabricate physical things, not just screens.
- Laser-cut products and art
- Engraving and small-batch fabrication
- Digital to physical workflows
- Brand artifacts and experiments
- Prototyping ideas quickly
Tools I Use
These are tools I've shipped real work with — not things I read about.
My stack changes based on the problem. I care more about shipping than tools.
If something needs to be built, shipped, or fixed, I can usually get it done.
If it needs deep specialization, I know how to find and work with the right people.
How I Approach Building
How I build now: I've turned my own way of working into systems — an executable methodology and a model of my own judgment — so one person ships at the scale of a team without lowering the bar.
Execution Cycle
Understand Before Building
I read the actual code and state, not my memory. I separate what's known from what's assumed and find the real constraint before writing a line.
Architect, Then Build
Two passes, never one. Decide what changes and why — dependencies, edge cases, test strategy — before any implementation. Reasoning and formatting don't compete for attention.
Decompose and Run in Parallel
I break work into independent pieces and fan them out across AI agents — finders, builders, reviewers — each matched to the right model tier. I'd rather run three plans at once than grind one serially. This is what my Forge methodology does.
Build Complete
Boil the lake. Every function has a body, every error path handled, no placeholders. When 100% costs minutes more than 90%, I do the 100%.
Prove It, Adversarially
Self-review is unreliable, so I prove it — build, tests, and security scans before and after, then red-team and C-suite review the result. Done isn't “it works,” it's “every gate passes.”
Codify the Learning
Every decision, failure, and bug class becomes a detector, a gate, or a rule — and feeds a model of my own judgment — so the system catches it automatically next time. The methodology compounds; it's the real product.
Operating Principles
The Methodology Is the Product
I don't just build products — I build the systems that build them. Executable methodology beats documentation; the real leverage is the process, the gates, and the learning loops.
Completeness Over Speed
I'd rather track every gap than ship at 90%. Boil the lake — when finishing it right costs a little more, finish it right.
Evidence Over Assertion
Compile it, test it, scan it, red-team it. The thing I'm most confident about is where the bug is hiding. Nothing ships unverified.
Leverage Through AI, Ownership of Everything
One person at the scale of a team — AI on rails, local-first, with my data, judgment, and methodology owned end to end.
Want to build something?
Reach out through any of these channels.