Two kinds of work
MooseQuest is a solo technology consulting and product studio based in Pennsylvania. The studio is run by Kristerpher Henderson and takes on two kinds of work:
- Consulting for other teams: architecture reviews, security audits, infrastructure design, and engineering mentorship.
- Products that MooseQuest builds directly. Current work is in development.
The studio format is deliberate. Consulting keeps the practice sharp across real systems; product work applies that same judgment to problems MooseQuest picks. Both sides of the work reinforce each other.
About Kristerpher
I help teams do the early architectural, security, and infrastructure work that makes systems hold up at scale. Most of what I bring is pattern recognition across very different domains.
How I work
The upfront lift pays off. Most people skip it and end up making changes along the way — re-architecting under load, retrofitting guardrails after the incident, backfilling automation that should have been there from week one. Doing the early work honestly is almost always what separates systems that hold up from systems that don't.
Most of the resistance I've hit over the years has come from people who didn't think a given feature or guardrail was needed up front. That resistance was almost always the signal — the thinking they were defending was the thing that needed to change. Automation isn't to be feared: if you want to do the same thing every day you can sign up to be a robot, and someone's still going to need a human to check the box eventually.
I measure my own success the same way. Most people count tasks completed. I count tasks that stopped needing to exist.
Where the pattern recognition comes from
I can see the shape of that early work quickly because I've seen the patterns before, across a mix of very different domains. Companies that want to change direction, or that haven't taken full advantage of what they've already built, are where that pattern recognition pays the highest dividends.
Government climate-science research taught me how to build the systems and integrations that let scientists be productive with their high-performance computing workloads. Media taught me that at a certain size, architectural shortcuts don't hide — they show up as customer incidents, with names and ticket numbers. Big tech taught me which ideas hold up once a product outgrows the team that originally built it. And critical infrastructure taught me that the software inside doesn't get to be ambiguous about what it's supposed to do. In more than one of those systems the customer base crossed 50 million — a scale that teaches lessons smaller systems can't.
Splunk, specifically
Splunk has been a through-line across my career. I've used it at almost every place I've worked, built end-to-end automation around it, and now offer that platform expertise to clients directly.
About the name
MooseQuest was my Halo gamertag, back when competitive Halo was enough of a thing to earn a segment on MTV News. I was a strategy player — finding the angles other people missed — and I haven't stopped being one. The name came with me into the work.
Working with MooseQuest
Engagements are remote-first. Project-based and monthly retainer structures are both available. For the shape of a typical engagement, see Services. To start a conversation, email hello@moosequest.net.