Which tier fits the lists you have to deliver?

You have already run spreadsheets by hand, trialled a scraped-list tool and sent a sample file to a client who asked where one column came from. None of that settled whether a generator can carry the provenance your handover needs, because the rows arrive as drafts rather than as sourced records.

Count the rows you must defend in a single client delivery, then count how many of those rows a generator can produce before a person checks them. That second figure decides your tier more than any headline number on the pricing page, since review time is yours and the credits are finite.

Work from the lifetime tiers published on softwareprogrammer.app: Creator lifetime, Store lifetime and BYOK Store lifetime. Read each as a different amount of the same generation work, then test the smallest against your hardest client sample. The file is judged by the client, not by which level you bought.

Creator lifetime covers bulk AI listing generation for one operator building files. You write product records in batches and let the generator draft titles and descriptions. The existing outputs are aimed at store listings, so you are adapting the tool to lead work rather than buying a contact-verification service.

Store lifetime widens that work toward exports for the major stores, with SERP title variations drawn from search result patterns. For a contractor this matters when a client wants catalogue-style rows rather than a pure contact sheet, because the export shape already matches what the store expects to receive.

BYOK Store lifetime lets you bring your own key for the model behind the generation. That choice usually appeals to a contractor who wants to control which engine writes the copy and keeps the spend visible in their own account rather than bundled into the tier.

The worry behind the comparison is not price. It is that a client opens the delivered file, picks a row and asks for the evidence behind it. A generator built for product listings produces plausible copy and structured columns, but plausibility is not verification, and you must say so plainly.

So the real question is what you can honestly attach to each row. If a client needs a source per record, keep your verification step and use the generator only for the parts it drafts well, such as titles and description text that you then check.

Treat the output as a starting sheet, not a proof. State in the handover what came from the generator and what your own checking added. That honesty protects the relationship more than any claim about how the rows were produced.

Moving up a level buys more generation room and a wider export shape, not more certainty about any single row. Budget for the review pass as the true cost. If your clients accept store-shaped catalogue exports, the wider scope pays off; if they want verified contacts, no tier solves that for you.

The free trial credits let you size one genuine batch before you choose. Run your most demanding sample through, export it, and check the file by hand as a client would. That test answers the tier question faster than comparing feature lists on the pricing page.