Choosing an Automate tier when your patch is one city

Between the entry tier and the one above it sits the only decision that matters for your patch: how much monthly volume you send through the system. You are not buying a national database, and nothing in the tiers adds contacts you do not already hold. You bring your own list of owners and developers in your city, and the platform carries the work of contacting them.

Look at the list as three ways to pay for the same connection layer. The lower tier suits a team testing a few sequences against a short list of local owners. The middle tier raises the volume ceiling for teams running outreach every week. The third route, where you supply your own model key, moves model billing to your provider instead of the platform.

Nothing on the page describes a per-seat charge that recurs each month, which changes how you budget. A team of three and a team of eight pay the same lifetime price for a given tier. What separates them is how many runs they push through and whether their volume outgrows the tier they picked.

Consider the middle tier first if your team contacts owners and developers on a rolling basis. It sits above the entry level for volume, which matters when you are working a city ward by ward and sending repeat sequences rather than one campaign. A single burst of outreach to a short list fits the entry tier; steady weekly contact usually does not.

The BYOK unlimited route appeals to teams that already hold a model account and want usage billed there. You supply the key, your provider bills the requests, and the platform tier removes the volume ceiling. That suits a team with predictable local volume and someone who can watch model spend. Teams without that oversight should stay on a volume tier.

The setup you inherit is the same across tiers: one screen where you connect the apps you already use, and work that runs inside those accounts rather than in a separate inbox. A guided setup walks you through the connections, and an activity log shows what has run.

The local objection is answered by how the product works, not by anything in the tiers. No tier supplies local data, so the quality of your owner and developer list stays your responsibility. What the platform does is run the outreach inside accounts you control, which means the coverage of your city depends on what you feed it.

Budget for two separate costs if you choose the key-owned tier. The lifetime price covers the platform; your provider bills each model request on top. A team that ignores this ends up watching two bills and may misjudge the real monthly outlay. Check with your provider about rates before committing.

Give someone on the team the job of watching the activity log in the first weeks. Runs touch live records, and the log is how you catch a sequence reaching the wrong group of owners before it repeats. Reviewing it is not optional housekeeping; it is how a small property team stays in control of its own local list.

Line the entry tier up against the middle one and the difference is volume, not features. Both give you the connection screen, the guided setup and the same log of activity. If your local list is small and your outreach is occasional, the lower tier covers it. If you are working several owner segments each month, the raised ceiling is the reason to step up.

Set the middle tier against the key-owned route and the question changes to who pays for model usage. The BYOK tier has no volume ceiling but pushes request billing to your provider. For a team already holding a model account and willing to monitor it, that trade is clear. For a team that wants one predictable payment, the volume tiers are simpler.

Write down your expected monthly runs before you decide, then pick the smallest tier that covers them with room to spare. Review the activity log after the first month and compare actual volume against what you assumed. Renewal is not the issue with a lifetime purchase, but outgrowing a tier still costs you.