South African proof-first talent platform

Separate locked portals. One trusted hiring system.

TALLO separates candidate and client workflows into secure portal experiences. Candidates build proof-backed profiles. Clients browse anonymous approved talent. Operations access is restricted and not advertised publicly.

Candidate portal Client portal

Candidate privacy Client approval gate Consent before unlock Timestamped actions

01 Candidate App

Profile, assessments, proof, availability and intro consent.

02 Client App

Anonymous talent discovery, shortlisting and controlled introductions.

Shared secure core Users · Profiles · Assessments · Intros · Audit

Locked access model

Choose the correct portal.

Each area is intentionally separate. A candidate should not see the client workspace. A client should not see operational controls.

Candidate

I am looking for work

Build your anonymous TALLO profile, add proof signals, complete assessments and respond to introduction requests.

Open candidate portal Client

I am hiring

Browse approved anonymous candidates, review proof, request controlled intros and manage hiring activity.

Open client portal

Product model

Separate experiences. Shared source of truth.

The platform is not being built as one messy interface with role-specific tabs. It is being shaped as separate applications that share the same secure backend and database.

This keeps the product simple for non-technical users, easier to secure, easier to explain to clients, and stronger for future investor or acquisition due diligence.

Phase focus

Build only what creates trust, speed or commercial value.

Candidate protection

Candidate identity, contact details and exact location stay hidden until the controlled introduction process allows release.

Client approval

Employer accounts do not automatically browse the marketplace. Approval is part of the trust layer.

Operational control

Review, moderation and risk handling stay away from candidate and client workspaces.

Auditability

Important user and client actions are timestamped so the platform can defend commercial claims, disputes and compliance questions.

Lean workflows

No vanity screens. Every dashboard element must help a user make a better hiring decision or complete a required action.

Security first

Role checks belong on the server. The interface is only the front door, not the permission system.

Security posture

Built for sensitive hiring data from day one.

Separate portal routes

Candidate and client users enter through different locked workspaces.

Server-side role checks

Private API routes must validate identity, role, status and resource ownership.

Data minimisation

Clients see only anonymous candidate cards until the consent and declaration process is complete.

Action history

Profile changes, intro requests and prior-contact declarations are audit events.

Build roadmap

Foundation first. Power features later.

Portal separationClient command centreRBAC hardeningCandidate discoveryIntro pipelineAudit viewsJobs and applications