Why this site, and not the obvious alternatives
We’re not a law firm and we’re not a chatbot. Here is what we are and why that matters for comp-plan review.
Band 1 of 4
Why an employment lawyer is the wrong tool here
An employment lawyer is the right call once you’re ready to dispute commissions in court. They are an expensive way to ask “is this comp plan reasonable” ($400 to $700 an hour, two-week turnaround, no written report you can hand back to your manager). Comp-plan review is a structured job: quota math, payout mechanics, clawback triggers, rate-shift language, accelerator caps, dispute clauses. We’ve negotiated comp plans. We’ve been on the wrong side of clawbacks. We tell you what your plan actually says, line by line. Use the lawyer once you know which clause to fight.
Band 2 of 4
Why ChatGPT is the wrong tool here
Comp-plan language is built to look standard and is not. The same “subject to management discretion” phrase means one thing at a startup and another at a public company; the same “earned upon collection” clause is enforceable in some states and overrideable in others. A general chatbot has never modeled an OTE against a real quota table, will summarize the obvious parts and miss the clawback that triggers on a deal you closed six months ago, and will invent a citation if you ask it for one. We’ve lived inside commission plans. The chatbot has not.
Band 3 of 4
A quality system, not a prompt
Borrowed from manufacturing: a serious quality program is not “we tried hard.” It is layered checks, a measured defect rate, and a patch loop that improves with every report.
Document parse and anchor map
Every line indexed before any analysis runs
Issue detection, layered
Pattern checks for quota math errors, clawback triggers, accelerator caps, rate-shift language, dispute-clause traps
Citation verification
Every claim tied back to a line in your file
Plain-English translation
Bound to the source, no rewording drift
Report assembly and final check
No claim ships unless every prior stage passed
Document parse and anchor map
Every line indexed before any analysis runs
Issue detection, layered
Pattern checks for quota math errors, clawback triggers, accelerator caps, rate-shift language, dispute-clause traps
Citation verification
Every claim tied back to a line in your file
Plain-English translation
Bound to the source, no rewording drift
Report assembly and final check
No claim ships unless every prior stage passed
Reader flags something? We patch the stage, not the report. Every reader after benefits.
Our patch loop
Every flagged issue runs the same five steps. The loop is what raises the floor — not heroics on any single report.
- 01
Flag
A reader reports an issue. Anything: a missed clause, an unclear translation, a number that does not match the source.
- 02
Diagnose
We trace it back to the part of the system that produced it — the prompt, the schema, the merge logic, the rendering layer.
- 03
Patch
We change the system, not just the one report. A new guardrail, a sharper question, a stricter check.
- 04
Verify
We re-run the patched system against the original input and against a regression set, so the fix does not break anything else.
- 05
Ship
The patch goes live for every future reader. The bar moves up once and stays up.
OUR COMMITMENT
If you find a defect, we fix the system. Then we tell you what we changed.
Every flagged issue feeds the patch loop. Every patch raises the floor for the next reader. That is the only quality program worth running.