Comparing Pricing Tiers for Insider Transactions Research Tools

Free is generous right up to the moment you need it to behave like infrastructure.

Pricing pages are written to flatter everyone. Your job is to ignore the flattery and ask a duller, more useful question: what happens when you hit the limit at 08:47 on a busy Monday?

For tools used in insider-transactions research, that is the whole game. The work is episodic, but the spikes are severe. A quiet week can need a handful of searches. Then a cluster of director buys appears after a selloff, a company files late, a regulator updates disclosures, and suddenly you are running screens, checking historical patterns, exporting names, and writing notes against the clock. A plan that looks fine on average can fail exactly when it matters.

This article compares three common tiers, Free, Pro at 39 EUR / mois, and Pro at 129 EUR / mois, through that lens: limits, use cases, and rate limits. There is no live platform-specific data in the brief, so where a hard number is unavailable, I will say n/a rather than pretend a spreadsheet exists somewhere. That already puts us ahead of half the internet.

The real buying question is not price, it is tolerance for interruption

A free plan and a paid plan can offer the same interface, the same search box, and the same marketing adjectives. They are still different products if one can be exhausted during normal use.

For insider-filing research, the relevant constraints usually fall into four buckets:

1. Message or query caps, the total number of prompts, searches, or analyses you can run in a period.
2. Rate limits, how quickly you can make those requests before the system says, politely, no.
3. Feature access, whether you can export, automate, use APIs, or access better models.
4. Priority and reliability, whether the service degrades when everyone else has decided that this is also the exact minute they need it.

The mistake most buyers make is to focus on bucket one alone. They compare monthly allowances and stop there. That is understandable, because monthly allowances are easy to print on a pricing page. But rate limits and reliability are often the difference between a useful tool and a decorative one.

Why insider-transactions workflows are unusually sensitive to limits

Insider data is not consumed in a smooth, evenly distributed way. It arrives in bursts around market events, blackout windows ending, post-earnings disclosures, and sentiment shocks. A researcher may need almost nothing for days, then need a lot in one hour.

That matters because many plans are effectively designed for average use, while markets punish peak use. If your process depends on screening all fresh director buys in a region, cross-checking prior trading behaviour, and drafting a note before the open, a rate limit is not a minor inconvenience. It is a broken workflow.

A simple test: what happens on your busiest day?

Ignore your average week. Ask instead:

• How many searches or prompts do you need on the busiest day of the month?
• Do you need results interactively, or can you wait?
• Are you working alone, or is a team sharing the same account or quota?
• Is the output for curiosity, or for a client, publication, or trade idea?

If the answer to the last question is “for anything with consequences”, the free tier becomes harder to defend.

Free tier: good for sampling, weak as a habit

The free tier exists to let you test fit. Used that way, it is sensible. Used as a permanent operating plan for serious research, it usually becomes a negotiation with scarcity.

Best use cases for Free

Free is appropriate when your workflow is manual, occasional, and tolerant of interruption. Typical cases include:

• learning the interface
• checking a handful of companies each week
• doing one-off background research on an issuer or insider
• comparing whether the tool adds anything to your existing process
• student or hobbyist use where speed is not critical

For these users, a free plan can be genuinely useful. Not every tool needs to become a monthly line item. Sometimes the correct price is zero.

Where Free starts to fail

The free tier tends to break down when you need consistency. That can happen earlier than expected. Common failure points are:

Bursty query demand

A single research session can consume a surprising amount of quota. You start with a screen of recent buys, branch into two or three names, check historical transactions, ask for peer context, refine filters, then export or summarise. The session that felt “light” has suddenly become a chain of dependent requests.

Lower priority during busy periods

Many services reserve better throughput or model access for paying users. That is commercially rational. It is also inconvenient when your use case is time-sensitive. In practice, free users often bear the brunt of congestion.

No room for experimentation

Good research is iterative. You test assumptions, rerun screens, and ask follow-up questions. Tight limits discourage that. The result is not merely less convenience, but lower-quality work, because you stop exploring edge cases.

The hidden cost of Free

The hidden cost is time. If you are spending 20 to 30 extra minutes a week managing limits, waiting for resets, or splitting work across tools, the cash saving may be illusory. At modest professional billing rates, the arithmetic gets ugly quickly.

That does not mean everyone should upgrade. It means Free is best thought of as a trial with benefits, not as infrastructure.

Pro at 39 EUR / mois: the first serious tier

At 39 EUR / mois, the Pro plan is where many users stop dabbling and start building a repeatable process. The name suggests coding, but the practical distinction is broader: this is the tier for people who need the tool to show up when asked.

