Choosing Automate when your patch is one city

Your team does not buy a database when you choose Automate. You buy a way to make the accounts you already pay for do more of the work: asking the AI to research an owner, draft the note, send it, update the record and log the activity. For a team contacting owners and developers in one city, that means the local detail stays in your own systems.

Setup runs through a single connection screen where you link the apps your team uses. From there the work happens inside your accounts rather than in a separate tool your team has to learn. Guided setup and an activity log give you a record of what ran, which matters when several people share outreach across a patch of streets and buildings.

The tiers are grouped by volume, and one tier is built around bringing your own model key. Because the work runs in accounts you control, the platform is bounded by the permissions those accounts carry. Treat it as an operator sitting inside your stack, not as a source of property data, and plan your first connections around the apps that already hold your local contacts.

Tier choice comes down to two questions: how much work you run through the platform, and whether you supply your own model key. The Starter and Growth lifetime tiers are organised by volume. The BYOK unlimited lifetime tier is organised around your own key, which means your model usage is billed to you by the model provider rather than bundled in.

A team covering one city often runs uneven volume. Outreach may spike when a developer releases a scheme and fall away between campaigns. Read the published tier table on softwareprogrammer.app against your own pattern rather than against a headline figure, and note that the price source is that table, not this page.

For a small property team, the practical split is between predictable volume on a volume tier and variable volume on the BYOK tier. If your team already holds a model key and wants to control its own usage, the BYOK route removes a volume ceiling. If you would rather not manage a key, a volume tier keeps the setup simpler.

The objection you raised is national data with no local detail. Automate does not supply data at all, so it neither solves nor worsens that problem. What it does is act on the contacts and records already in your accounts. Your local knowledge of owners and developers stays the input; the platform handles the research, drafting, sending and logging around it.

The second thing to check is permissions. The platform can only do what the connected accounts allow, so if a team member's account cannot edit a record, neither can the automation running through it. Map permissions before you connect anything, and decide which accounts the work should run under for contacting owners and developers.

Destructive steps need confirmation, which is a deliberate brake rather than a fault. For a team sending outreach to local decision makers, that confirmation step is where you catch a wrong list or a duplicate send before it goes out. Read the activity log after your first campaigns to see exactly what ran and under which account.

Take a team on a volume tier first. They connect their contact records, their email and their sheets through the one connection screen, then ask the AI to research a set of local owners, draft notes, send them and log each step. Volume is the thing they watch, because every research pass and every send draws on the same allowance.

Now take the same team on the BYOK unlimited lifetime tier. The work is identical, but the model usage runs on their own key and is billed by the model provider. That suits a team whose campaign volume swings with developer releases, since there is no volume ceiling to plan around, though someone must hold and monitor the key.

Neither tier changes what the platform can reach. Both are limited by the permissions of the accounts you connect, and both require confirmation on destructive steps. Choose by volume pattern and by whether you want to manage a model key, then confirm the current tier details on softwareprogrammer.app before paying.