Organizational Independence Software
Your team either can’t build it,
or builds the wrong thing.
Both are the same failure, and it happened before anyone opened an editor: nobody wrote down what the thing was actually supposed to do. So the wrong problem gets solved, the tool gets picked before the requirement exists, and what comes back looks finished and is not.
Twenty minutes here and you walk out with the thing that was missing — the one build worth doing, and the specification your team or an AI coding tool builds from.
You do not have to be technical to use it. You have to be the person who decides what the company builds.
About twenty minutes. You bring the problem.
Why the last one did not work
Every one of these happened before anybody wrote a line of code
The wrong problem got solved.
Built properly, delivered on time, and the business did not move. It was the most annoying job, not the one actually holding you back.
The tool got picked before anyone knew the requirement.
So the requirement quietly bent to fit the tool, and the thing you needed became the thing that platform could do.
What came back looks finished and is not.
The path in the demo works. The real cases were never written down, so they were never handled — and they are most of the job.
Nobody can tell you whether it is done.
With nothing written to check it against, “done” is an opinion, and the only way to test it is to put it in front of a customer.
Your team asked questions you could not answer.
Not because they were being difficult. The decisions had never been made, and they surfaced halfway through the build where they cost the most.
You bought the licences. You can see the invoice. You cannot see the change.
Access is not adoption, and nobody can tell you where it stalled.
None of them are a knowledge problem, and none of them are a talent problem. They are six faces of one missing artifact — nobody ever wrote down, precisely enough to build from, what the thing was supposed to do.
The whole principle
One thing in your company is limiting everything else. Improve anything but that and nothing moves.
It is why a hundred percent of your staff using AI still only gets you to average. They are all making the parts of the business that were never the problem slightly faster. The output of a business is set at its narrowest point, and everywhere else is decoration.
So the question was never which tool. It was always where is the narrow point, and what do we build at it. Everyone told you to start. Nobody told you what to start with.
What it actually does with you
Four steps, in a conversation. Nothing to install, nothing to learn first.
Draw your org chart as a map of the work
An org chart is normally who reports to whom. Here it is a map of what the company actually does, seat by seat. Not the version on the website — the version that is true on a Tuesday.
Split every seat into its three kinds of work
Deciding what should happen, doing it, and reading whether it worked — strategic, tactical, analytical. Every seat holds all three, and almost nobody is good at all three. The part a person is worst at is where their seat quietly jams.
Find the one part of one seat that is holding the company back
A conversation, and a stubborn one — it will not take a vague answer and move on. Not what is most annoying. What is actually limiting the output. Almost everything you were about to build sits somewhere else and would have changed nothing.
Decide what gets built there, and whether a person still does it
Every project you start is attached to a seat and to one of those three kinds of work. That is the link between the chart and the software, and it means what you build has a reason you can say out loud to the person sitting in that seat.
Your company, as the tool sees it
Every seat gets split three ways, and each part is either done by a person or by something you build.
Every project after that starts one of three ways, and you say which: you already know what you want built, you know which seat needs the help but not the detail, or you do not know what to build yet. All three are normal, and the third one gets its own guided pass.
Then it interviews you about the thing you decided to build — eight subjects, one at a time, and it comes back at the ones you answered thinly. That stubbornness is the feature. A specification built on half your attention looks finished and is worthless.
What you walk out with
Six documents, not a summary
Enough for your own team to build from, or for an AI coding tool to start the same afternoon.
The specification
What it is, who it is for, what it must do, and how you will know it worked. Plain enough to hand to a person, precise enough to hand to a machine.
PRD.md
The design decisions, already settled
How it fits together and what it is built on — so the argument about how to build it happens before the money is spent, not after.
architecture.md
The operating manual
The rules the thing gets built under, written down once. Drop it into the project and every session after that starts already knowing your business. Most people skip this and most of the value sits here.
claude.md
The data structure
The tables it needs and the starter data to put in them, ready to run.
seed.sql
The settings it will ask you for
Every key and connection listed up front, with none of your own secrets in it.
env-templates.md
The instruction that starts the build
One paste into an AI coding tool, and the thing begins to exist. This is the step that turns a document into something running.
claude-code-prompt.md
This is what organizational independence software means, and it is the whole reason the documents matter more than the conversation that produced them. A job that has been written down can be handed to somebody and stay handed over. A job that only exists in your head can be supervised, and nothing else. Every company that cannot run without one particular person is a company where the important work was never written down.
Who this is not for
If every decision is already made — you know exactly what the thing should do, down to how it behaves in the awkward cases, and what you want now is somebody to write the code — then what you need is a developer. This does not write code, on purpose. It is built for the person who has to decide what gets built and then carry the room.
Knowing roughly what you want and not the detail is a different thing, and it is one of the normal ways to start here. So is not knowing yet.
It is also not a course. There is nothing to attend, nothing to complete and no next tier waiting at the end of it. You use it on a real problem in your own business, or you do not use it.
Atiba de Souza — who built it, and whose business runs on what it produced.
Proof
The system that runs our own business was specified with it.
Not a demo built for a stage. Athena runs the morning brief, the client records, the outbound email and the reporting for a business with staff on two continents.
The same is true of the client applications our team has delivered. The specification comes out of this, and the build starts from it.
Pricing
Priced by the project, or by the year
One project is $199. 60 of them, across a year, is $995 — which is the whole argument for the year.
Unlimited users on every plan. Build as many org charts as you like — the chart is how you work out what is worth building, and charging for thinking would be charging for the wrong thing.
You pay first and the account is built from the email you pay with. Nothing to fill in before you are allowed to buy, and nothing to confirm in an inbox before you can start.
One project
One real problem, taken from a shrug to a specification.
$199once
Nothing renews.
- One project build
- Unlimited org charts — map the whole company
- Unlimited users — bring the whole team
- Every file: the specification, the architecture, and the prompt an AI coding tool builds from
- Paid once. Nothing renews.
- Another project is $199, or a year covers 60
Annual
For the owner who keeps finding the next thing to build.
$995a year
or $99 a month
- 60 project builds a year
- Unlimited org charts and role analysis
- Unlimited users — bring the whole team
- Every file: the specification, the architecture, and the prompt an AI coding tool builds from
- Cheaper than buying two projects on their own
- Extra builds: 10 for $79
Company
For a company where more than one person is building.
$2,995a year
or $299 a month
- 300 project builds a year
- Org charts shared across the company
- Unlimited users — bring the whole team
- Everything in All year
- Extra builds: 10 for $79
Questions people actually ask
What does "Organizational Independence Software" mean?
It means software that gets a company running on written decisions instead of on the person who keeps making them. The work is mapped, the one thing limiting it is named, and what should be built about it is written down in enough detail that somebody else can build it. That last part is what independence turns on: a job nobody has written down can only ever be supervised.
Do I need to be technical?
No. It is a conversation. You describe the problem in your own words and it asks until it understands — it will not accept a shrug and move on. What comes out the other side is technical; what goes in is not.
Does it write the code?
No, and that is deliberate. It produces the complete brief that an AI coding tool builds from. Handing a machine a half-formed idea is exactly how the last attempt went wrong.
What if I do not know what to build?
That is the normal case and it is one of the three ways to start a project: you already know what you want built, you know which seat needs the help but not the detail, or you do not know yet. The third one runs a guided pass that works out what is genuinely limiting the business first, proposes what to do about it, and only then starts specifying. It regularly changes the answer people arrived with.
Do I have to sign up before I can buy?
No. You pay first, and the account is built from the email you paid with. There is no form standing between you and the thing you decided to buy.
How long does it take?
Budget twenty minutes for the conversation and a few minutes for the documents. Give it real answers and you get something buildable; give it shrugs and you get a document that reads well and says nothing.
Can my team use it with me?
Yes. Invite them into the same workspace and the map of the company is shared. That is the point — this stops being a leadership exercise the moment the people in the seats can see it.
Can I try it on one thing first?
Yes — that is exactly what the single build is. Bought once, nothing renews, and you keep everything it produces. Most people buy the year on their second problem, because by then the arithmetic has made the decision for them.
Is this another course?
No. There is nothing to attend and nothing to finish. You use it on a real problem in your own business and you leave with the thing specified.
Bring the problem you have been circling.
The one you keep meaning to block out a Friday for. Twenty minutes from now you will have it specified, in six documents, and something worth handing to somebody.