Every proposed plan includes all six public-profile tools. Upgrade for more successful lookups, longer snapshot history, structured exports, and collaborative review—not to unlock basic clarity.
Start with the sample workspace, then choose the amount of repeat research your workflow needs. Final prices and limits remain proposed until a compliant live provider and billing system are connected.
forever
Explore every research view before deciding whether saved history is useful.
per month
Build dated baselines, revisit public profiles, and review changes in one place.
per month
Organize recurring creator, client, or competitor research with a small team.
Concept pricing only. Taxes, renewal terms, provider-dependent limits, cancellation steps, and any refund policy will be published before checkout is enabled.
No Instagram passwordAccount credentials are outside the product model.
Successful results countFailed or unsupported requests should not use an allowance.
Public profiles onlyPrivate accounts and restricted content remain unavailable.
The tools stay the same across plans. Capacity, history, collaboration, and support scale with the workflow.
| Capability | Free | Researcher | Studio |
|---|---|---|---|
| Tool access | All six samples | All six tools | All six tools |
| Lookup allowance | 3 sample previews/day | 100 successful/month | 500 successful/month |
| Snapshot history | Current sample | 90 days | One year |
| Change comparison | Sample view | Included | Included |
| CSV export | Sample format | Supported fields | Shared exports |
| Team seats | — | One | Five proposed |
| Support | Help center | Priority |
Use the sample interface when you are still deciding which follower or profile question matters.
Use dated history when you revisit the same public profiles after posts, launches, or campaigns.
Use groups and seats when several people review creators, clients, or competitors together.
These answers describe the proposed model. Final commercial terms will be published before anyone can pay.
A proposed allowance would count only when the provider returns a supported public result. Invalid usernames, private accounts, and failed provider requests should not consume usage.
No. The current interface uses clearly labeled sample data. The plan structure describes a future workflow after a compliant provider is connected.
Any paid launch should include a clear self-service cancellation path and show renewal timing before purchase. Final terms will control once checkout is available.
Provider cost, supported coverage, operational capacity, and compliance review must be confirmed before final limits and prices can be promised.
Help shape the launch model. Tell us which tools, history window, and team workflow would actually be useful.
Contact iFollowTracker