Should your property team buy app builds by count?

Picture a Tuesday where your team has a shortlist of local owners to call, a site visit to log, and a director asking why the last mailing went to national addresses. You write down what the tool needs to do. That written brief is what turns into an app built for your city, not a list stretched across the country.

Your brief goes in, and the build comes back carrying the working parts you described: the data behind it, logins so only your people and invited developers get in, and payments where a deal needs them. The work is the build itself, not a licence to a tool you assemble yourself.

Lifetime here is counted in apps. A slot covers one finished app, and the tiers differ by how many slots you hold. If your team runs a separate tool for owner outreach and another for developer conversations, each one is its own build and its own slot.

One app lifetime, three apps lifetime, ten apps lifetime: that is the whole ladder published on softwareprogrammer.app. The division is quantity, not depth of feature. Nothing in the tier names suggests a bigger build inside a bigger tier, so read them as a count of finished apps your team can hold at once.

A small property team starting with owner outreach might sit comfortably on one slot and keep everything in a single app. A team that also tracks developer conversations, site visit notes and a pipeline view is looking at several separate tools, which points at the middle or upper tier depending on how many of those you genuinely want to run.

The practical question before choosing is a list. Write down every separate app you can name, with its own logins and its own data, then count them. That number, not the size of your team or the length of your client list, decides which tier you are buying.

Your objection is fair, and it is the one most property teams raise: national data with no local detail. A platform that hands you a national list does not help a team whose next call is to an owner three streets away. The question to ask is whether the platform builds to your brief or ships a fixed list.

Here the brief is the starting point. You describe the local contacts, the fields that matter, the logins and the payment flow, and the app is built from that written description. The detail comes from what you specify rather than from a national dataset sold to everyone in the country.

That shift changes the check you run before paying. Instead of asking how many records you get, ask whether your brief names the streets, the contact types and the fields you need. If it does, the build follows your city. If it does not, no tier will fill that gap for you.

Take a team that wants one app: owners and developers held in one place, invited logins for two colleagues, and a payment step when a reservation is taken. One app lifetime covers that single build, and the brief describes every field. This is the simplest path and keeps the team inside one tool.

Now take a team splitting outreach from deal tracking, with a third app for site visit notes. Three slots cover the three builds, each with its own logins and data. The same written-brief approach applies to each, and the store that sells every deal carries its rules into each purchase you make.

The ten app tier only makes sense if you can name ten separate tools today. Do not buy slots for tools you might want later. Count what your team would open next week, choose the tier that matches, and leave the rest until those apps are real.