Bplan Document
Bplan Document
Legitimacy System
Executive Summary
Online job fraud is a rapidly growing threat. In fact, reported losses from online job
scams tripled between 2020 and 2023ftc.gov. Many of these scams are disguised as
fake job postings engineered to steal personal information or moneyindeed.com.
verifyHire is a proposed SaaS platform that authenticates job listings before they reach
applicants. By cross-checking each listing against company databases, official
websites and reputable sources, the platform would grant a “verified” seal only to
legitimate postings. This business plan outlines how verifyHire will fill a clear gap in the
recruiting market: protecting job seekers from fraud and restoring trust in online hiring.
Problem Statement
Fraudulent job ads are pervasive and damaging. In a recent Aerotek survey, 79% of
job-seekers reported encountering suspicious postings at least some of the
timeaerotek.com, and 64% encountered obvious fraud, with nearly 25% admitting
they’d been victimized by a scamaerotek.com. The Better Business Bureau estimates
that 14 million people are exposed to employment scams each year, leading to over
$2 billion in aggregate lossesbbbmarketplacetrust.org. FTC data mirror these trends:
reported consumer losses from job scams exceeded $220 million in just the first half of
2024ftc.gov. Most fake job ads aim to harvest personal data or money from
applicantsindeed.com, exploiting vulnerabilities in the hiring process. Even major job
sites admit that, despite screening measures, scammers can slip fraudulent listings onto
their boardsindeed.com. The result is wasted time, financial harm, and growing distrust
among job-seekers – a problem that demands a technical solution for verifying listing
authenticity before applicants are harmed.
Market Analysis
The addressable market includes online job platforms, staffing agencies, and
employers who post jobs. Globally there are thousands of job boards and recruitment
sites. Key segments include: (1) large publicly-listed boards (Indeed, LinkedIn,
ZipRecruiter), (2) vertical niche boards (engineering, healthcare, etc.), (3) corporate
career sites for mid-to-large companies, and (4) staffing/recruitment firms’ client
postings. With 1.3B+ professionals and 71M companies on LinkedIn
alonenews.linkedin.comnews.linkedin.com, and millions of job ads active at any time, the
scale is massive. The rise of remote and hybrid work (35% of U.S. employees in 2023
worked remotelypsmarketresearch.com) has expanded the geographic reach of listings
– any scammer worldwide can now target local applicants via global boards.
Major industry trends support our value proposition. Hiring tech is embracing AI and
automation, from résumé-screening to chatbotspsmarketresearch.com. Similarly,
verification via technology is an emerging area (for example, blockchain-based
recruitment solutions are cited as a growth segmentpsmarketresearch.com). Job
seekers are also demanding safer experiences: social media has seen groups exposing
“ghost jobs” and fake listings. Regulatory attention (new laws on ghost job
transparency) further underscores the market’s focus on honesty. In sum, the
combination of a large, growing recruitment market and rising demand for trust creates
a strong opportunity for verifyHire.
Business Model
verifyHire will operate on a B2B SaaS subscription basis, complemented by
transactional fees. Key revenue streams may include:
Ad/Referral Partnerships: With compliance and high trust, we could offer non-
intrusive advertising or earn referral fees from trusted career services.
This mixed model ensures diversified income. The primary focus will be enterprise
buyers (who value risk reduction) rather than direct job-seeker sales, making verifyHire
financially attractive as a B2B tool with B2C touches.
Marketing Strategy
To reach customers, verifyHire will pursue a two-pronged approach targeting
employers/boards and job-seekers:
Partnerships with Job Platforms: We will engage major job boards and HR software
providers to integrate verifyHire. Demonstrating that our technology reduces fraud
can make us a value-add or premium feature for them. Attending HR tech
conferences and networking with industry associations (SHRM, HR Tech, etc.) will
seed these collaborations.
Direct Sales to Enterprises: A small sales team will target large employers and
recruitment agencies that are likely to value brand protection. Case studies showing
reduced fraud can persuade HR departments and compliance officers to buy in.
Digital Content & Social Proof: We will publish expert content (blogs, webinars) on
avoiding job scams to build credibility. Outreach on LinkedIn and professional
forums highlighting our verification checks can attract job-seekers and HR
influencers alike. User testimonials and reported success (e.g. “This listing saved me
from a scam”) will be highlighted in marketing collateral.
Search/SEO and PR: Since job-seekers search tips on spotting scams, SEO content
on “verify job listing” can drive organic traffic to our service. Press releases when
we achieve milestones (seed funding, partnerships) will raise brand awareness.
This strategy combines inbound (content/SEO) and outbound (B2B sales, partnerships)
tactics. We will measure success by pilot program signups, conversion of free users to
paid integrations, and customer retention rates.
Operations Plan
Team & Development: We will build a lean core team initially: software engineers (to
develop the verification engine and UI), data specialists (to access and interpret public
company records), and a few compliance/legal advisors (to navigate data privacy).
Development will follow agile iterations, starting with an MVP that can vet listings from
Year 1: Focus on product development and pilot customers. Expenses ($500K) for
development, data acquisition, and marketing will exceed income. We project
minimal revenue (~$50K) from a handful of pilot clients (covering some pilot costs).
Year 3: Expansion phase. If verifyHire captures more of the market, say 20 midsize-
to-large clients by year-end (totaling ~$1M in recurring revenue), with additional fee-
for-service income (~$200K), total revenue could reach $1.2M. Operating costs may
be ~$800K. This could result in a small profit.
Technological Risk: Verification algorithms may miss clever scams (false negatives)
or flag legitimate posts (false positives). Mitigation: Continuous machine learning
model training with real-world examples, plus human review for flagged cases. We
will iterate on logic (e.g. NLP detection of scammy language) to improve accuracy.
Market Adoption Risk: Major job boards or employers may be slow to adopt an
external verifier, preferring to manage fraud internally. Mitigation: We will target
early adopters in privacy/security-minded industries and emphasize partnerships.
Offering a white-label or integration option can lower adoption friction. A freemium
tier can let job-seekers drive viral demand (if users demand “verified” tags on
listings).
Competitive Risk: Large platforms (LinkedIn, Google Jobs) might build their own
verification features. Mitigation: verifyHire aims for flexibility by working with any
platform. Early patents on novel verification methods could create barriers. If a
competitor emerges, our advantage would be our specialized focus and first-mover
data.
Regulatory Risk: New laws could change job-posting rules. For example, states like
Kentucky and California are proposing (or passing) laws requiring employers to
disclose whether a posting is an actual vacancycongress.govcongress.gov. While
such regulation reflects the ghost-job problem, it could impose compliance burdens.
Mitigation: verifyHire can build in compliance tools (e.g. automated posting status
flags) as value-added features, helping clients meet legal requirements. We will
maintain close legal monitoring (for example, Ontario’s upcoming rules on
disclosurecongress.gov) and ensure our service adapts quickly.
Data Privacy/Security Risk: Handling job data and possibly personal data (like email
domains) involves privacy regulations (GDPR, etc.). Mitigation: We will use only
business-public data and anonymize user logs. Compliance frameworks (e.g. SOC
2) will guide our data policies.
Overall, we will manage risk by technical diligence, legal awareness, and by aligning our
value proposition with both market demand and regulatory trends. In fact, having clear
verification can help companies avoid fines or reputational damage, turning a potential
regulatory risk into an opportunity for our service.
Conclusion
The verifyHire platform addresses a pressing and growing need in the recruitment
industry. By preventing fake job postings from harming candidates, we create value for
both job-seekers and employers. The business opportunity is supported by large
market size and fast growth in hiring
technologyfortunebusinessinsights.compsmarketresearch.com. Our solution leverages
References
Federal Trade Commission (2024). New FTC Data Show Skyrocketing Consumer
Reports About Game-Like Online Job Scams (Press Release, Dec 12, 2024).
Aerotek (2023). Job Scams on the Rise: How to Spot and Avoid Fraud in Your Job
Search.
BBB Institute for Marketplace Trust (2020). Protecting Yourself from Employment
Scams.
P&S Intelligence (2024). U.S. Online Recruitment Services Market Size & Forecast.
Indeed (2025). 17 Common Job Scams and How to Protect Yourself (Career Advice
article).
Congressional Research Service (2024). “Ghost” Job Postings (Issue Brief, Library
of Congress).
Primary goal: Accurately verify job postings at scale and surface a clear, portable
trust signal (“Verified” badge + machine‑readable assertion).
False positive rate for legitimate posts and appeal cycle time.
3. User Personas
Job‑seeker: Needs quick, trustworthy signals; prefers simple badges and clear
reasons.
Recruiter/TA manager: Wants low‑friction bulk verification, audit logs for compliance,
and SLA guarantees.
Job board/platform PM: Seeks fraud reduction, stronger brand trust, minimal latency
impact, and easy API/webhook integration.
4. User Stories
As a job‑seeker, I want to see a clear badge and reasons so I can decide safely in
seconds.
As a platform PM, I want webhooks to update listing states and detailed error codes
when checks fail.
As compliance, I want immutable evidence for audits, with least‑privilege access and
redaction.
Target latency: under 5s for 80% of posts, with async deep checks for the
remainder.
Data: Prefer authoritative sources; fall back to heuristics with confidence scores.
Evidence graph: Structured store of entities (employer, domain, job post, contact
channels) and edges with provenance.
Integration SDKs: REST, GraphQL, and client libraries; webhooks for state changes.
Data Flow
1) Ingest posting payload → normalize schema.
2) Run deterministic checks (domain, DNS, WHOIS, MX, DMARC, SSL, official links).
3) Query authoritative registries and knowledge sources.
4) Run ML models: language cues, anomaly detection, contact mismatch risk, salary
plausibility.
5) Aggregate signals into a confidence score with explainable reasons.
6) Decide: Verified, Flagged, or Rejected + required remediation.
7) Persist evidence and publish signed badge + webhook.
Technical Stack
Backend: TypeScript/Node or Kotlin, gRPC/REST, OpenAPI; message bus
(Kafka/NATS).
Security: mTLS intra‑service, OIDC for auth, KMS/HSM for keys, Vault for secrets.
Site integrity: TLS certificate CN/SAN match, HSTS, canonical employer links.
Job data consistency: Role, location, salary range coherence with employer history
and industry baselines.
Graph features: Distance to known trusted entities, shared infrastructure with known
bad actors.
For flags: precise remediation advice, e.g., “Publish jobs via careers.example.com or
add a verified TXT record.”
Public keys published via a JWKS endpoint; short‑lived tokens to prevent replay.
Optional on‑page widget that validates the JWS against our JWKS in the client.
API Design
Core Endpoints
POST /v1/jobs: Create or submit a job for verification.
SOC 2 Type II roadmap; ISO 27001 alignment; DPA and SCCs for EU transfers.
Encryption in transit and at rest; key rotation policies; comprehensive logging with
retention tiers.
Platform dashboard: SLA graphs, latency heatmaps, top failure reasons, and
signature health.
Competitive Landscape
Point‑in‑time screening by major boards vs. continuous, cross‑source verification.
Our moat: evidence graph, signed assertions, and platform‑friendly latency + UX.
Pilot programs with measurable scam reduction KPIs and co‑marketing case studies.
Growth: $2,000/mo + $0.20 per verification, SSO, priority webhooks, 99.9% SLA.
Gross margin targets >75% by Year 3 via model efficiency and caching of evidence.
CAC and payback modeled per segment; partner channel reduces blended CAC.
Q2: Evidence graph v1, badge service, and first ATS integration.
Q4: Signed assertions v2, enterprise features, and SOC 2 audit prep.
Accessibility
WCAG 2.2 AA for all surfaces. Keyboard‑first flows and screen reader labels.
Feature attribution for model decisions; drift and data quality monitors.
FAQ
What if a legitimate startup has no registry footprint? We support alternative proofs
like DNS TXT verification and founder email verification.
Can platforms hide unverified jobs? We provide policy hooks; platforms decide
enforcement levels.
Glossary
Evidence graph, assertion, confidence, precision/recall, DMARC, DKIM, JWKS.
Extended Whitepaper
1. Background and Context
Online recruitment has evolved through three eras: classifieds to portals, portals to
aggregators, and aggregators to platform ecosystems. Each transition scaled volume
and reach, but also broadened the attack surface for scammers. Today’s threat actors
operate like growth hackers, A/B‑testing posts, rotating infrastructure, and exploiting
platform loopholes. A trust layer is overdue.
Employer: Brand damage, candidate trust erosion, support burden, legal exposure.
Provenance: Each edge carries source, timestamp, hash, and confidence. Hash
chains allow audit trails.
5. Model Development
Datasets: Curated positive set from verified corporate feeds; negative set from
reported scams, honeypots, and platform takedowns.
6. Human‑in‑the‑Loop Protocols
Triage levels: Auto‑clear, reviewer‑required, auto‑reject with appeal.
Quality: Golden set rotation, inter‑rater agreement (Cohen’s κ), reviewer dashboards.
Data protection: GDPR, CCPA/CPRA, DPDP (India). Our approach: minimal data, DPA,
SCCs.
Phase APAC: MCA (India), ACRA (Singapore), ASIC (Australia), NZBN (New Zealand).
9. Partner Integrations
ATS: Greenhouse, Lever, Workday, SAP SuccessFactors, Taleo via APIs and
webhooks.
Job boards: Indeed, ZipRecruiter, LinkedIn via partner programs where available.
Parallelism: Fan‑out evidence fetch with bounded concurrency; circuit breakers per
connector.
Abuse: Rate limiting, partner‑key reputations, anomaly detection for bulk submits.
Sensitivity analysis: Price vs margin under low/high review rates and connector
pricing.
Success: 60%+ reduction in scam complaints, ≤2% false positive rate, p95 latency
≤8s.
Incident response: Transparent status page, RCA within 5 business days for Sev‑1.
Not verified: Gray badge, tooltip “Publisher has not verified this posting.”
2. Copy Guidelines
Avoid implying job quality or pay; focus solely on authenticity.
3. Accessibility Details
SVGs with descriptive titles, focus states, and high‑contrast modes.
4. Flows
Employer onboarding: DNS TXT challenge, OAuth app install, initial backfill
verification.
Appeal flow: Submit evidence, track status, receive decision with rationale.
3. Risks
Platform incumbents replicating core checks; mitigation via partnerships, patents,
and data moat.
Detailed Financials
1. 36‑Month P&L Sketch
Revenue: Subscriptions, usage fees, enterprise add‑ons.
EBITDA trajectory and cash runway under base and bear cases.
2. Cohort Economics
Logos by segment, ARPA, expansion, churn, NRR targets.
Appendices
A. Sample JSON Assertion
{
"iss": "https://api.verifyhire.example",
"sub": "job:12345",
"employer": "employer:67890",
"verified_at": "2025-10-01T12:34:56Z",
"exp": 1738497600,
"checks_passed": ["dns_domain_match", "registry_match", "contact_channel_corp
orate"],
"confidence": 0.94,
"evidence_hash": "sha256-..."
}
{
"event": "job.verified",
"id": "evt_abc123",
"job_id": "12345",
"status": "verified",
"confidence": 0.92,
"reasons": ["domain_alignment", "registry_record"],
"occurred_at": "2025-10-01T12:35:01Z"
}
Logs: 30 days hot, 365 days cold for audit trail with legal holds.
E. Metrics Definitions
Scam exposure rate: Complaints per 10k views pre/post.