Why Pro is often the default recommendation

For a solo analyst, newsletter writer, active private investor, or small research shop, Pro is usually the most defensible choice. The monthly cost is low enough to be forgettable, but high enough that the provider can justify giving you meaningfully better limits and service than Free.

If your workflow includes any of the following, Pro is usually the minimum viable tier:

• daily or near-daily use
• recurring watchlists
• scheduled research around filings or earnings
• repeated comparative work across several issuers
• draft generation for notes, memos, or internal updates
• basic automation or API experimentation, if included by the product

The key phrase is “minimum viable”. Pro may not be luxurious, but it often moves you from scarcity to normality.

The rate-limit question is more important than the sticker price

At this tier, the ideal outcome is not infinite usage. It is enough headroom that you stop thinking about usage. If Pro gives you that, it is excellent value. If it still leaves you rationing prompts or API calls, then the nominal affordability is beside the point.

This is especially true for users who work in sessions. A plan can offer a respectable monthly allowance and still be frustrating if it throttles you heavily within a short window. For insider-filings work, session throughput matters.

Who should not choose Pro

Pro is a poor fit if you already know your workload is heavy, collaborative, or automation-led. Examples include:

• teams sharing research duties
• users running many parallel screens
• desks producing client-facing output on a schedule
• anyone relying on API access for production workflows
• users who routinely hit limits on lower paid plans elsewhere

In those cases, Pro can become a false economy. You save $80 versus Pro, then spend that saving in friction, retries, and workarounds.

Pro at 129 EUR / mois: expensive only if your time is free

The jump from 39 EUR / moisto 129 EUR / moislooks large because it is large. It is an extra $80 a month, or roughly 5.2 times the Pro price. That deserves scrutiny. It does not deserve reflexive dismissal.

What Pro is really for

Pro is not simply “more messages”. It is usually the tier for users who need one or more of the following:

• materially higher usage ceilings
• higher rate limits
• better concurrency
• access to stronger models or premium features
• more reliable service under load
• team or business-critical usage where downtime is costly

If Pro is the first serious tier, Pro is the first operational tier. It is for people who have stopped asking whether they use the tool enough, and started asking whether the tool can keep up.

The economics of Pro are often misread

A common objection is simple: “I cannot justify 129 EUR / moisa month.” Fair enough. But the correct comparison is not with zero, it is with the cost of failure.

If Pro saves an analyst one hour a month, it may already pay for itself. If it prevents one missed note, one delayed client update, or one broken automation run, the case strengthens. If it supports a multi-user workflow, the per-person cost can become quite ordinary.

There is also a subtler benefit. Better limits change behaviour. Users on constrained plans self-censor. They ask fewer follow-ups, test fewer hypotheses, and avoid broad screens because they fear wasting quota. A higher tier can improve output quality simply by removing that mental tax.

When Pro is overkill

Pro is overkill if your use is mostly exploratory, occasional, or manually paced. It is also overkill if the underlying product still lacks features you need. Paying more for the same bottleneck is not sophistication, it is loyalty to a problem.

A useful discipline is to ask whether your pain is caused by limits or by capability gaps. If the tool cannot do the task at all, moving from Pro to Pro will not rescue it. If it can do the task but keeps running out of road, Pro probably will.

Rate limits: the line item nobody reads and everybody feels

The phrase “rate limit” sounds technical enough to be ignored. That is a mistake. In practice, it governs whether a tool feels responsive, sluggish, or unusable.

What rate limits actually do

A rate limit caps how many requests you can make in a given period, for example per minute, hour, or day. It exists to protect system stability and prevent abuse. Entirely reasonable. Also entirely capable of ruining your morning.

For insider-transactions work, rate limits matter because tasks are often chained:

1. pull recent filings
2. filter by transaction type and market cap
3. inspect insider history
4. compare with peers
5. generate a summary
6. export or share results

Each step can consume one or more requests. If the chain stalls halfway through, the workflow is broken even if your monthly quota remains healthy.

Interactive users and API users feel limits differently

Interactive users notice latency and lockouts. API users notice failed jobs, retries, and queue management. Both care about the same underlying thing: can the system absorb bursts?

For API or automation use, low rate limits are particularly dangerous because they create hidden engineering work. You end up adding retry logic, backoff policies, caching, and monitoring simply to compensate for a plan that was too small. Sometimes that is still worth it. More often, it is a sign you bought the wrong tier.

A practical framework for judging rate limits

Because the brief does not provide platform-specific limit numbers, the right approach is qualitative:

Choose Free if:

• you can tolerate pauses and resets
• your work is mostly ad hoc
• you do not automate anything
• missing a window is annoying, not costly

