About Freelance Codex

What we publish

Freelance Codex has four main content types, each with a job.

1) The Codex: evergreen, maintained pages

The Codex is the “canonical answer” layer. One page per evergreen topic, updated over time, with a visible “last reviewed” date and change log.

Examples of Codex topics:

• getting started without chaos: Freelancing basics
• finding clients reliably: Find clients without a huge audience
• pricing with math and positioning: Set freelance rates
• contracts that handle reality: Contract clauses that matter
• getting paid on time: Invoicing + getting paid
• taxes without panic: What to track weekly
• delivery and retention: Onboarding and retaining clients
• longevity: Boundaries and burnout

A Codex page is designed to be read in layers:

• a tight summary (for speed),
• “If you only do 3 things” (for action),
• then depth (for understanding and edge cases).

2) Radar: timely updates that route back to the Codex

Radar is where “the world changed” content belongs. It's not meant to be evergreen. It's meant to be useful this week.

Each Radar post answers:

• what changed,
• who it affects,
• what to do this week,
• and where the maintained evergreen page lives.

Browse: Radar.
If you're new to the format: How Radar posts work.

3) Tools: templates and calculators people reuse

Tools are the “make it boring” layer: templates, calculators, and playbooks that reduce decision fatigue and prevent improv under stress.

Examples:

• Rate Calculator
• Statement of Work (SOW) Template
• Invoice Template + Late Payment Sequence
• First 30 Days Checklist

Every tool is paired with context links to the relevant Codex page, because templates without explanations tend to be misused.

4) Research: methodology and citable outputs

Research is where “authority” is earned the boring way: by describing what you counted, what you didn't, how sources were selected, and where uncertainty lives.

Start with: Research & Index and Methodology.

How we aim to be reliable

Reliability is not a tone. It's a set of constraints.

What “maintained” means in practice (plain-language)

“Maintained” is not “updated constantly.” It means the page is treated like a living reference, not a one-time post. When the world changes, the goal is that the answer changes with it, with enough context that you can trust what you're reading.

In practice, maintenance looks like:

• status signals you can check quickly (a “last reviewed” date and a change log where applicable),
• clear scope (what the page covers, and what it doesn't),
• assumptions made explicit (so you can tell whether the advice matches your situation),
• links we try to keep working (and a clear correction path when they don't),
• timely change handling (Radar captures “this week” changes and routes back to the evergreen page).

If you're in a hurry, here's the simplest mental model: Codex pages are the map, Radar is the traffic report, and Tools are the reusable checklists and documents you keep in your drawer.

Editorial standards: how we define “truth”

We separate:

• verified facts (what's true regardless of preference),
• expert consensus (widely accepted best practices),
• informed inference (what follows from the facts, with stated assumptions),
• speculation (clearly labeled, used sparingly).

That policy lives here: Editorial standards.

Review policy: what “last reviewed” actually means

A date on a page should mean something. We define what counts as reviewed, how often pages are checked, and what triggers out-of-cycle updates.

Read: Review policy.

Disclosure: how recommendations work

If a tool recommendation might earn money (affiliate link, partnership), we disclose it clearly and avoid pay-to-rank behavior.

Read: Disclosure policy.

How to use this site in practice

This is the part most “about” pages skip, but it's the only part that matters.

How to use the site in 15 minutes/week

Most freelancers don't need more information. They need a small, repeatable cadence that prevents the business side of freelancing from becoming a constant background stressor.

Once a week, set a timer for 15 minutes and run this loop:

1. 5 minutes: scan Radar for anything that changed recently and might affect your work. If something looks relevant, skim the “what to do this week” section and follow the link back to the maintained page. Browse: Radar.
2. 5 minutes: reopen one Codex page for your current bottleneck and read just the summary layer. You're looking for one decision to simplify (scope, pricing, pipeline, delivery, or cashflow). Browse: the Codex.
3. 5 minutes: apply one tool so the decision becomes a default. That might mean copying a clause into your contract, adding a line to your SOW, or pasting the late-payment sequence into a draft email. Browse: Tools & templates.

The point is not to “keep up.” It's to keep your system from drifting. If you only do one thing this week, pick the area that's most likely to cost you money or time in the next 30 days.

If you're starting

Start with a small offer you can deliver in 1–2 weeks, get a simple get-paid system in place, and run a repeatable pipeline.

Do this:

• Freelancing basics
• First 30 Days Checklist
• Start here

If you're inconsistent

Pick one lead channel and run it weekly, tighten scope boundaries, and do a weekly admin block.

Do this:

• Find clients without a huge audience
• Your solo operating system
• I'm already freelancing but inconsistent

If you're growing

Compute your floor, package your work, and standardize delivery so you can scale without chaos.

Do this:

• How to set freelance rates
• Rate Calculator
• Freelance contracts: the clauses that matter
• I'm scaling to agency-of-one

If you're burned out

Treat burnout like a systems emergency: boundaries, cashflow, workload ceilings, and recovery time.

Do this:

• Boundaries and burnout
• Getting paid on time
• I'm burned out

Frequently asked questions

Who is Freelance Codex for?

Independent freelancers, consultants, and agency-of-one operators who want a calmer system: lead flow, pricing, contracts, delivery, cashflow, and longevity.

Is this a blog?

Not really. Blogs are optimized for novelty. A maintained reference is optimized for retrieval: you show up with a problem, get an answer you can act on, and come back later to the same page when the details change.

When we publish something time-sensitive, it goes into Radar and points back to the maintained evergreen page.

What's the difference between Codex, Radar, Tools, and Research?

The simplest split is: Codex is the maintained answer, Radar is “what changed recently,” Tools are reusable templates and calculators, and Research is where we show methodology and cite sources when counting or claims require it.

Is this only for one country?

No, but taxes and legal topics vary by jurisdiction. We keep “jurisdiction notes” explicit and avoid blending rules into one confusing blob. See: Editorial standards.

How do I know whether a page is current?

Check the “last reviewed” date and the change log (where present), and compare it with the kind of question you're asking. Evergreen concepts (scope control, payment terms, pricing models) tend to age well; rules and platform policies can change quickly. When something changes fast, you'll usually see it show up in Radar first.

Do I need to read everything?

Please don't. Start with your current bottleneck, apply one tool/template, and move on. The site is built for targeted use, not completionism.

How should I use templates without shooting myself in the foot?

Use templates as defaults, not as magic. Before you paste anything into a contract or SOW, make sure you understand what problem the clause is meant to prevent (late payment, scope drift, stalled approvals, unclear acceptance criteria). If the context page says “this only works if X is true,” take that constraint seriously.

Can I cite this?

That's the goal. The long-term plan is to make key pages citable by:

• maintaining updates,
• showing sources,
• and publishing methodology where data is involved.

See: Research and Methodology.

Do you track me or sell my data?

The details live in the policies. Start with Privacy and Cookies.

What if my situation is an edge case?

That's normal. Most “freelancing advice” is written for a clean scenario: good client, clear scope, easy approvals. When your reality is messier, look for the assumptions on the page and adapt the steps to your constraints. If you hit a gap that feels common and high-stakes, it's a great candidate for a new page: Ask the Codex.