What a local property team should ask before paying

Three decisions sit in front of you before any money moves: which tier fits the work, what you will run first, and how you will judge a session that does not complete. Take them in that order. The page you are reading holds no figures; the lifetime tiers are published on softwareprogrammer.app, so read them there against the sessions you would actually hand over.

For your team, the covered work is a brief with options and live prices attached, four modes you can switch mid-session, recordings kept with replay, and finished runs saved as lessons. That covers the shape of the sale you make in one city: choosing a housing scheme or a site, drafting the approach to an owner or a developer, and leaving a record your colleagues can watch back.

Start from your pipeline rather than the number. Count the owner and developer contacts your team approaches in a normal month, how often someone needs teaching rather than a finished email, and how many of those runs are worth saving. That count tells you whether one lifetime tier is enough and whether the upgrade is a question for this quarter or a later one.

Learner and Certified are the two lifetime tiers, and both are paid once rather than monthly. Neither is a seat count, so do not read the page as one plan for a junior negotiator and one for the owner. What changes between them is described in the brief you request, which sets out the options and live prices together, so ask for that brief and read the two side by side.

Underneath the tiers the mechanics are shared. You open a session, choose a mode, and switch modes partway through when the work changes from teaching to doing. Recordings are kept with replay, so a colleague can watch how an approach to an owner was shaped. A run that ends well can be saved as a lesson, which is the part that carries your local detail forward.

Judge each tier against the same three things: how many sessions your team would start in a month, how many finished runs you want kept as lessons, and who needs to watch the replay. A team that mostly trains newer negotiators on local housing schemes will weigh the teaching side; one that runs outreach every week will weigh the task side.

The worry you have named is national data with no local detail, and it is the right worry for a city team. Nothing here is a national list. You bring the district, the owners and the developers, and you brief the assistant on your own patch. The product works from the brief and the accounts you log in to, which is why the local detail comes from your side of the desk.

The method for testing that: one district, one set of owner contacts, one developer conversation. Start the session, switch modes when the work shifts, and watch the replay afterwards to see where the local knowledge came from. If the run does not complete, read the brief and the saved lesson before anyone acts on it, because completion is not guaranteed and the judgement stays with your team.

Because you sign in to your own accounts, the assistant works inside services you already control rather than reaching into new access for you. There is no data package to backfill with national owner records. If your doubt is about coverage, the honest answer is that the coverage is what you write into the brief.

When do you move from Learner to Certified? After a saved lesson has proved useful at least once. Run a district, save the finished run, let a colleague replay it and try the same approach with a nearby developer. If that replay earns its place in the week, the upgrade question has evidence behind it. If it sits unwatched, the lower lifetime tier is doing the job.

Price the decision against the work you would hand over, not against a seat. One payment covers a lifetime tier, and the second tier is published on the same page, so compare them as two levels of access to the same product rather than a separate tool. Read the brief with options and live prices while you decide, so you are comparing on today's terms.

For most city teams the sensible order is: brief the work, run one district, save the lesson, then upgrade when colleagues ask for the replay. That way the second payment follows a run your team has already used with an owner or a developer, rather than a projection drawn from a national average you never trusted.