Costing an automation platform for a city property team

Rather than a monthly seat charge, the spend here is a lifetime tier bought up front. That matters for a property team contacting owners and developers in one city, because your outreach volume shifts with each development you track. The tier you choose sets how much work you can run, not how many people can log in.

What you are paying for is the connection between the apps you already use. Once those links exist, the AI researches, writes, sends, updates and logs inside your own accounts. Your existing subscriptions keep doing their jobs, and the platform sits above them rather than replacing them.

The BYOK route moves one cost off the platform entirely. On that tier you bring your own model key, so model usage is billed by your provider. That changes the shape of your spend: a fixed lifetime tier plus variable model billing you control directly, which suits teams that already hold a key.

Volume is the first thing that shifts. The Starter and Growth lifetime tiers differ by how much work you can push through, so a team contacting a few owner lists each week sits at a different point from one running continuous outreach across several developments. Match the tier to your busiest month, not your quietest.

The larger step is the BYOK unlimited lifetime tier. Here the platform stops metering your runs and your own model key carries the usage instead. For a property team with steady, predictable outreach this can simplify planning, because the platform cost is settled once and model spend follows your actual activity.

Across every tier the same capabilities are present: the single connection screen, guided setup, an activity log, and work that runs inside your own accounts. Climbing tiers changes capacity and billing method, not the core mechanics, so the decision is about volume and key ownership rather than features held back.

The concern raised is national data with no local detail, and it is worth answering directly. This platform does not sell you a contact list at all. It connects the apps you already pay for and works inside them, so the local knowledge in your own systems stays the source rather than being replaced by a national file.

That distinction changes what you are buying. Your owner and developer records, however you hold them, are what the AI works from. If your local detail lives in a spreadsheet, a CRM or an inbox, the platform reaches it through the accounts you connect, provided those accounts grant the access.

The hesitation is fair as a question about data quality, but it points at your own records rather than the platform's. Before paying, confirm that your local owner and developer data is in an app you can connect, and that the permissions on that app allow the work you have in mind.

Decide first whether you want a metered tier or the BYOK route. If your team already holds a model key and prefers a single settled platform cost with usage billed by the provider, the BYOK unlimited lifetime tier removes volume counting from your planning. If you would rather not manage a key, a metered tier keeps everything inside one purchase.

Then compare Starter against Growth by your real outreach rhythm. Count the messages, research runs and record updates you expect in a typical month for the city you cover, and add the peaks around new development launches. Choose the tier that absorbs the peak, because running out mid campaign costs more in disruption than the step up.

Finally, test the connection screen during guided setup before committing. Link the apps that hold your owner and developer details and run one small sequence end to end. If the activity log shows the work landing where you expect, the tier question becomes a simple matter of volume against the published table.