If you are considering the paid beta, you need to check that its access period, capacity and development stage suit the work you plan to do. OppAlerts is sold as a paid beta running to December 31, 2027. One payment, no automatic renewal, and it includes 30 active campaigns, 10,000 tracked calls a week and six weekly calls with Ben.
Beta, in practical terms
The product is under active development and people are doing real work in it while that happens. Accept both halves of that deliberately, because finding out later is worse.
Parts of it are unfinished. Features will change during the service period, reports will change shape, and there will be interruptions. Take the API and MCP server: they read data and run searches, and they cannot yet create or change a campaign.
In return you get the person building it. The published description includes weekly calls with Ben, for training and for feedback on how you are using the product. That is unusual and it is the real substance of the arrangement. A request that makes sense gets discussed with the person who would implement it.
Who this suits
A team that needs the research reports now and can work around a product still being built. Somebody has to be free to actually read the reports each week.
It does not suit anyone who needs a settled feature set, uptime commitments or a security review process. It does not suit work where the report formats have to stay put. All reasonable requirements. This is the wrong stage of a product to bring them to.
The commercial terms
One payment, service through December 31, 2027, no automatic renewal. When the period ends, access stops and nothing can be exported after that.
Reasonable exports are available while the service runs. Bulk exports of the Prospect Index or the News Index are not included, and the detailed limits are still being set.
Payments are non-refundable. Substantial collection costs start the moment a customer's campaigns start.
Establish these before you buy
Get these in writing, from whoever you buy this class of product from.
- What the payment includes, and what is charged separately.
- When the service period ends, and what happens to your access and your stored history that day.
- Whether anything renews automatically, and on what terms if you choose to continue.
- What the support route is, and what response to expect when a collection fails or a report is wrong.
The fourth one matters more in a beta than anywhere else. Things go wrong. You need to know what happens next.
Work out your usage first
Before committing, calculate the tracking volume your reporting actually needs. One credit is one tracked item, on one provider, on one day, so it is providers multiplied by days for each item. Pricing and inclusions runs several examples.
Teams overbuy frequency almost every time. Ask how often a number has to change before anybody would act on it. Buy that.
Before paying, review the beta terms against your planned usage and required capabilities. Make the decision based on the service available for that period.
See whether OppAlerts fits your work or what happens after the beta.