Freelance Codex

Ask the Codex: submit a question worth turning into a page

Good questions are specific, high-stakes, and common. Ask yours here, and we may turn the answer into a maintained Codex page (anonymized) that helps others.

Freelancing gets weird in predictable ways. The same handful of problems show up again and again: pricing uncertainty, scope creep, late payment, unclear ownership of work, delivery chaos, and burnout disguised as "just a busy month."

The point of "Ask the Codex" is to capture those problems as real questions, then turn the best ones into clear, maintained answers that other freelancers can actually use.

This is not a generic advice inbox. It is a page factory. If your question is specific, high-stakes, and common, it can become a Codex entry: one canonical URL, updated over time, with tools/templates linked so the answer is operational.

If you want to browse existing answers first, start here:

What makes a good question

  • Specific: a real situation with real constraints
  • High-stakes: money, risk, time, or reputation is on the line
  • Common: lots of freelancers hit the same wall eventually

If your question sounds like "I need a practical system, not motivation," it probably fits.

Submit a question

What makes a question "Codex-worthy"?

A Codex-worthy question has three properties:

  1. Specific: a real situation with real constraints
  2. High-stakes: money, risk, time, or reputation is on the line
  3. Common: lots of freelancers hit the same wall eventually

A question like "How do I freelance?" is too broad. A question like "How do I stop a client from paying Net 60 when I'm a solo freelancer with no cash buffer?" is the right shape.

Examples of strong questions

  • "My client keeps adding 'small' requests. What exact language do I put in my SOW to make changes boring?"
  • "A client is 10 days late on an invoice. What follow-up sequence works without burning the relationship?"
  • "I can estimate the work, but the scope is fuzzy. Should I price hourly, fixed project, or a retainer?"
  • "I want to raise rates, but I'm scared I'll lose clients. What's a low-drama strategy?"
  • "I feel constantly behind. What boundaries do I set that clients actually respect?"

If your question sounds like "I need a practical system, not motivation," it probably fits.

Before you submit: check if the answer already exists

To keep the Codex clean, we try not to publish five overlapping pages on the same topic. Before you submit, skim these common "root pages":

If you find a page that is almost your answer but missing one crucial edge case, that is a great submission: "This page is close, but my situation is different because X."

That kind of feedback improves maintained pages faster than brand-new topics.

The context checklist: what to include so we can answer well

Freelancing problems are conditional. The best answer depends on constraints. The fastest way to get a useful answer is to include the context that changes the recommendation.

When you submit a question, include as many of these as you can:

1) Your stage

Pick the closest match:

  • starting / leaving a job
  • already freelancing but inconsistent
  • stable but trying to grow
  • scaling to agency-of-one
  • burned out / overloaded

If you're unsure, start here: Start here.

2) Your country (and where the client is)

Taxes and contract enforceability are jurisdiction-dependent. You don't need to write an essay; just state the countries involved.

3) What you do (one sentence)

Example: "I help B2B SaaS companies improve onboarding conversion by rewriting and testing key product flows."

If you can't write this in one sentence, that might be the real bottleneck (and the Codex can help).

4) Client type and deal size

  • B2B vs consumer
  • startup vs enterprise
  • one-off project vs retainer
  • approximate budget range

This matters because enterprise procurement, payment terms, and contract redlines behave differently than a small business client.

5) What "success" looks like (the outcome)

What are you trying to achieve?

  • get paid faster
  • stop scope creep
  • raise rates without losing clients
  • reduce admin
  • protect your time
  • improve retention
  • fix pipeline inconsistency

Stating the outcome prevents us from answering the wrong question.

6) Your current constraints and risks

Examples:

  • you need cash this month
  • you have too many concurrent projects
  • the client insists on Net 60
  • you're handling personal data
  • you have a single big client (high concentration risk)

7) What you've already tried

This prevents generic advice. Two bullets is enough:

  • "I sent one reminder email; no response."
  • "I tried fixed pricing and got scope creep."

What happens after you submit

A submission can lead to one of three outcomes:

  1. Direct answer (private)
    If the question is useful but not broadly applicable, it may be answered without becoming a public page.
  2. An anonymized public Codex page
    If the question is common and high-stakes, we may publish the answer as a maintained page (without identifying details).
  3. A tool/template update
    Sometimes the best outcome is improving a tool page (like the Invoice Template + Late Payment Sequence) or expanding an existing Codex page rather than publishing something new.

We aim to keep the Codex clean: fewer pages, stronger pages, maintained over time. That philosophy is explained here:

Privacy and anonymization

If we publish a question as a public page, we remove identifying details. In practice, that means:

  • no company names
  • no unique project identifiers
  • no private documents quoted verbatim
  • no personal information beyond what is necessary to answer (often none)

If you want details on data handling, read: Privacy policy and Cookie policy.

If you need something removed, use: Contact.

What we can and cannot do

Freelancing advice touches legal, tax, and financial decisions. Being useful requires being honest about boundaries.

What we can do

  • explain common workflows that reduce risk (scope control, invoicing cadence, capacity limits)
  • describe common contract clauses and what they typically aim to accomplish
  • provide templates and scripts you can adapt
  • help you reason about tradeoffs ("hourly vs fixed vs retainer" under uncertainty)
  • route you to official guidance or qualified professionals where needed

What we cannot do

  • provide individualized legal or tax advice
  • review your contract as your lawyer
  • guarantee outcomes (no system guarantees a client will pay, but good systems reduce risk)

For clarity on how we handle high-stakes topics, see Editorial standards and Terms.

If you want the fastest answer: pick your category

If you're submitting a question, it helps to route it to a category. Here are the most common ones and where to start reading while you wait:

Pricing and negotiation

Contracts, scope, and IP

Invoicing and getting paid

Finding clients and pipeline

Systems, admin, and overwhelm

Boundaries and burnout

FAQ

"Should I ask here or use the Contact page?"

Use Ask the Codex for questions you want answered as content. Use Contact for corrections, broken links, or site issues.

"Can you look at my specific contract?"

We can explain clauses and common red flags, but we can't act as your lawyer. For a clause map of what matters, start here: Freelance contracts: the clauses that matter.

"Will my question be published?"

Not necessarily. If it becomes a public page, it will be anonymized. Many questions are better handled by improving an existing page or tool.

"What if my question is sensitive?"

Share only what's necessary. Avoid names and unique identifiers. If you need something removed later, use Contact.

"How do I write a question that gets a useful answer?"

State your outcome, constraints, and what you've tried. If you can include the "context checklist" items above, you're doing it right.

"What if I don't know my stage?"

Start with Start here. The path pages help you choose the right defaults without overthinking.

Recommended next steps (even before you submit)

If you want to turn confusion into action today, these are the highest-leverage moves:

  1. Read the summary + "If you only do 3 things" on the page closest to your problem (use the links above).
  2. Copy one tool/template and adapt it to your situation (don't design from scratch).
  3. Submit your question with the context checklist so the answer can be precise.

Status

  • Last reviewed: Feb 06, 2026
  • Change log: Feb 06, 2026 - Expanded Ask page into a complete submission guide with context checklist, privacy notes, and internal routing links.