Version 1 · 31 August 2026 · options only

Ceilings, and what to read

Asfiro names three ceilings and then says “hundreds more”. The library has thirty of those hundreds already written. This is what could link to what, and nothing is changed on the site yet.

The rule I would hold to. A link goes on the thing a reader would want to leave for, not on every noun that happens to match an article. One link per ceiling minimum, four maximum, and each one placed at the moment in the description where the reader would think “how”. Everything else stays plain text. Twelve links in this section would make it a directory, not an argument.

The three, as they stand

Two of the three descriptions are already right, so the suggestion is links only. The first has one word doing double duty and reads better without it.

Hiring a leadership team that will drive to results

Now. The first team got here by doing what you asked well. The next one has to decide things you will never see. Most founders hire for the job they can describe, and then keep making the decisions anyway, which teaches the new team to wait.

Suggested. The first team got here by doing what you asked well. The next one has to decide things you will never see. Most founders hire for the job they can describe, then keep making the decisions anyway, which teaches the new team to wait.

the hire itselfrun a real case study instead of an interview
the week aftermanage managers, not work
the year aftermeta-manage so their decisions compound
the first failurea contract for when they get it wrong

Raising the next round of funding

Now. The round is rarely a fundraising problem. It is whether the last twelve months read as a company that compounds, and that is settled long before anyone opens a deck.

The description is already right. Nothing to change here.

the processrun it as a competitive auction
the narrativethree rules for the story
the economicsvalue created against value captured
the year beforewhy the last twelve months already decided it

Operational excellence to reach profitability

Now. Growth hides the leaks. Profitability is not a cost exercise: it is finding the parts of the machine that were never actually built, and building them while the machine is running.

Suggested. Growth hides the leaks. Profitability is not a cost exercise: it is finding the parts of the machine that were never actually built, and building them while the machine is still running.

the rhythmset the drumbeat
the splitrun the business and build it at once
beforeverify the plan before it starts
the choosingprioritise on something other than opinion

Hundreds more — twelve the library already answers

Every one of these is a ceiling a founder actually hits, and every one has a framework already written for it. Today “Hundreds more” expands to a list of disciplines. It could expand to this instead, and then carry one link at the end into the whole library.

Finding the segment actually worth winning · needs-based segmentation
Winning a complex sale you cannot brute-force · consultative selling
Deciding faster without deciding worse · start with the answer, then pressure-test it
Changing the culture rather than talking about it · the sum of thousands of micro-behaviours · honest, frequent feedback
Getting the first product out at all · user stories, not features · deliver, automate, fail fast
Running without being in every decision · guide toward empowered decisions · conflict without escalation · when top-down stops working
Holding a strategy across three horizons · break the problem by time
Getting a company to agree on one thing · the memo that ends the debate
Building an org chart that survives the next hire · three structural changes
Knowing which question to ask yourself · the growth assessment
Proving the idea before building it · a business model in ten minutes
Turning product management into a discipline · five steps, none of them simple

What I would actually do

1. Leave descriptions one and three alone; they are already the argument.
2. Add the four links under each ceiling, laid out as above with the small “when” label. That label is what stops it reading as a further-reading list: it says WHERE in the sequence each framework belongs.
3. Replace the “Hundreds more” expansion with the twelve above, each one line, one link each.
4. End it with a single link to all thirty frameworks, which is the “hundreds more” promise actually kept.

Nothing here is on asfiro.com. Say which of the four to do and I will make it, or mark up this page and I will follow the marks.