Renew or release: build the owner's math, then the offer

1 · Learn the move · Constraints + negative instructions

A tenant's lease is rolling and you have two decisions tangled together: whether you would rather keep the tenant or take the space back, and what you say to them first. Asked loosely, the model answers both with invented inputs - a downtime guess, a market rent, an allowance figure - and then writes a warm letter quoting a rent it made up. The constraints separate the two jobs and ban the fiction in each. The framework uses only pasted facts and puts every unknown cost in a [YOUR NUMBER] slot, with the comparison set up but not computed. The offer letter restates only what the current lease says, leaves the proposed rent as a slot, invents no market claim, applies no pressure, and does not step on the tenant's option. On a site with an unbuilt pad next door, the framework also names the question only you can answer: whether releasing this space competes with the building you might start. Neither half says which way to go.

Two outputs, both from the pasted lease and rent roll only. 1) A renew-or-release framework: each scenario's lines, any figure I did not give you as [YOUR NUMBER], the net comparison set up and not computed, no winner. 2) A renewal letter under 150 words: current terms only, proposed rent as [YOUR NUMBER], no market claims, no pressure, nothing that changes the option. List what counsel checks before it sends. [lease sections] [rent roll row]