About the studio
AI made it easier to build, automate, and generate code. It did not make it easier to know what should be built, owned, simplified, or left alone. Most businesses are not short on tools. They are buried under decisions, dependencies, half-connected systems, and new promises arriving faster than anyone can evaluate them.
Wild Thyme helps businesses cut through that noise, understand what they already have, and make better decisions before they spend more time, money, or trust on the wrong things.
We work directly with organizations when the problem calls for our involvement, and we have begun turning some of our experience and repeatable capability into standalone products, starting with the Outside-In Commercial Diagnostic. Alongside both, the workshop keeps running: experiments, prototypes, tools, land and sensor work, and things that have not decided what they are yet.
Reliable technology, built around the people who use it, is our craft.
From the founder.
I started Wild Thyme Studios in 2025, during a period of transition in the technology industry.
I have a deeply technical background, having spent my career in the trenches of organizations both big and small, helping improve, change, and build from the ground up. I work with teams of all kinds, building things that last.
But over the years, my work naturally expanded beyond code. I found myself helping organizations navigate heavy structural changes, untangle messy, inherited vendor relationships, and fix technical decisions that were choking their operations.
I realized that most businesses don’t need more technology. They need to understand the systems they already have so they can make intelligent, independent choices about what to do next. They need to get out from under the noise and the dependency so they can just focus on being themselves.
Wild Thyme grew out of that realization.
The studio exists to bring deep technical experience and hands-on execution to founders and operators who need to understand, simplify, change, or build the technology their business depends on, without creating another layer of dependency in the process.
It also became a place where that experience could take more than one form. Some of it belongs in an engagement. Some of it can be built into a product that stands on its own, without requiring an engagement at all.
The problem you name is rarely the problem we solve.
Sometimes the named problem is real. Sometimes it is a symptom. Sometimes it is the version of the problem that is easiest to talk about, but not the one costing the business time, money, or control.
The work starts by looking at what is happening across the technical, organizational, and business layers of the system. Once that picture is clearer, the next move is usually smaller and more specific than what was first proposed.
The goal is not to create a bigger project. The goal is to find the useful one.
Four moves, in order.
01
Define the question
Most engagements arrive with a proposed solution already attached. The first task is to work out which question needs answering.
02
Read the system
Before recommending anything, we look at how the current system works: the tools, workflows, vendors, incentives, constraints, and people around the work.
03
Separate symptoms from causes
Most pain points are downstream of something else. We name the cause clearly before proposing a fix.
04
Build the smallest useful thing
The right move is usually narrower than what was originally scoped. We prefer useful, durable work over large projects that create new dependency.
What we produce
Our first standalone product
Outside-In Commercial Diagnostic
An independent read of how a business is understood from the outside: what it appears to be saying, where friction is forming, what that is likely costing, and what options exist. Our first product.
What engagements produce
The work below comes out of direct client engagements.
Architecture review
A clear read of the current technical shape, where the pressure points are, and what should be addressed next.
Vendor exit plan
A practical path out of a retainer, contract, agency relationship, or platform that no longer serves the business.
Vendor and platform assessment
A structured comparison of the tools, platforms, or services under consideration against criteria that matter to this business.
Technical audit
A structured review of code, infrastructure, security posture, operational risk, and the decisions around them.
Workflow simplification
A review of the steps, tools, handoffs, and approvals that have accumulated around the work, with recommendations for what can be removed or simplified.
Internal tool
A small custom system built to do one specific job a team cannot easily buy.
Implementation handoff
Built systems documented and transferred to the team that will own them.
Decision memo
A written recommendation on a single technical, organizational, vendor, or architecture decision.
Standalone products are designed to be useful without requiring an engagement. The Outside-In Commercial Diagnostic is the first. For a fuller picture of how direct client engagements take shape, see our consulting work.
Working together
We work directly with founders, operators, and local or regional businesses that want more control over the technology their business depends on.
That can mean getting out of a bad retainer, understanding whether an AI idea is real, reviewing architecture, simplifying workflows, building a small internal tool, or making one technical decision clearly before more money gets spent.
Engagements start with a defined question and a fixed scope. Documentation, code, and decisions transfer to the client at the end. Continued work is offered when useful, never assumed.
The first step is a 30 minute call. Bring the situation, the constraint, or the decision you are trying to make. We’ll use the call to decide whether there is a useful next step.