The AI tools on your portfolio are lowering your rate

NEKO.AI — Tue, 21 Jul 2026 14:59:13 +0000

When a client asks a freelancer "do you use AI?", the honest-but-fatal answer is "yes, I use ChatGPT." You just told them the thing they are paying you for is a $20 subscription they also have. Naming a cheap tool anchors your price to it — and anchoring is one of the better-established effects in negotiation research.

But not every tool does this. The trick is to score each on one axis: when the client learns you use it, does the cost of replacing you go up or down? That sorts your whole stack into four tiers.

Tier 0 — Rate destroyers (hide these)

ChatGPT, Grammarly, Canva, Copy.ai. You use them; so does everyone. They never belong in a proposal, an invoice line, or a discovery call.

Tier 1 — Speed tools (your margin, not your price)

Whisper, Cursor, Claude Projects. They make you faster. Faster is profit. If you bill hourly and get 3x faster, you just cut your own pay. Switch to fixed-price before you get fast, not after.

Tier 2 — System tools (this is where your rate changes)

Make.com, Zapier, an API + a prompt library — built in the client's account, running without you. Same Make.com account, two outcomes: speed up your own delivery (Tier 1, invisible) vs. build a scenario that runs their process daily and you charge to maintain it (Tier 2, monthly retainer). The difference is whether the output keeps working after you leave.

Tier 3 — Proof tools (turn a system into a premium invoice)

A Loom of the system handling bad input. A before/after sheet in their numbers. A Tier-2 system nobody can see the value of gets priced like a task.

Most freelancers live in Tier 0/1 and wonder why they compete on price. The money is Tier 2, proven with Tier 3.

I put this into a free tool — check your stack, see where your rate is leaking: https://hann2626-soru.github.io/ai-tool-rate-check/

The full framework (and the scripts for the "do you use AI?" moment) is Chapter 1 of The Freelancer AI Automation Playbook.

Which tasks are actually worth automating? Take the minimum, not the average

NEKO.AI — Tue, 21 Jul 2026 14:01:41 +0000

Most "automate your workflow with AI" advice gives you the same instruction: automate your repetitive tasks. That advice is how people spend a weekend automating invoicing — the task that feels worst — and get 40 minutes a week back.

The problem is that repetitive is necessary but nowhere near sufficient. Half of your repetitive tasks will burn a weekend and give you nothing. Here's the screen I use to tell which half is which.

Score four axes, then take the minimum

For each recurring task, score 1–5 on:

A — Input availability. Can a machine reach the raw material? 5 = it's in a queryable place (a sheet, Slack, Stripe). 1 = it lives in your head or a phone call.
B — Output tolerance. What's the cost if it's wrong (not whether you can review it — almost everything is reviewable). 5 = a bad draft is a 90-second fix. 1 = a wrong invoice amount goes to a real client.
C — Decision density. 5 = fixed shape, content is lookup. 1 = every instance is a new judgment call.
D — Frequency. 5 = daily, 1 = monthly.

Then the one move that matters:

automatability = MIN(A, B, C, D)

Do not average. A task that scores 5-5-5-1 averages 4.0 and looks like a green light — and you'll build it beautifully and run it once a month. Automation is a chain; the weakest link is the real strength.

Why invoicing is a trap

Invoicing usually scores A5 (the amount is in the contract), C5 (fixed format) — it feels like the perfect first automation. But B1 (a wrong number to a client is real money) and often D2 (twice a week). MIN = 1. The most automatable-feeling task on your list is one of the worst actual candidates. Every ranking method that averages, or just counts repetition, gets this exactly backwards.

Then price it

real_rate = monthly_revenue / hours_actually_worked (including admin — this is your capacity rate, not your quoted rate). For each task, cost/year = times_per_week × minutes/60 × real_rate × 46. Rank by MIN first, then hours/week. The tasks with MIN ≥ 3 are your pool; sum them and you have a real number to act on.

Run it in 30 seconds

I packaged this as a free browser tool (no signup, EN/日本語/ES): Automation Audit. There's also a Claude Code / agent skill if you'd rather run it in your terminal — both are MIT-licensed, fork away.

If you sell automation to clients, sending a scored diagnostic like this before you quote is how you stop competing on a price list. That method comes from The 8-Hours-a-Week-Back AI Automation Audit — the full 90-minute audit and the three builds that recover the time.

DEV Community: NEKO.AI