An admin scale is a Hubbard admin-tech tool for connecting a distant goal to today's actual work. It has ten rungs, read top-down — from the most abstract idea of why we exist, down to the concrete numbers we watch every week. Its power is alignment: every rung has to agree with the one above it and the one below it. When an org stalls, it is almost never one broken thing — it's nearly always two rungs that have quietly gone out of agreement. This page states all ten rungs for Automate Your Offer, plus the founder's current strategy thinking underneath them.
Current state: 0 clients today. The plan below is a hypothesis about how to land the first one — not a guarantee, a best current bet.
A per-year Goal has to survive multiplication. Subscription revenue alone at entry pricing does not get there:
| Mix | Annual | Verdict |
|---|---|---|
| 250 clients × $59/mo subscription only | ≈ $177K/yr | A real business. Not the Goal. |
| 250 clients × $99/mo subscription only | ≈ $297K/yr | Still roughly a third of the way. |
| 250 builds averaging $3,300 + 250 × $99/mo maintenance | ≈ $1.12M/yr | Hits it — because the build fee carries it. |
| 100 builds averaging $7,500 + 100 × $99/mo maintenance | ≈ $869K/yr | Close, with a quarter of the clients. |
What this rung actually says: the subscription is the floor — it's what makes revenue recurring and survivable. The scoped build fee is the main line, and it's what carries the company to a million a year. The $59/month idea in the Strategy section below is a way to get into exchange with the first clients cheaply, not the model that reaches the Goal.
Which mix we actually run — more clients at a lower build, or fewer at a higher one — is a live decision.TO BE SET Whichever way it lands, the ladder still holds: prove one, duplicate to ten, review and cut, leap to fifty, then two-fifty.
Prove the whole line works end to end, once, with one paying client. Every project below has to fire for that to happen.
Product: Traffic arriving at the wizard at a cost we can live with.
| Target | What it is here |
|---|---|
| Vital | The wizard at /build/ produces a real, personalized blueprint. If that breaks, nothing downstream matters. |
| Primary | Pixel firing, one campaign live, feed-only placements, budget set. |
| Operating | Check cost per lead daily. Do not stop and start the campaign — restarts reset learning. |
| Production | Enough opt-ins to give the Registrar a board worth working. |
Order — Cyrus runs the campaign. No edits for a full week once it's live.
Product: Confirmed, vetted meetings on the calendar.
| Target | What it is here |
|---|---|
| Vital | Every lead gets called. A lead nobody calls is money set on fire. |
| Primary | Assistant Registrar hatted, NumberBarn working, board access granted. |
| Conditional | If a lead goes quiet after the full 4-4-3 cadence, mark it and move on — don't stall the queue. |
| Operating | 4-4-3 cadence, text the booking link while still on the phone, log every touch. |
| Production | Meetings on the calendar, each carrying its vetting stars. |
Order — Amahle, every weekday, starting with the hottest card on the board.
Product: A closed client — scope agreed, payment arranged.
| Target | What it is here |
|---|---|
| Vital | They approve a blueprint they actually believe in. A yes we talked them into doesn't deliver. |
| Primary | Registrar hat read end to end; deck, notes page and checkout open in tabs before the call. |
| Conditional | If they can't pay in full, solve structure — plan, split, or financing. Never lose a build over structure. |
| Operating | Run the 23 slides; discovery is the phase that decides it. |
| Production | One signed, scoped client. |
Order — Cyrus runs every call until the close is proven repeatable.
Product: A client who knows exactly what happens next and has handed over what we need.
| Target | What it is here |
|---|---|
| Vital | Access and credentials collected. Without them the build simply stops. |
| Primary | Client created in the portal, delivery steps seeded from the product template. |
| Operating | Kickoff booked, portal walkthrough sent, expectations set in writing. |
| Production | A build with a start date and nothing outstanding. |
Order — Whoever closed them, same day as the close.
Product: A working machine, live on their domain.
| Target | What it is here |
|---|---|
| Vital | It actually works for their business — not a demo, a working machine. |
| Primary | Scope frozen in writing before build starts. |
| Conditional | If a required API doesn't exist, the scope conversation reopens before we build around it. |
| Operating | Client approves each delivered step in the portal as it lands. |
| Production | One machine delivered and switched on. |
Order — Tanina, against the dated steps in the plan.
Product: Recurring revenue started.
| Target | What it is here |
|---|---|
| Vital | The monthly starts. Without it we built a one-off, not a business. |
| Primary | Billing set up and the first payment collected. |
| Operating | Maintenance tier recommended by name at handoff, not months later. |
| Production | One client on a monthly plan. |
Order — Set at handoff, before the build is signed off.
Product: A client getting real leads and saying so.
| Target | What it is here |
|---|---|
| Vital | They actually use it. An unused machine churns no matter how good it is. |
| Conditional | If leads aren't flowing after 30 days, we look at ad spend and the catch tool before anything else. |
| Operating | Check in at 7, 30 and 60 days. Ask for the number, not for a feeling. |
| Production | A documented win — and a referral asked for. |
Order — Amahle checks in; Cyrus handles anything that needs fixing.
Same seven projects as Program 01 — they don't change, the way we run them does. What changes at this level:
Same seven projects as Program 01 — they don't change, the way we run them does. What changes at this level:
Same seven projects as Program 01 — they don't change, the way we run them does. What changes at this level:
A project with no program above it is somebody's pet task. A target with no project around it is a wish with a number on it. An order with no target behind it is just being told what to do. Kept as one tree, every instruction on the board traces up to the goal — and when something stalls, you can walk the branch and find the exact place it broke.
These live inside the tree above — this rung is the reference for what each target type means. Every project in every program uses these six.
| Target Type | What It Does |
|---|---|
| Major Target | The broad thing being achieved by the project. |
| Primary Target | The organizational and terminal groundwork that has to exist first — who's on post, what's actually set up. |
| Vital Target | The one thing that must get done, or the whole project fails. |
| Conditional Target | "If this, then that" — the find-out-first steps, used before committing further. |
| Operating Target | The actual sequence of actions, and who does each one. |
| Production Target | The amount of product to be produced — with real numbers. |
| Type | Target |
|---|---|
| Major | Land and deliver client #1 — proof the business actually works. |
| Primary | Someone is holding the Assistant Registrar hat and is actually working the leads board. |
| Vital | The wizard at /build/ has to actually produce a working, scoped build — if it doesn't, nothing downstream matters. |
| Conditional | If a lead goes quiet after three touches, then mark it cold on the leads board and move to the next lead. |
| Operating | Assistant Registrar runs the 4-4-3 cadence on every lead, logs every touch, and books the Blueprint Approval Call. |
| Production | 1 client closed and delivered. No fixed date is set for this specific target yet — the ladder's only fixed date is Dec 31 for 250TO BE SET |
Orders sit at the bottom of every branch of the tree above — each project ends in one. The table below is the standing set that applies across all of them.
| Standing Order | Who | When |
|---|---|---|
| Run the 4-4-3 follow-up cadence on every lead. | Assistant Registrar post | Every lead, ongoing |
| Log every touch on the leads board. | Assistant Registrar post | Every contact, no exceptions |
| Drag the card to reflect the lead's current status. | Assistant Registrar post | Immediately on status change |
| Book the follow-up before hanging up the call. | Assistant Registrar post | On every Blueprint Approval Call |
Kept short on purpose — this table lists what's real today, not an aspirational full ops manual.
One real person pays for the Lead Machine. The wizard at /build/ produced a working scope, the Assistant Registrar booked the Blueprint Approval Call, and delivery happened without heroics. It's proof, not a victory lap.
Ten people pay, using the same path that got the first one. There's a full written overview of exactly how it happened, and a list of what already got cut because it slowed things down.
A deliberate leap using what the overview at 10 revealed — not a grind, a repeatable jump we understood before we made it.
200 to 300 people are paying $59–$99 a month. It's a real business, not a hustle, and the giveaway has started to tighten because the company is more solid than it was at the start.
Tracked live on the staff dashboard. Up is black, down is red — no interpretation needed to see which way a stat moved. Every graph is fixed to a 13-week range, so a good or bad week is always seen next to its recent history, not in isolation.
Org's VFP — "We automate the selling so you only talk to buyers."
That one sentence is built from five sub-products, each one produced by a different post. See the Org Board for how each division fits.
| Sub-Product | Produced By |
|---|---|
| Confirmed, vetted meetings | Assistant Registrar |
| Closed, scoped clients | Registrar |
| Delivered, working builds | Production |
| Verified, correct work | Qualifications |
| Satisfied customers who refer and re-enrol | Public |
$59/month — hosting and keeping the machine running. That's the recurring floor, and it's deliberately low: the point at this stage is to get into exchange with the public, not to protect margin.
The build fee is handled separately from the monthly — a small additional monthly amount that pays the build off over time rather than a wall of cash up front. Exact figure and termTO BE SET
We run their ads for the first thirty days at no charge. One condition, and it's the important part: they take what they're saving and put it into ad spend. That way the machine actually gets fed, they see real leads in the first month, and the value is proven instead of promised.
Why it works: the single biggest reason a new client churns is that they never turned the thing on. This turns it on for them.
After the first thirty days, we rebuild their website. Not a template with their logo dropped on it — a redesign and rebrand that matches the machine we just built them, so the traffic we're sending has somewhere worth landing.
Why it works: it removes the excuse that the leads didn't convert because the site was embarrassing.
We hand them the media, so the selling stops depending on the owner doing it manually:
Why it works: most owners don't stall on strategy, they stall because nobody made the assets. This removes the manual work and hands them a machine that's already loaded.
The Lead Machine brings people in · the new website and funnel give them somewhere to land · the media does the selling — explainer video, ad creative, and the ebook giveaway · and the whole thing runs whether or not the owner is working. That's the full promise — we automate the selling so you only talk to buyers — delivered as three concrete things rather than a claim.
And it tightens as we climb. This much giveaway is a startup tool for getting the first clients into exchange. At 10, at 50, and at 250 the stack contracts — items move from included to paid — because by then the proof exists and the company doesn't need to buy belief.
Done at the top: Cyrus, as Founder & Executive Director, with the Board of Advisers. It answers what are we doing this period, and why that instead of something else. It's written down, it covers a period rather than a day, and it changes rarely. Everything on the ten rungs above is strategic planning. Output: a written strategy.
Done by the executive secretaries — HCO Executive Secretary, the OES (Tanina), the PES (Amahle) — for the divisions they command. They take the strategy and break it into programs, projects, and targets, then into daily battle plans: the short list of things a specific person intends to get done today, aimed at the strategy. This is the layer that gets skipped, and skipping it is why plans die on paper. Output: battle plans with names and dates on them.
Done by whoever holds the post. They work their battle plan, log what they did, and produce their department's product. They shouldn't have to reverse-engineer the strategy to know what to do today — that's the whole point of layer 2. Output: the actual valuable final products, and the statistics that prove them.
The rule that ties it together: a strategy nobody converted into a battle plan is a wish. A battle plan with no strategy behind it is busywork. When output stalls, check which of the three layers is missing before blaming the person at the bottom of it.
What we're selling right now doesn't have to be elaborate. Call it the Lead Machine, knowing what it becomes later.
Getting into exchange matters more than margin. Even a small monthly — $59/month, or $99 — from a lot of people is substantial for software running on Claude credits.
Offer partnerships and generous deals early. We can hook people up while we're small.
As each milestone is passed, tighten the giveaway. The looseness is a startup tool, not a permanent policy — it contracts as the company becomes more solid.
The point is to get started and get into exchange with the public, even at thin or no margin. You don't need to win big to begin; you need to begin.
200–300 people paying $59–$99/month is a real business.
This isn't a document to read once. It's reviewed whenever something stalls — a stat stops moving, a project keeps missing, a program doesn't seem to be working. The fix is almost always an out-of-alignment rung: a Project running with no Program behind it, an Order nobody actually gave, a Statistic with no Target set for it. Find the rung that's disagreeing with the ones around it, fix that one thing, and the rest of the scale usually falls back into line on its own.