Start free with JobSpring
Internal account pricing preview

Choose how much of your search can run on auto fill.

This is the logged-in jobseeker pricing concept for the Chrome extension. The page is intentionally simpler than the public marketing surfaces and focuses on monthly limits, extension value, and what happens when usage runs out.

Current plan: Free 12 of 20 auto fills used this month • resets May 1
Chrome extension connected Saved answers synced Queue pauses automatically at your plan limit
Plans

Simple monthly tiers for extension-driven applications.

The plan structure is based on assisted submission count, not abstract credits. Each tier answers a clearer search habit: occasional, steady, or aggressive monthly job discovery.

Current plan
Free

For jobseekers who want to test the extension before they make it part of a weekly routine.

$0 per month

Keeps the barrier low while still giving the user a real monthly cap and enough usage to understand how the workflow behaves.

  • 20 auto fills per month
  • Saved answers library
  • Standard board support
  • Manual review before send
Best for testing the extension
Plus

For active searchers who apply every week and want enough volume to keep momentum without hitting the ceiling too early.

$12 per month

A practical step up for regular search behavior, with more monthly extension usage and less interruption once good-fit roles start appearing in clusters.

  • 80 auto fills per month
  • Queue and retry handling
  • Faster answer reuse
  • Priority board updates
Good fit for weekly applications
Pro

For heavier search cycles, relocation pushes, or candidates managing multiple target roles at the same time.

$29 per month

The higher-capacity plan for jobseekers who want the extension to handle a larger monthly pipeline without constantly managing the cap.

  • 250 auto fills per month
  • Advanced queue controls
  • Deeper board coverage
  • Usage analytics and priority support
For aggressive monthly search volume
Compare

What actually changes by tier.

The main variable is monthly auto-fill volume. Everything else should stay easy to understand from a logged-in account point of view.

Feature Free Plus Pro
Monthly auto fills 20 80 250
Saved answers library Included Included Included
Queue and retry handling Basic Improved Advanced
Board support refreshes Standard Priority Priority
Usage visibility Monthly count Monthly count + queue state Detailed analytics
FAQ

Auto apply pricing questions jobseekers will ask first.

What counts as one auto fill?
One successful extension-assisted submission counts as one auto fill. If the extension starts a flow but the application is not actually sent, it should not consume the quota in the final product behavior.
What happens when I hit my monthly limit?
The queue should stop sending additional applications until the cycle resets or the user upgrades. The rest of the account still works, but extension automation pauses at the plan cap.
Do unused auto fills roll over?
This concept assumes they do not roll over. The value proposition is steady monthly capacity, not storing a growing balance of credits that becomes harder to understand over time.
Can I use a paid plan without the Chrome extension installed?
No. The paid value is tied directly to extension-driven application flow. Without the extension installed and connected, the upgrade would not unlock the main benefit.
Can I switch plans mid-cycle?
Yes. The cleanest behavior is to let users upgrade immediately when they need more volume and let downgrades take effect on the next billing cycle so usage rules stay predictable.
Why not sell one-time packs instead of monthly tiers?
Monthly tiers are easier to understand inside the account. They match the way most jobseekers search in active cycles and keep the extension value tied to a recurring workflow instead of sporadic credit math.
Internal concept note

This route is intentionally quieter than the public marketing pages. It is meant to feel like a logged-in billing surface where the plan choice is secondary to the user’s actual question: how many extension-driven applications can I send this month, and what happens if I need more?