Plans for a small SaaS team chasing operations managers

Two tiers are published, and both are one payment rather than a recurring charge. That shape suits a team whose tool budget is set once a year. The price source is the lifetime list on softwareprogrammer.app, so open that page yourself and read the current figures rather than relying on a summary written earlier.

Your objection is the one worth holding on to. A list can look substantial and still contain nobody who signs off on operations software. When you describe the task, say plainly that you need names, roles and countries, and ask for the options with their live prices before you commit to a direction.

A session runs in four modes and you can switch between them mid-session, so research can turn into a walkthrough without starting again. Sessions are recorded with replay, which matters when two people share one seat and the second needs to see what the first was taught.

Read the two tier names as levels of certification rather than as volumes of output. Nothing in the published list promises a number of rows, sessions or countries. What the tiers differ on is the depth of teaching and the certification attached, so compare them on that basis and ignore any assumption that the higher tier produces more contacts.

Start with the lower tier and let it earn the upgrade. A two-person team can learn the shape of a session, test whether the brief returns people with real authority, and decide whether the teaching suits how you sell before spending on the certified level.

The work itself is straightforward to describe. You explain the task, a patient AI teacher researches it, and you receive options with live prices alongside a walkthrough. When a run finishes in a way you want to repeat, that finished run can be saved as a lesson, which gives the second person a starting point rather than a blank session.

Switching between the four modes mid-session is where a small team gains most. One person can watch the taught method while the other drives, then hand over without restarting the task or losing the research already gathered.

Keep the scope tight for the first month. Name two or three countries and one job title, then judge the output on whether those people could plausibly approve a demo. If the brief keeps returning coordinators and assistants, the problem is the task description, not the tier, and that is cheaper to fix than to upgrade around.

The honest risk is that a finished run can look more complete than it is. Nothing in the product guarantees that a session will finish your task, so the sensible posture is to treat every output as a draft that a person on your team reads before it goes anywhere near a prospect.

Access is the second thing to settle. You log in to your own accounts, so the assistant works through services you already hold rather than bringing its own. Plan who on the team owns which login, and keep that separation clear when two people share the work.

A third point concerns payment and identity steps. The product never enters card or ID details, which leaves those steps with you throughout. That is a reasonable boundary, and it means you should not expect a session to complete a purchase or a verification on your behalf.

Before paying, decide what a failed run would cost you. Two people testing a method for a week is a small outlay of time. Relying on unverified rows in a live outreach sequence is a larger one, because a wrong name at an operations manager's address damages the sender's reputation as much as the message.

The comparison is simpler than it first appears. Both tiers are lifetime, so you are not choosing between a trial and a commitment. You are choosing how much teaching and certification you want behind the same core behaviour: a task described, researched, then taught, shown or done with you.

For a team of two, the certified tier makes sense when one person will carry the method and teach it onward. Saving finished runs as lessons supports that, because the method travels with the lesson rather than staying in one head. The learner tier fits better when you are still deciding whether the approach works for your market.

Judge the gap on what you would actually repeat. If you expect to run the same demo-booking task across several countries, the higher tier is easier to justify. If the task changes every month as your product shifts, pay for the lower tier and keep the flexibility.

Neither tier removes the checking. A saved lesson still describes a method, and a method applied to a new country still needs a person to confirm that the roles and titles match local practice. Budget the review time alongside the purchase, then buy the tier that matches the volume of repetition you can honestly foresee.