Free frameworks and diagnostics
The thinking I use inside businesses, written down and given away. No signup wall on any of it. If it is useful on its own, take it and use it.
The operator
The work that starts with you. The person at the top is the biggest lever in a business under ten million.
Model the floor, not the expectation
When you put a number in front of anyone, show the slowest credible version, not the one you are hoping for. Underpromising on paper is how you earn the yes, and it is the only forecast you never have to walk back.
What leverage actually means
The whole brand is named after this word and most people read it wrong. Leverage is the gap between what you put in and what you get out. Five forms, they stack, and the highest-leverage act is a good decision, not a build.
The umbrella of why
Founders collect tactics because tactics feel like progress. A tactic with no goal above it and no why above that is just motion. Three layers that tell you which of the hundred things to actually do.
Knowing is not doing
You watched the video, you understood it, nothing changed. Knowledge is the cheap part. Theory, practice, habits: the three steps of real change, and why more theory never fixes a practice gap.
The best business development is personal development
The uncomfortable first answer to how you grow a company under ten million: it is rarely out there in the funnel or the hire. It is the person at the top. Work on the business all you like, it snaps back to the size of the operator. The pillar the rest of these hang off.
What you actually control
Most founder energy goes to the part of the week that does not respond to effort. Two lists at the start of the week, and the sharp rule most people get half right: judge yourself on input, steer the business on output.
Reps, not perfection
You do not get good by getting it right, you get good by getting enough reps that right becomes cheap. Why the last five percent is a trap, consistency beats intensity, and a failure is a data point rather than a verdict.
Plan it, then track it
Every founder swears they have no time and cannot say where it went. Those are the same problem. Planning and tracking are two different skills, most people were taught neither, and this is the one to fix first.
Walk in as a peer
How you show up in a room decides most of the outcome before the work is mentioned. Peer not vendor, curiosity not humility, and why the label you accept becomes the ceiling other people hold you to.
People and teams
Grading, developing, and getting real ownership out of the people around you.
The day 90 question: you already know
Skill takes a year to build. Character shows up in weeks, and research across 1,000 hires says the trajectory is set by day 90. The seven-signal A player checklist, the scorecard to write before day one, and why you sit on answers you already have.
You did not delegate it, you loaned it out
You think that function is off your plate. The test: in the last thirty days, did you make or reverse a call the supposed owner could have made. One yes and you never handed it over, you just stopped watching. The check that maps to which seat you run from.
Bring decisions, not problems
The test for whether someone takes load off you or adds to it: when something breaks, do they hand you a question or a recommendation. What a real decision looks like, and how to train your team to bring them.
Same words, different dictionaries
Most of what looks like disagreement is two people using the same words and meaning different things. You both said done, you both said soon, you shook hands and walked away misaligned. How to catch it before it costs you.
You learn it better when you have to teach it
Knowing from the start that you will teach a thing changes how you learn it. Teaching forces you to translate, which exposes what you never actually understood. The cheapest way to make sure something landed.
As is, the gap, to be
You know someone is not where you need them. Naming what is actually in the way is the hard part, and it is never one thing. Six named gaps, why they cause each other, and the twenty minute test that stops you fooling yourself.
You cannot touch the keyboard
Why the work you hand over keeps coming back, and the one rule that decides whether a handover sticks. Also why you are worse at explaining your strongest skill than your weakest one.
Player Levels: how to grade your team honestly
S, A, B and C players, what each one is actually driven by, and what to do about every person you have. Most advice says cut your C players. The money is in developing your B players.
Building systems
Turning what works into something that runs without you, and does not quietly slide back.
Harvest the organs
When you inherit a system, a tool, a competitor's playbook, or an AI's plan, the instinct is to rip it out and rebuild clean. Usually the slowest, most wasteful option. Keep, harvest, fix, cut: take the parts that work and leave the rest.
Silent errors
The problems that hurt a business are rarely the ones that set off alarms. They are the ones nothing flags, so nobody fixes them, so they compound until a customer finds them. The job is not to never fail, it is to make failures loud.
Why good companies slide backward
The thing that kills a healthy business is rarely a competitor. It is comfort on one side and a neglected frontier on the other. Why a standard is regression insurance, not bureaucracy, and how to hold both at once.
Test it five times
A thing that worked once has not been proven, it has been observed. Run it five times before you trust it, especially anything with an AI in the loop. Why five, and the sister rule for when something breaks.
The walking skeleton
Most founders wait months for the perfect system and ship nothing. Build the thinnest version that runs end to end, ugly but alive, put it in real use, then thicken it. How to keep a build from becoming a science project.
Workflow or SOP: where the detail belongs
Most process documentation fails for one reason: the detail is at the wrong altitude. Three levels, what each is for, and the rule that keeps a diagram readable. Includes a worked example you can copy today.
Built, in use, documented, owned
Four words that tell you whether anything in your business is actually finished. A system nobody uses, a procedure nobody follows, and a person nobody lets decide are the same failure.
AI is not your constraint
I build custom AI systems, and I am telling you it is probably not your problem. Automating something that did not matter just gets you more of it, faster. What to fix first, and in what order.
Diagnose your business
Short reads and tools to work out where you actually are before you spend money or time.
Are you supply or demand constrained?
Answer this before you spend money on anything. Almost every wrong move in a business under ten million comes from getting it backwards, and the split case gets misdiagnosed constantly.
What happens if you are gone for two weeks?
Not the dramatic version, the ordinary one. Four possible answers, what each looks like, and the first move for each. Most owners assume they are in the top one and are actually in the second.
Which seat are you actually in?
Six functions, two questions each. Find out whether you run your business from the Employee, CEO or Chairman seat, what your real constraint is, and how far you are from the next seat.
Founder OS: your operating manual
A separate product of mine, at mapyouros.com. Eight tests, then a written manual for how you are wired: how you decide, where you stall, and what to stop trying to fix about yourself. It is also step one of my intake, so if you are an established founder and there is a fit, I will know before we ever speak.
Working with an advisor
Written against my own interest: how to tell what you are buying and whether it is working.
Systems or therapy: which half are you buying?
Good help works on the person at the top and builds the machine underneath. A lot of it does only one and charges for both. The failure mode that makes founders swear off help, and how to tell which half is in the box before you pay.
Name the constraint, do not prescribe the fix
You cannot diagnose a business in five minutes, so anyone who hands you the fix that fast is selling, not diagnosing. Good advice names your real constraint and stops there. How to screen everyone who wants your money, and a discipline to use on yourself.
Advisor, operating partner, board member
Ask four founders what a consultant, a coach, and an advisor are and you get four answers. The honest taxonomy, drawn along the one line that matters: who is accountable for the outcome, and how to tell which one you actually need.
How to tell whether your advisor is worth it
Written against my own interest. You cannot cleanly prove what an advisor caused, and most of us quietly prefer it that way. Four things to agree before you start, and five questions worth asking anyone who wants your money.
More of this happens live
The community is free. Bring a real business question and get a real answer, in front of other founders working on the same problems.
See how the community works