Internal Product Brief

JobsCrow Bench Sales Module

This page summarizes the proposed Bench Sales module so the development team can review scope, user flow, visibility rules, payment model, and suggested website placement without making it a primary public feature.

Purpose

Enable recruiting companies to create employer accounts, upload consultant resumes, pay per profile, and market candidate availability while keeping candidate contact details private.

Employer onboarding Resume uploads Privacy controls Pay per profile Search visibility

Core objective

  • Allow employers to register and manage candidate profiles.
  • Support fixed-cost or credit-based profile uploads.
  • Hide candidate contact details while exposing employer contact details for inquiries.
  • Create a structured flow for profile uploads, search discovery, and recruiter responses.

Functional scope

1

Employer account

Registration, email or phone verification, account dashboard, and upload management.

2

Candidate upload

Manual or bulk resume upload with mandatory fields such as name, skills, experience, education, and location.

3

Payments

Stripe or PayPal style integration with fixed cost per profile, invoices, and transaction history.

4

Search visibility

Searchable profiles with hidden candidate contact details and visible employer contact information.

Visibility rules

  • Candidate resume can be searchable.
  • Candidate direct contact details can be hidden.
  • Employer contact details should appear on inquiry view.
  • Search filters should include skills, experience, location, and availability.

Notifications

  • Successful upload alerts.
  • Payment transaction notifications.
  • Expiring or inactive profile reminders.
  • Renewal or balance alerts for upload credits or plans.

Roles

  • Employer: register, upload, manage, pay.
  • Admin: monitor employers, transactions, and disputes.
  • Future option: job seeker visibility controls if enabled later.

Tech recommendation

  • Frontend: React-based interface integrated into JobsCrow.
  • Backend: Node.js or Django API services.
  • Database: PostgreSQL or MongoDB for profiles and transactions.
  • Authentication: OAuth 2.0 or JWT.
  • Hosting: AWS or Azure.

Non-functional needs

  • Data encryption for resumes and employer details.
  • Fast profile indexing and search retrieval.
  • Scalable upload and search architecture.
  • Usable dashboard for profile and payment management.
  • Privacy and compliance readiness.

Website placement recommendation

This should not appear as a primary JobsCrow feature. The better website approach is a low-visibility recruiter-focused landing page used mainly for direct outreach and sharing with recruiting firms.

  • Do not place in homepage hero or main feature blocks.
  • Use a dedicated hidden page such as /recruiter-vip or /bench-sales-access.
  • Optionally add a low-profile footer link for recruiter audiences only.
  • Send LinkedIn prospects directly to that landing page.
Recommended label for the footer: Recruiter VIP Access. This sounds selective, professional, and does not reposition the whole website around bench sales.

Suggested footer link structure

Below is the recommended footer structure to share with the development team. The recruiter link is present, but kept secondary.

  • Recommended footer URL: /recruiter-vip
  • Alternative URLs: /recruiter-partner-access, /bench-sales-access, /early-access/recruiters
  • Do not use a homepage CTA button for this feature.
  • Keep the footer wording neutral and premium, not overly sales-heavy.