Noundry isn't a committee. It's a focused body of work maintained by one senior .NET engineer who has spent 25+ years building enterprise systems, shipping production code, and discovering — the hard way — what actually matters for long-lived C# applications.
Founder, Principal Engineer
I've been writing C# and .NET code since before it was cool — starting in the ASP.NET Web Forms era, through WebMatrix and MVC, across every major .NET release up to .NET 10. That span gives me an unusual view: I've seen which abstractions survive, which "best practices" quietly rot, and which libraries you can still trust a decade later.
For the past 25 years I've built enterprise software for JPMorgan Chase, Ernst & Young, Kellstrom Aerospace, Law360 (now LexisNexis), Catch Health, and a long list of MGAs, brokers, healthcare operators, and growth-stage SaaS companies. I've managed data-center migrations, unified HR and payroll systems across a bank merger, built a single codebase that powered 20 vertical lead-gen sites, and rescued 300-module legacy ERPs from the trash heap.
Noundry is the distillation of everything that kept working across all of it.
Every enterprise .NET project I walked into had the same shape — and the same gaps.
Somewhere around my fifteenth greenfield .NET project, I noticed I kept writing the same infrastructure over and over: a Dapper wrapper with caching, a feature-flag gate, a role-aware auth layer, a forms backend, a job scheduler, yet another Razor UI kit.
Each project hired or borrowed a handful of loosely-related open-source libraries from different maintainers with different philosophies, stitched them together, and called it a stack. Six months later half of them were abandoned and nobody could remember why the DI registration looked the way it did.
Noundry is the opposite of that. One coherent body of work. One aesthetic. One set of conventions. Forty-plus libraries that actually know about each other, a set of tools that compose instead of fight, and a CLI that threads it all together. It's what I wish I'd had on day one of every project for the last 25 years.
Every Noundry library has a scar from one of these engagements.
Tech Lead & Interim CTO
Health-insurance marketplace serving 400K+ members. Architected AI-powered compliance monitoring, designed the analytics integration layer across every corporate system, and led the engineering team through rapid regulated growth.
Founding Engineer
Migrated a national brokerage off a legacy platform onto a purpose-built .NET CRM with policy, commissions, and NIPR compliance. Evolved into Insurancera — a self-hosted, AI-augmented, 15-module insurance management platform for MGAs and brokers.
Lead Architect
Led the migration of a 300+ module legacy .NET ERP (Phoenix) to a modern API-first architecture. Classic defragmentation: identify the seams in a monolith, rebuild the connective tissue without stopping the business.
Principal Engineer
Designed and maintained a single .NET codebase powering ~20 vertical lead-generation sites generating $350K+/month — one of the earliest multi-tenant platforms I ever shipped, long before SaaS conventions existed.
Senior Engineer
Designed a single codebase launching 12+ practice-area legal publications with unified billing. Now owned by LexisNexis; used by 95% of top U.S. legal practices.
Senior Developer
Integrated global data vendors into a single compliance platform deployed to 100,000+ users across the firm — an early lesson in what "enterprise integration" really costs.
Infrastructure & Application Engineer
Managed infrastructure during the Chase / JPMorgan merger. Unified HR, payroll, recruiting, and BI systems across data centers. Built accessHR serving 10,000+ daily users; increased per-server capacity 5x.
Deep across the full .NET stack, with particular strength in systems integration and regulated industries.
Every library plays well with every other library. No dependency conflicts, no philosophical mismatches, no "here's six ways to do the same thing."
Perfect architecture that ships next year is worse than a working one that ships next week. Noundry is versioned, public, and usable today.
You shouldn't have to make 50 decisions before your first endpoint responds. Good defaults, documented escape hatches, zero magic.
Every library ships with machine-readable guides so AI assistants generate correct code the first time. No hallucinated APIs.
Hiring me for a fractional CTO engagement, asking about Noundry, or just wanting to stay on the list — send a note below.
Thanks — I'll get back to you within 24 hours.