Choose Pro if:

• you need regular access with modest bursts
• you work alone or nearly alone
• you want enough throughput to finish a session without babysitting usage
• you may experiment with automation, but not run production systems

Choose Pro if:

• you need sustained bursts or higher concurrency
• your work is deadline-driven
• multiple users or processes depend on the account
• rate-limit failures would create downstream costs

Matching plan to use case

A pricing comparison becomes clearer when attached to actual jobs rather than abstract user labels.

Casual investor or student researcher

This user checks a few names, reads around a filing, and occasionally asks broader market questions. They are not publishing on a schedule and do not need automation.

Best fit: Free
Upgrade trigger: repeated frustration with caps, or desire for regular screening

The key is honesty. If you use the tool twice a month, paying for Pro is an expensive way to feel professional.

Active private investor

This user maintains watchlists, screens for insider buying after drawdowns, and revisits names frequently. They want speed, but not necessarily industrial-scale throughput.

Best fit: Pro
Upgrade trigger: sustained daily use, frequent limit hits, or need for premium features

This is probably the largest group for whom Pro is the sweet spot.

Newsletter writer, independent analyst, or content publisher

This user has deadlines. They may need to turn filings into notes quickly, compare multiple cases, and produce publishable summaries. Their usage is bursty but meaningful.

Best fit: Pro or Pro
Decision rule: choose Pro if publication cadence or audience expectations make delays expensive

The difference here is not technical sophistication. It is whether the workflow has consequences.

Small team or research desk

Several people may query the system, or one person may run heavier processes on behalf of others. Shared usage creates invisible contention. What felt ample for one user becomes cramped for three.

Best fit: Pro
Downgrade case: only if usage is genuinely light and non-overlapping

Teams routinely underestimate the pain of shared limits. Computers are less sentimental than colleagues.

Pro building automations or internal tools

If the product offers API access or automation features, the choice should be driven by throughput and reliability, not by the word “Pro” in the plan name. Marketing departments are not a standards body.

Best fit: Pro for prototyping, Pro for production-like use
Upgrade trigger: rate-limit handling becomes a project in itself

If your code spends more time apologising for the plan than doing the job, you have your answer.

How to decide in 15 minutes

You do not need a procurement committee. You need a short audit.

Step 1: map your busiest workflow

Write down the highest-intensity task you perform or expect to perform. For example:

• scan all fresh insider buys this morning
• investigate five names
• compare each against prior insider activity
• draft a note and share it

If that workflow feels fragile on Free, it is.

Step 2: estimate the cost of interruption

What happens if you hit a cap midway through?

• nothing important, continue later
• mild annoyance, but recoverable
• delayed note or missed opportunity
• broken client or team process

Map that answer to the plan. The more expensive the interruption, the less sensible a cheap tier becomes.

Step 3: separate experimentation from operation

If you are still evaluating fit, start low. If the tool is already in your process, stop pretending evaluation is still the phase. Many users stay on low tiers months after the decision has effectively been made.

Step 4: review after one month

The right plan is not a moral identity. Start with the lowest tier that plausibly supports your workflow, then review actual pain points after a month. Upgrade if you are managing limits. Downgrade if you are paying for headroom you never touch.

That is the adult answer. It lacks drama, but then so does good risk control.

So which one should you choose?

For most readers, the answer is straightforward.

Choose Free if you are testing fit

Use it to learn the product, run occasional screens, and decide whether it belongs in your stack. Expect limits. That is the bargain.

Choose Pro at 39 EUR / moisif you want a real working plan

This is the default recommendation for solo professionals, active investors, and independent researchers. It is cheap enough to try, serious enough to matter, and likely to remove the worst forms of friction.

Choose Pro at 129 EUR / moisif the tool is part of your operating system

If you publish, automate, collaborate, or work under deadlines, Pro is often the correct choice. Not because expensive means better, but because interruption has a price and someone will pay it. Better that it be the subscription.

The open question, and the one worth checking before you commit, is not whether the higher tier offers “more”. It is whether it offers enough additional throughput and reliability to change your actual workflow. If it does, the next step is simple: run your busiest real task on the lowest plausible tier for one week, log every limit hit or slowdown, and upgrade only if the evidence says the cheap plan is making you work for it.

---

Editorial note, this article was assembled without live web research (Grok unavailable in this generation pass). Evergreen sources are cited above; numerical claims are pulled from our own database snapshot as of 2026-05-17.

Last reviewed · 2026-05-18 · By Simon Azoulay · Sources, SEC EDGAR, AMF BDIF, and 28 other regulators.