What a startup should settle before paying

Two lifetime tiers are published, Learner and Certified, and both are one-off rather than recurring. That structure matters more than the labels for a young company, because it removes the renewal question from your first test. Read the tier names as scope markers, then check the published table on softwareprogrammer.app for the figures themselves.

Begin with the work you actually owe someone this month. If your test is a short outreach sequence to a named list, the lower tier is enough to see whether the assistant teaches you a method you can repeat. Upgrade only when a specific task keeps stalling at the same point.

Treat the tiers as two sizes of the same product rather than two products. The four modes, the brief with live prices and the session recordings appear across the offering, so your decision rests on how much guided work you need, not on which capabilities exist. Confirm the scope of each tier on the source page before you pay.

Each tier buys access to the same working pattern: you describe the task, the assistant researches it and returns a brief with options and live prices. From there you switch between four modes mid-session, so a session can move from explanation to demonstration to doing the task beside you without restarting.

Sessions are recorded and can be replayed, which suits a small team where one person learns the method and another needs to follow it later. Finished runs are saved as lessons, so a sequence you complete once becomes material you can revisit rather than a one-off conversation you have to reconstruct.

The difference between Learner and Certified sits in the depth of that access rather than in the basic pattern. Before choosing, list the tasks you want covered in the first month and check which tier covers them. Where a task falls outside a tier, note it and keep that work in house for now.

The common worry is signing an annual commitment before a single reply arrives. That worry is reasonable and it points at a sequencing problem rather than a product problem. A lifetime tier removes the renewal clock, but it does not remove the need to test the method on a small, cheap piece of work first.

Hesitation also shows up as doubt about whether the assistant will finish the task. It may not, and the product says so. Some sessions end with a method you can apply yourself, which is a useful outcome for a founder learning outreach, though it is not the same as a completed campaign.

A third source of doubt is access. You log in to your own accounts, so the assistant works inside services your startup already holds. That keeps your credentials and payment steps with you, and it means setup is your job. Plan an hour for that before you judge results.

The gap between the tiers pays for more guided scope, not for a different kind of answer. If your test is one short outreach sequence and a replay to share with a co-founder, the lower tier covers the shape of that work. Pay for the higher tier when a named task keeps needing a longer session.

Judge the upgrade against a concrete bottleneck. If your team repeatedly stalls at the same stage, such as writing a first message that earns a reply, the extra scope has somewhere to go. If the stalls are spread thinly across unrelated tasks, more scope will not fix the pattern.

Set a review point before you buy either tier. Give the test a fixed number of attempts, then look at replies and at whether the saved lessons are worth returning to. That evidence, not the tier name, tells you whether more scope is justified for your startup.