Price the Assistant Path in Disagree-Minutes, Not a Free Sticker

Picture a Thursday release desk that I am using as a composite, not as a customer story. Three engineers share one assistant path because the sticker says free. The suggestion looks tidy. Nobody pushes back.

Twenty minutes later the same function is in review again. The assistant nodded at a null check the service has never had. Sound familiar?

Here is the rude question I ask before anyone opens a pricing page. How many minutes did you spend throwing that suggestion away and trying again?

If that number is fat, a free sticker can be the expensive path. If it is thin, buying a second path is theater. Which one is on your board this week?

What I am pricing, and what I refuse to fake

I am not pricing tokens. I am not pricing rollback hours. I am not scoring how "incident-adjacent" the work felt. Those are other decisions, and mixing them is how a review becomes a slogan contest.

This ledger prices disagree-minutes. A disagree event is a suggestion an engineer discards, re-prompts, or rewrites before merge. Clock time. Not vibes.

It is a conversation tool. It is not objective truth, and it is not a benchmark of any vendor. If your inputs are guesses, the output is a guess with cleaner handwriting.

Public developer threads this week kept circling the same bruise: retry decisions, and assistants that agree too fast. I am not treating those posts as evidence about any product. I am treating the bruise as a buying question. When the assistant stops arguing, do you stay, pay, or take the ops bill yourselves?

Disclosure: This article was prepared as part of MonkeyCode's product outreach.

The operator supplied two availability claims for that project, and described it as open source: free model access, and a free server option. I am not asserting a quota, a hardware shape, a duration, a model name, a license text, or permanence. Those are facts you confirm on the current project page the day you decide. If the page and this paragraph disagree, believe the page.

Four paths, one unit

You are not choosing "free versus real." You are choosing among four paths.

1. Stay on hosted free model access, if that offer still exists when you look.
2. Use the free server option, if the current offer actually changes who holds the queue and the prompts.
3. Buy a paid path from a vendor who will invoice you.
4. Self-host a stack your platform team will still operate in week six.

Define the variables before anyone types a number. Otherwise the meeting will invent a winner.

• N — engineers on this path this week
• R — discarded suggestions per engineer per week
• M — minutes to discard, re-prompt, and re-check one discard
• H — loaded hourly cost for those engineers
• Q — minutes lost when access stops mid-task, times how often it happened, times H
• P — paid invoice for the same week, in money you already spend
• S — platform hours for self-host or for running the free server option, times platform hourly cost, plus any hosting you actually pay
• D — custody hard-gate, yes or no. Not a made-up dollar figure

Weekly disagree cost is N * R * M / 60 * H. Add Q. Compare that sum with P, and with S.

A score without an owner and an expiry is a poster. Name the engineering manager. Expire the choice in 14 days. Exit if measured R does not move, or if D flips to yes.

A filled example, labeled as fiction

Do not copy these inputs into a slide and call them a pilot. They are a worksheet illustration. They are not a MonkeyCode measurement, not a market study, and not your ROI.

Suppose N = 8, R = 6, M = 12, H = 80. Disagree cost is 8 * 6 * 12 / 60 * 80 = 768 per week. That 768 is the number that can reverse "free is free."

Now a hypothetical paid pilot cuts R from 6 to 2, and P is 400. New disagree cost is 8 * 2 * 12 / 60 * 80 = 256. Savings against the old path: 768 - 256 = 512. Net of the invoice: 512 - 400 = 112. Thin. One stubborn week and the paid path loses.

Sensitivity, same fake inputs. If M is 5, not 12, the original disagree cost falls to 8 * 6 * 5 / 60 * 80 = 320. Paying 400 to chase 320 is a no, unless custody already forced you off hosted free. If the paid path keeps R at 6, you bought a more expensive nod. Why would you renew that?

Self-host uses the same math and a different bill. Six platform hours at 90 is 540, before any model hosting you actually pay. The free server option might shrink S. It might not. I will not pretend I timed it. Put real ops hours into S after a week of running the option, or do not claim a saving.

What reverses the illustration even when 768 looks scary? D = yes. If prompts, diffs, or customer code cannot sit on a hosted free path, the sticker is irrelevant. You leave. Then disagree-minutes only break the tie between a paid contract and self-host, including whether the free server option changes custody or merely changes the login screen.

Incentives, not applause

A free path trains a quiet habit. People stop arguing with the suggestion because arguing feels like wasting a gift. Paid paths train a different quiet habit. People defend the invoice. Self-host trains a third one. Platform defends the cluster they stayed up to build.

Ask who gets praised. The engineer who merges fast, or the engineer who discards a fluent wrong diff? If the first one gets the praise, your R is under-counted, and every path will look smarter than it is.

