T2 reviewed
Published entry path
Shown only where the public pricing source supports it.
R3 SMB verification ops
Run SMB checks without turning hiring into document sprawl
PRAMAAN helps 5-50 person firms manage candidate, contractor, and vendor verification status with purpose, consent, review states, and support routes before broader plan/API claims are made.
R3 SMBT2 reviewedConsent-firstDecision supportNo automatic hiringNo raw-ID forwarding
Sample preview — no real PII
Candidate and vendor dashboard
Candidate
A*** M. · Sales
Consent receivedContractor
T*** S. · Technician
Manual reviewVendor
GSTIN ending 8XX
Signal readyPayment
Invoice pending
GST invoice supportedVerification supports decisions; it is not an automatic hiring decision.
R3
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Plan volume, support, API, and refund terms follow source-of-truth pricing or signed scope.
Audience stakes
Small businesses need verification discipline without pretending PRAMAAN guarantees hiring outcomes, legal clearance, or plan entitlements.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Ops run on screenshots
Small teams collect Aadhaar, PAN, resumes, and references in chat before consent and retention are clear.
Hiring needs review states
Candidates, vendors, and contractors need pending, review-needed, completed, disputed, and expired states.
Client proof needs boundaries
Client or procurement proof should use scoped evidence, not raw report forwarding.
Specialized module
SMB hiring and vendor workflow
R3 SMB operations playbook for candidate, contractor, and vendor verification with consent evidence and bounded plan claims.
SMB teams
Operations owners
Compliance reviewers
People being verified
Who this is for
Role-based trust, not one generic buyer.
Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.
Founder / COO
Move fast without creating privacy debt
PRAMAAN view: Consent status, check state, and billing/source-of-truth plan route.
HR or ops owner
Track candidates, vendors, and contractors
PRAMAAN view: Queue, review-needed states, expiry, and support escalation.
Candidate or vendor
Purpose, correction, and visibility
PRAMAAN view: Consent notice, report access, correction, DSR, support, and grievance routes.
Workflow
Request, consent, signal, review, and audit stay connected.
The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.
- Scope1
Choose the business purpose
Candidate, contractor, or vendor checks start with a purpose and requester role.
- Consent2
Subject sees the request
The person can consent, decline, correct, or ask support before processing.
- Review3
Ops sees bounded status
The dashboard shows permitted signals, status, expiry, and manual-review context.
- Decide4
Business policy stays human
PRAMAAN supports the decision; it does not automatically hire, reject, or certify legal suitability.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Candidate and vendor queue
Track invited, consented, review-needed, completed, and expired checks.
Consent evidence
Purpose, requester, selected check, timestamp, and support path remain attached.
Plan-scoped volume
Included volume and support terms come from the current pricing source or signed business scope.
API and bulk by scope
API, webhooks, CSV, and migration/backfill are labelled only where supported and agreed.
No automatic hiring
Verification is decision support, not a guarantee, certification, or statutory-process replacement.
Raw-ID minimization
Share status and scoped evidence instead of forwarding raw documents to clients.
Consent and DPDP
Consent and DPDP-native workflow
Each page keeps consent, purpose, minimization, DSR, support, and grievance paths visible.
Explicit consent before checks
Purpose shown before processing
Operational views prefer signals over raw documents
DSR, correction, support, and grievance routes visible
Sample preview
Candidate and vendor dashboard
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Candidate and vendor dashboard
Candidate
A*** M. · Sales
Consent receivedContractor
T*** S. · Technician
Manual reviewVendor
GSTIN ending 8XX
Signal readyPayment
Invoice pending
GST invoice supportedVerification supports decisions; it is not an automatic hiring decision.
Use cases
Specific workflows a buyer can recognize.
Primary workflow
Use PRAMAAN for the highest-frequency verification path.
Less document forwarding and clearer consent.
Exception review
Route amber, incomplete, or disputed signals to a human reviewer.
Better decisions without automatic rejection.
Renewal or expiry
Refresh signals when a badge, pass, or role context becomes stale.
No reliance on old screenshots.
Responsible use
Responsible employment decisioning
PRAMAAN provides verification signals for human review, not automatic hiring outcomes, legal clearance, or statutory-process replacement.
No legal-outcome guarantee
No automatic hire/reject claim
No hard-coded plan volume unless source-backed
Adverse signals need review
Cancellation/refund follows actual policy
SMB pricing posture
T2 reviewed
Use current pricing or signed scope for monthly price, included checks, cancellation, API access, and refund terms.
- No hard-coded included volume without approval
- No refund promise unless source-backed
- No API entitlement unless scoped
SMB verification ops
R3
SMB copy is reviewed before claiming included volumes, API access, customer outcomes, or migration/backfill support.
Integration and operations
SMB operating model
Start with dashboard verification and scope higher-volume rails deliberately.
Dashboard checks
Supported
Single public check
Supported
Bulk / CSV
By agreement
API / webhooks
By agreement
Legacy report backfill
By agreement
Proof and pilot clarity
SMB proof clarity
Talpro in-house use can be referenced as internal proof. Named customer logos, live counts, candidate-outcome metrics, and client claims require approval.
FAQ
SMB verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Start consent-first SMB verification
Run candidate, contractor, and vendor checks with plan-scoped volume, support, and review terms.