Pay Band & Raise Decision Kit

Decide what the levels are worth while nobody is asking — so that when somebody asks, the answer is a lookup, not an invention.

What it is

Replaces pay set by negotiation appetite with pay set by a structure you can say out loud: the ladder built from the roles that actually exist, the bands from inputs you can cite, the placement rule that survives two people comparing numbers — then the request handled the same way every time, at a stated date, in writing, with a no that carries a path. For founders and heads of people at 5 to 200 staff deciding pay one case at a time.

What you receive

a defensible answer to what people here get paid — the level ladder in observable terms, the bands built only from inputs you can name and date, with their width, overlap and placement rule, the anomaly register with a funded dated repair, the standing raise process with its four questions and stated answer date, the counter-offer doctrine settled in advance, and the decision record with the yes message and the no message that names a path

Delivered as a single, complete .md skill file — open it, paste it into any capable chat model, and work. No installation, no account with anyone but us.

Supported models

• Claude (Opus/Sonnet)
• ChatGPT (GPT-4o/5)
• Gemini
• any capable chat model

People reach for it when

• “how to set salary bands for a small company without hr”
• “employee asked for a raise how do i decide”
• “how to say no to a raise request without losing them”
• “someone found out a colleague earns more than them what do i do”
• “should i match a counter offer to keep an employee”

Record

In the collection. The sale room is being fitted; this work goes on sale when it opens.

License

Free-shelf works ship under the DolceDrago House License — use the outputs freely, personal or commercial; the work file itself stays with the house.