Log discards like bugs

I want a row each time someone throws a suggestion away. This format is a proposal. I have not run it in your repo, and it does not call a vendor.

# retry-log.tsv
# ts    engineer    lane    minutes reason  page_risk
2026-10-13T15:04:00Z    eng-a   hosted-free 11  agreed-with-missing-null    no
2026-10-13T15:22:00Z    eng-b   hosted-free 18  retried-same-bug    no
2026-10-13T16:01:00Z    eng-c   paid-pilot  4   style-only  no
2026-10-13T16:40:00Z    eng-a   free-server 9   queue-stall-then-rewrite    no

Read it before anyone builds a dashboard:

awk -F'\t' 'NR>2 {n[$3]++; mins[$3]+=$4} END {for (l in n) printf "%s rows=%d minutes=%d\n", l, n[l], mins[l]}' retry-log.tsv

Rows and minutes by path. That will not prove quality. It will stop the argument from living in Slack memory. If page_risk is ever yes, stop the ledger and use your incident review. This sheet is the wrong tool while a pager is hot.

Then a tiny gate. Unexecuted proposal. Swap the constants. The + 50 is a friction buffer I picked so a 10-currency "win" cannot flip a squad. Change it in the review, out loud.

# proposal_retry_gate.py — illustration, not a measured benchmark

def weekly_cost(n, r, m, h):
    return n * r * (m / 60.0) * h

def gate(hosted_cost, hosted_r, paid_invoice, paid_r, self_host, custody_blocked, buffer=50):
    if custody_blocked:
        return "exit-hosted-free"
    paid_total = weekly_cost(8, paid_r, 12, 80) + paid_invoice
    # Recompute paid_total with YOUR n, m, h. The 8/12/80 above match the fiction only.
    if paid_total + buffer < hosted_cost and paid_r < hosted_r:
        return "pilot-paid"
    if self_host < hosted_cost and self_host < paid_total:
        return "price-self-host-or-free-server"
    return "stay-and-remeasure"

hosted = weekly_cost(8, 6, 12, 80)
print(hosted, gate(hosted, 6, 400, 2, 540, False))

On these fake inputs the print is 768 and pilot-paid, because 256 + 400 + 50 is still under 768 and R fell. Drop paid_r back to 6 and the same function should refuse the upgrade. A green demo that never disagrees is not a win. It is an unmeasured nod.

Fix the script before you trust it: pass n, m, and h into gate instead of leaving the illustration constants inside paid_total. I left that smell on purpose. If nobody notices, you are not ready to let a worksheet pick a vendor.

The 4-part gate

Run these in order. Skipping to price is how free stickers win arguments they should lose.

1. Hard stop. If the change can page a human, the path does not merge it. Hosted free, paid, free server, self-host — same rule. A fluent yes is not a review.
2. Custody. Can this repo's prompts and diffs live on the hosted free path under current policy? If no, exit today. Then ask whether the free server option changes who holds the data, or only where the process runs. If the docs do not say, the answer is no.
3. Disagree-minutes versus invoice. Only after the first two. Run a 14-day paid pilot with the same log. If R does not fall enough to beat P plus your buffer, stop. Do not "give it a quarter" because the demo felt sharp.
4. Ops reality. If self-host, or the free server option, needs a platform owner you do not have, it is not the cheap path. Blank name means S is infinite for this decision.

Owner: the engineering manager for that squad. Expiry: 14 days from the first logged row, dated on the doc, not in someone's head. Exit criteria: R unchanged, custody unclear, or free access interrupted often enough that Q alone exceeds P. Archive the choice in the same doc. No silent renewals.

Re-open the doc if headcount, repo sensitivity, or the vendor's terms change before day 14. A gate that cannot expire is a loyalty program.

Who should walk away

Skip this ledger if any of these are true.

• You have no human reviewer. The hole is the merge policy, not the sticker.
• You need a quota, an SLA, or a box size. This article is not a spec sheet. Read the current offer.
• Your week is incident response. Disagree-minutes are a planning unit, not a pager unit.
• You wanted a cluster tutorial. A decision gate will not install one, and I am not going to pretend it will.
• You cannot name the variable that would reverse you. Then you are shopping.

Also skip it if the squad will not log discards. An empty TSV makes every path look free, which is the bias we came here to kill.

The only question I want back

Would a drop in M from 12 to 4, with R unchanged, keep you on hosted free model access? Or does custody already force the exit, so the minutes are a footnote?

If you are actually choosing, check the current MonkeyCode terms for free model access and the free server option, confirm the license yourself, log one week of discards, and put your own N, R, M, P, and S into the gate. Then say which input flipped the call. I will trust that over a sticker.