BYOStack is a personal trainer for building AI skills.
Build AI skills that actually work for your workflows — a compounding stack where you own the intelligence.
Claude gives everyone the same gym. BYOStack gives you the trainer and the program: four Coaches — each a Claude Project that walks you through one stage — that push you to determine what is worth building, capture how your work actually happens, and pull out the judgments that make it yours. The skills you build come out significantly better — and they are yours, because you built them through a guided methodology and proper reasoning.
And if you already build in Claude, here is exactly where this sits: BYOStack is the upstream architect. Claude’s native skill-creator is the general contractor. The contractor is excellent — the build does not happen without it — but the contractor builds what the plans call for. BYOStack architects the plans before anything is built: which skills deserve to exist, what they must capture, and the judgments they have to carry. When finished architectural plans reach the general contractor, significantly better skills emerge from a solid foundation, because the thinking happened first.
Maybe you are paying for two or three AI subscriptions. You have watched the tutorials. And you are still doing your work more or less the way you did it a year ago.
That is not because the AI is weak. It is because nobody taught you the methodology to apply it.
Most "AI productivity" content tells you to automate everything. That is the wrong approach. Most things should not be automated. Most workflows are not worth the build effort. And most prompts produce mediocre output because the thinking that should have happened first never did.
BYOStack teaches you to do the thinking first.
What this is — and what it is NOT
Read this before you spend a dollar, because this is where expectations go wrong if they are not set plainly.
BYOStack is a methodology. It teaches you a repeatable system for deciding what to automate, deconstructing it — the process and the judgment underneath it — building it, and iterating it, for your own specific work. It is NOT a library of done-for-you skills you drop into Claude and run. The output of every Coach is a starting point you iterate, validate, and apply your own judgment to. The methodology gets you to the right answer faster. It does not replace the thinking.
If what you want is a library of pre-built skills, BYOStack is NOT that product, and you should NOT buy it. If what you want is a system that teaches you to build skills the right way for your own work, you are in the right place.
What you actually receive: a Version 1, NOT a finished skill
When you finish a run, the Execute Coach produces Version 1 (V1) of your skill — a properly reasoned starting point built on a workflow that passed the Four Lenses and went through the full CASE methodology — carrying your process and the judgment underneath it. V1 is NOT finished. It is NOT done-for-you. It will NOT produce exactly what you want on the first run, and no honest methodology would promise otherwise. You iterate it — two to four cycles minimum — into something you would use without editing.
That is the deliverable, and it is the point. Tools you subscribe to disappear when the subscription ends. A methodology you have internalized stays with you for the rest of your career. This is the difference between renting AI capability and owning it. With BYOStack, you own the intelligence.
How it works
BYOStack runs on four components you will use on every workflow:
- CASE — Compile, Analyze, Strategize, Execute. A four-stage process. You do not get to skip stages.
- The Four Lenses — forcing function, time savings, cost savings, revenue generation. A workflow has to pass at least three of the four to be worth building.
- Universal Skills — the reusable building blocks you build once and call from every workflow that needs them. This is how your stack compounds.
- The Deployment Decision Tree — where a skill lives decides whether it works the way you need it to.
At the start of the build, you write one Outcome Statement — a single five-variable formula adapted from Dan Nicholson’s Solvable Problem™ framework that converts a vague ambition into a surgical build target. Skills built from a clear statement consistently outperform skills built from vague intentions.
Four Claude Projects — one Coach per CASE stage — walk you through all of it. They are demanding on purpose. When you try to skip the thinking, they push back, because the thinking is what makes the skill work.
The part most documentation never captures is the judgment. Every workflow you run carries decisions you no longer notice making — which items get extra scrutiny, what gets escalated, what you check before you trust the output enough to send it. Those calls are the difference between a skill that mimics your real work and a generic one, and they are invisible to you precisely because you have made them a thousand times. The Compile Coach is built to extract both layers: process deconstruction takes the workflow apart into its steps, and a dedicated second pass pulls out the judgment underneath them — named, on the record, in your own words. Your process is what you do. Your judgment is what makes it yours. And expertise being invisible to its owner is not a quirk of individuals — it is true wherever expertise lives.
Do NOT just automate it — ask whether it should exist
Inside CASE, the very first stage — Compile — carries the highest-leverage question in the whole methodology, and it is the one most people skip: is this the right way to solve the problem, or just the way your current tools forced you to solve it?
Most workflows were shaped by the software you happened to learn. You learned a platform, you learned its steps, and the workflow became "the steps the tool requires." Automate one of those without questioning it and you do NOT get leverage — you get a faster version of a process that was never the best path. You automated the tool’s constraints instead of removing them.
BYOStack runs a first-principles pass on every workflow before you build: name the real outcome, work backward to the most direct path, and eliminate the constraints that were never yours. More often than not, the slowest part of your workflow was never the work itself — it was the tool you were doing the work inside of. That is the difference between optimization and redesign. Optimization makes the existing path quicker. Redesign asks whether the existing path should exist at all.
Built on Claude. The methodology is universal.
BYOStack is built to run on Claude. That is where the Coaches live and where you will build your skills, so you should be working in Claude or willing to. Other platform versions may follow if there is demand for them — that is a possibility worth naming, not a launch promise.
The methodology itself is bound to none of that. CASE, the Four Lenses, the first-principles pass, and the Outcome Statement come from a general decision-making framework, not from any AI tool. Once you have internalized them, you will catch yourself running them on decisions that have nothing to do with AI — what to build, what to walk away from, where the real constraint actually sits. You are learning a way of thinking that is pointed at AI skill-building first and applies to most any business decision you face.
Who this is for
- You have real workflows worth solving and you are willing to do the thinking the methodology asks for.
- You want to own a repeatable system, not rent a one-off result.
- You are comfortable iterating a V1 into a working skill over two to four cycles.
- You work in Claude, or you are willing to.
Who this is NOT for
- You want a library of done-for-you skills you can drop in and run. BYOStack is NOT that, and you should NOT buy it.
- You want something that works perfectly on the first run with no iteration.
- You are not willing to document a workflow in detail before automating it.
- You are looking for a prompt pack or a list of tricks.
A note on scale: BYOStack is a personal-use product. The methodology in it is also what I bring into organizations as a Strategic Advisor. If your read after using BYOStack is "we need this across our company," there is a separate conversation for that — byostack.ai/scale. No pitch, just a real conversation.
The price is $97, one time
For that you get the BYOStack Methodology Guide and the four Claude Project Coaches — Compile, Analyze, Strategize, and Execute — plus the supporting materials that walk you from setup to your first shipped skill. You pay once. It is not a subscription, and nothing expires — the methodology is yours to keep. It is a considered purchase rather than an impulse buy, and that is deliberate: at $97, you will actually open the files and do the work. One requirement, stated plainly: the Coaches run in Claude, and their sessions are long and deliberate by design — so you need a Claude Pro plan or higher, currently around 20 US dollars a month, paid to Anthropic, not to me. The free plan includes Projects, but its usage limits cut a Compile session short in the middle, and a half-captured workflow is worse than none. If the cost of the tool your skills run on is a dealbreaker, this product is not for you yet.
Before you buy: how this works, and what is yours
BYOStack is a methodology product. The Coaches produce suggestions and starting points, not finished work. Every output requires you to iterate, validate, and apply your own judgment. The methodology gets you to the highest-leverage outcome faster — it does not replace the thinking. That is a feature, not a bug. And the judgment the methodology extracted from you does not belong to a vendor’s model or a template library — it is on the record, in your artifacts, yours.
And because you own the skills you build, you own what they do. The skills are built to confirm before they act — nothing should send an email, place a calendar hold, write to a system of record, or change a file without your explicit go. You verify that on every live run, especially for anything that touches clients, contracts, money, or data. BYOStack teaches the method; it does not run your skills, and the responsibility for what they do rests with you. That is not fine print. It is the same ownership that makes the methodology worth having.
About Jeff Merck
Jeff Merck is a Certified Certainty Adviser, executive professional, and serial entrepreneur with more than twenty-five years across enterprise sales, operations, technology, and delivery. He solves complex problems using his own methodology, and BYOStack is that methodology made teachable — the same thinking he brings into organizations as a Strategic Advisor. He is driven by a mission to help others succeed and make a global positive impact through his collective works. When he is not working or pondering problem-solving, he spends his time with his family and on his spiritual development.
If you have read this far and it fits, you are who this was built for. Start with one workflow that matters.