Choosing an Automate account when your sales team is two people

Think about the purchase as three lifetime options rather than a monthly bill that grows with headcount. Starter, Growth and BYOK unlimited differ by how much work you can run and by who pays for the model calls. For two people booking demos, that split matters more than any feature list.

Your volume is small and specific: outreach to operations managers in named countries, replies sorted, demos placed on a calendar. Estimate how many runs a week that takes, then pick the tier whose volume covers it with room to spare. Growth exists for teams that expect that number to rise.

The BYOK unlimited tier changes who carries the model cost. You bring your own key, and your provider bills those requests. Read it as a different arrangement, not a bigger version of Growth, and choose it only if you already hold a key and want that split.

Keep the tiers beside your weekly routine when you compare them. A two-person team books demos in bursts, so the question is whether the quieter weeks on your calendar still leave room inside the volume you bought. Write down the runs you expect in a normal week and a busy one, then read the tier against the busier figure rather than the average.

Each tier gives you the same connection screen, where the mail, calendar and CRM apps you already pay for are linked in one place. From there the work runs inside those accounts, so a message sent or a record updated happens where your team already looks for it.

Guided setup walks you through building a sequence, and an activity log records what ran and what it touched. For a two-person team, that log is the check on whether the list contains decision makers or only names. You read the outcomes rather than trusting a count.

Starter suits a low, steady volume of demo requests. Growth raises the volume you can run. BYOK unlimited removes the volume ceiling and moves model billing to your own key. All three keep the same connection screen and log.

What you are choosing between, then, is how much work flows through one setup, not which capabilities appear. Two sellers sharing an account read the same log and see the same runs, so agree between you who watches replies and who clears the queued steps each morning before you pick a volume.

The worry is fair: a list can look large and still hold no one who signs off on a purchase. Automate does not bring its own contact list, so the quality of what you reach depends on the records you already keep and the countries you have named.

That is why the activity log earns its place. When a run adds a contact or updates a stage, you can see where it came from and whether the person matches an operations manager in a country you sell into. A big number with no matching role is easy to spot.

Treat the hesitation as a prompt to narrow your inputs. Connect the CRM where your team already records job titles, set the countries you sell into, and let the runs work from those records. The platform does not decide who counts as a decision maker; your data does.

If your CRM holds thin records, spend a week filling in titles and countries before you buy a higher tier. Buying volume first only multiplies empty rows faster, and the log will show that plainly. A cleaner input makes the smaller tier look more useful than a larger one does.

The step from Starter to Growth buys volume, not a different product. If your week already fills the lower tier, the extra money pays for more runs through the same connection screen and the same log, which is what a growing demo pipeline needs.

Moving to BYOK unlimited is a different trade. You carry the model cost on your own provider key, so the lifetime tier buys the volume ceiling rather than the model calls. Work out whether your provider bill sits comfortably below the volume premium you would otherwise pay.

Neither step fixes a weak list. Before you pay more, check that the runs already booked demos with operations managers in your named countries. The tier is a volume decision; the quality of who you reach comes from the accounts you connect and the records inside them.

One practical test: run a fortnight on the tier you hold and count the demos the log attributes to those runs. If the count is close to the ceiling, the next tier has a case. If it is far below, the money is better spent on the records feeding the runs.