Protect cash runway, get a simple offer ready, and start your pipeline before you quit if you can.
Map
Content map: buckets + paths
A visual overview of how the site fits together: Start Here paths, Codex pages, Tools, and Radar posts, with the routes between them.
Use it like a subway map: pick the path that matches your current bottleneck, then follow the links to the maintained page and the tool/template that turns it into action.
If you want a guided route, start with Start here. If you already know the topic you need, go straight to Search and open the relevant Codex page or tool. And if something just changed and you need timely context, browse Radar.
How to read the map (quickly)
The map is intentionally simple. It is not a complete taxonomy of every internal link on the site; it is a navigation model for the main workflow: pick a path, route to an evergreen page, then pull in a tool or a timely update when you need it.
Think in three layers:
- Stations: each card is a page you can open. The title is a link.
- Neighborhoods: cards are grouped into buckets (Start Here, Codex, Tools, Radar) so you can decide what kind of page you want first.
- Routes: the lines show the recommended relationships between pages (for example, a path that routes to a Codex page, or a Codex page that pairs with a tool/template).
The two clicks: open vs focus
Each node gives you two actions:
- Click the title to open the page in a new view and read it.
- Click Focus to highlight the routes around that node and dim unrelated parts of the map.
Focus is the fast way to answer: "If I start here, where do I go next?" Use it when you are choosing a route. Use the page links when you are ready to read and act.
What Focus highlights
Focus is deliberately conservative: it highlights the node you focused and its immediate connections. In addition:
- If you focus a Start Here path, you will see the Codex pages and tools it routes to.
- If you focus a Codex page, the map also expands around that page so you can see its connected tools/templates and related Radar posts.
If you want to reset, use the Clear focus button above the map.
What each layer means
The layers are the main "jobs" the site does. If you pick the right layer first, you spend less time collecting information and more time turning it into action.
Start Here
Start Here is a router. It is for the moment you are unsure what to read. Each path is designed to match a common bottleneck and route you to a small set of pages and tools.
If you are new, overwhelmed, or restarting, begin with Start here instead of trying to browse your way into clarity.
Codex
The Codex is the evergreen layer: maintained pages designed to stay useful as details change. It is where you go for the durable explanation and the "default" approach you can reuse.
If you already know the kind of problem you have, browse the Codex.
Tools
Tools are templates and calculators. They exist to operationalize a decision: turning "I know what to do" into a real document or a repeatable checklist.
If what you need is an asset you can reuse, go to Tools & templates.
Radar
Radar is the timely layer: short updates designed to capture what changed, who it affects, what to do this week, and where the evergreen version lives.
If you are reacting to a change, start with Radar and then route to the maintained Codex page.
Legend: what the routes mean
The legend under the map shows the kinds of connections currently drawn on this page. These are not "rankings" or "required order." They are hints about what usually pairs well.
The map uses a few route types:
- Path route: a Start Here path that routes you to a next page (usually a Codex page or a tool/template).
- Codex → Tool: a Codex page that has a related tool to help you implement the guidance (or a tool that links back to the relevant Codex page).
- Codex → Radar: a Codex page with related Radar posts, for when the moment changes but the evergreen system stays.
If you are unsure which route to follow, the simplest rule is: route to the maintained page first (Codex), then pull in the tool/template when you need to do the thing for real.
The map
Group by: Pillars. Pillars groups everything by Codex pillar; Types uses the original buckets (Start Here, Codex, Tools, Radar).
Pick a bucket, then click Focus to see connected pages.
List view is compact (better on mobile). Switch back to Visual map if you want the diagram.
Stop relying on luck. Pick one channel, run it weekly, and follow up like it is part of delivery.
Consistency comes from systems: a weekly sales rhythm, clean scope boundaries, and a simple admin habit.
If your close rate is high, raise prices. If scope creep is common, tighten SOW and change control before raising.
Use a written scope, clear due dates, and a follow-up sequence that escalates procedurally (not emotionally).
Standardize the repeatables (onboarding, SOW, invoices) and do a weekly review. Admin shrinks when decisions shrink.
Scaling is mostly process. Standardize delivery, document SOPs, and hire only when you can keep quality consistent.
Burnout is often a system problem. Fix scope, pricing, and workload ceilings so you can recover without collapsing revenue.
Legend
Path route
Codex → Tool
Codex → Radar
Suggested routes (pick one)
The best way to use the map is to pick a route based on your current bottleneck. You do not need to read everything. You need a small, correct next step.
Route 1: path-first (when you are unsure what to read)
Use this when you feel stuck, overwhelmed, or new. The goal is not to browse. The goal is to choose the path that matches your reality and follow it until you have a plan.
- Open Start here and pick the closest match.
- Come back to this map and focus the matching Start Here node.
- Open the routed Codex page and read the summary sections first.
- Open the routed tool/template and turn the advice into a draft.
You can stop as soon as you have the next action written down. Depth is optional; progress is not.
Route 2: problem-first (when you already know what hurts)
Use this when you can name the bottleneck in one sentence: pricing, scope, getting paid, lead flow, delivery, admin, or boundaries. The map helps you find the maintained page that fits, plus the tool that turns it into action.
- Scan for the Codex page title that matches your problem.
- Focus that Codex node to highlight its nearby connections.
- Open the Codex page and find the default approach.
- Follow the Codex → Tool route to the template/calculator (if available).
If you would rather search than scan, use Search to jump straight to the right page, then return to the map if you want to see adjacent tools and updates.
Route 3: tool-first (when you need a template now)
Use this when you already know what you need to produce: a SOW, a rate calculation, an invoice flow, a checklist. Tools are the fastest way to get to a usable artifact.
- Scan Tools and open the one that matches your artifact.
- If the tool links back to a Codex page, open it for context.
- Do not aim for perfection. Aim for a first draft you can iterate.
Tool-first works best when you already have a decision and you need to operationalize it. If you are still deciding, route to the Codex page first.
Route 4: change-first (when "something changed")
Use this when you are reacting to the environment: platform rules, market shifts, new risks, or new expectations. The goal is to understand the change quickly, act this week, then route back to the maintained page so you do not get stuck in update churn.
- Browse Radar for the relevant update.
- Use the linked route back to the maintained Codex page.
- Return to the map and focus the Codex node if you want to see related tools or adjacent updates.
Change-first is about speed and containment: you want enough to make a decision without turning your week into research.
If you are unsure which route applies, default to path-first. The Start Here layer is designed to route you into the right maintained page without you having to guess.
A weekly way to use this map
This map is designed to support that loop. Here is a habit you can run once a week in 15-30 minutes:
- Name the bottleneck. Write one sentence: what is currently costing you the most money, time, or stress?
- Pick the right starting point. If you do not know what to read, start with Start Here. If you do know, start with the Codex or Tools.
- Focus one node. Use Focus to highlight the routes around it and choose the next page to open.
- Do one operational action. Open the linked tool and create a first draft: a template filled in, a checklist copied to your system, a calculator run with your numbers.
- Capture the next check. Write one follow-up you will do next week (for example: send a revised SOW, update an invoice sequence, review rates, or run a small outreach block).
The point of a weekly loop is not to become "perfect." It is to prevent drift. When you keep tightening one system at a time, freelancing becomes more boring and predictable in the best way.
Two guardrails (so you do not turn this into a reading project)
- Timebox the map. Use it for navigation, then open the page you need and leave the map.
- Prefer action over collection. If you cannot point to the document you created or the checklist you updated, you probably read too much and operationalized too little.
FAQ
Is this map a required reading order?
No. It is a navigation aid, not an assignment. Use it to find the right next page faster. If you want a guided plan, Start Here is the better default: Start here.
What is the difference between clicking a title and clicking Focus?
Clicking the title opens the page. Focus is for route selection: it highlights the connections around that node so you can see what it routes to (or what routes to it) before you leave the map.
Why does the map dim other nodes when I focus something?
The goal is to reduce noise. When you focus a node, unrelated nodes and routes dim so the connected cluster is easier to read. Use it like highlighting a route on a transit map: you still know the city exists, but your eyes can track one line.
How are the routes chosen?
Routes come from curated relationships in the content itself: Start Here paths include "next" links, Codex pages can point to related tools/templates, tools can link back to the relevant Codex pages, and Radar posts connect to the evergreen topic they route to.
What do I do if I want the fast answer, not the map?
Use Search to jump directly to the relevant page, read the summary sections, and stop when you can act. The map is most helpful when you are choosing a path or exploring connections.
Where should I start if I'm brand new?
Start with Start here and pick the path that matches your reality. The map is useful after that: focus the path you picked to see what it routes to.
How often is this map updated?
The map changes when the underlying content changes: when paths, pages, tools, or relationships are updated. There is no single cadence that fits every topic; for the general policy behind reviews and updates, see Review policy.
Can I suggest a missing connection or report an error?
Yes. The easiest way is to send the URL(s) involved and what you think is missing. Use Ask the Codex for a topic suggestion or Contact for corrections.
Does this work on mobile?
Yes, but expect to scroll inside the map area. If you are on a small screen, focusing a node is the easiest way to reduce noise and make the connected route readable.