Salesforce Administrator Portfolio

UpForJobs

A full Salesforce CRM implementation for a Dubai-based AI talent platform — candidate management, client engagements, UpPaq service packages, and placement tracking across the MENA region.

Explore the build View process
Click a segment to view screenshot
ORG SCREENSHOTS CANDIDATES MATCHER PIPELINE DASHBOARD
● Candidates list view ● Talent matcher flow ● Engagements pipeline ● Executive dashboard
Candidate management Talent Matcher Flow UpPaq service packages Engagement pipeline MENA region tracking Custom objects Sales Cloud Screen Flow Executive dashboard Sprint placement Dubai-based client Candidate management Talent Matcher Flow UpPaq service packages Engagement pipeline MENA region tracking Custom objects Sales Cloud Screen Flow Executive dashboard Sprint placement Dubai-based client
Project overview

Built for the talent platform

UpForJobs Recruitment CRM is a Salesforce implementation built for a Dubai-based AI freelance talent marketplace — managing the full cycle from candidate onboarding and client briefing through to sprint placement and post-engagement reporting across the MENA region.

"This was a consulting engagement — I diagnosed the operational gap, designed the data model, and delivered a working CRM. This Salesforce org is a portfolio reproduction of that build, demonstrating the solution architecture I delivered for the client."

The build demonstrates custom object design, screen flow architecture, multi-object relationship mapping, executive dashboard creation, and the Talent Matcher — a guided briefing flow that creates Engagement records automatically.

Scope
Custom objectsCandidate__c · UpPaq__c · Engagement__c
Candidate fields11 custom fields
Talent Matcher screens3 — brief · package · confirm
Pipeline stages5 — Briefing to Cancelled
Sample data11 candidates · 5 clients · 5 engagements
Dashboard components4 components · 4 reports
Process Doc →
Data model

Object architecture

Four objects — three custom, one standard — plus the Engagement junction record that links every Candidate, Client, and UpPaq into a single trackable placement record auto-numbered ENG-0001 onwards.

Custom object
Candidate__c
Full freelancer roster. 11 fields capturing skills, sprint rates, availability status, and MENA location data. Multi-select skills picklist with 8 categories.
Skills__c Availability__c Sprint_Rate_USD__c MENA_Based__c LinkedIn_Profile__c Years_Experience__c
Custom object
UpPaq__c
Productised service packages — the UpForJobs equivalent of a product catalogue. Each UpPaq defines a sprint tier, duration, and included services.
Package_Name__c Sprint_Duration__c Package_Tier__c Included_Services__c Rate_USD__c
Custom object
Engagement__c
The core placement record. Links Candidate, Client Account, and UpPaq. Auto-numbered ENG-0001+. Tracks region, status, and revenue across the full 5-stage pipeline.
Candidate__c Account__c UpPaq__c Status__c Region__c Revenue__c
Standard object
Account · Contact
Client companies and onsite hiring contacts across the MENA region — UAE, KSA, Egypt, Qatar, Kuwait. Five client accounts each with primary contacts.
Account Name Industry Region Contact Name Title Email
Screen Flow
Talent Matcher
The guided briefing and matching tool — 3 screens walk the recruiter from client brief through UpPaq selection to confirmation. Auto-creates the Engagement record.
Client Brief screen UpPaq Selection Confirmation Auto-create Engagement
Dashboard
MENA Pipeline
Executive dashboard embedded as the app home page. Active sprint value, revenue by client, engagements by region donut, and candidate availability breakdown.
$31k pipeline metric Revenue by Client UAE vs KSA donut Availability split
Flow design

The Talent Matcher

The Talent Matcher Screen Flow is the operational centrepiece of the UpForJobs CRM — it replaces manual Engagement record creation with a guided 3-screen briefing process that enforces data completeness and creates the correct object relationships automatically.

A separate record-triggered Flow fires when an Engagement reaches Completed status, auto-creating a follow-up task for the recruiter to conduct a post-sprint review with the client.

01
Talent Matcher Screen Flow
Screen Flow — launched from UpForJobs app nav
Screen 1 — Client Brief: select client Account, target region, and required skills
Screen 2 — UpPaq Selection: choose service package and sprint duration
Screen 3 — Confirmation summary before submission
On submit: auto-creates Engagement__c with Status = Briefing, linked to Account and UpPaq
02
Completed Engagement — Post-Sprint Review
Record-Triggered Flow — Engagement Status = Completed
Triggers when Engagement Status changes to Completed
Creates Task: "Schedule post-sprint review with client" assigned to Engagement Owner
Due 5 business days from completion — ensures follow-up without manual reminders
Sample data

The numbers

Data built to demonstrate a realistic MENA-region talent operation — candidates with varied skills and availability, clients across the Gulf, and a live pipeline of engagements at every stage.

11
Candidate records
5
MENA client accounts
5
Active engagements
5
Pipeline stages
3
UpPaq packages
8
Skills categories
$31k
Active pipeline value
4
Dashboard components
Security model

Permission sets

UFJ Recruiter
Placement Team
R C E D
Candidates
Engagements
UpPaqs
Accounts
Tasks
UFJ Manager
Senior Access
R C E D
Candidates
Engagements
UpPaqs
Accounts
Tasks
UFJ Admin
Full Access
R C E D
Candidates
Engagements
UpPaqs
Accounts
Tasks
Build process

How it was built

Built as a consulting reproduction — the same architecture delivered to UpForJobs, rebuilt in a Developer Edition org for portfolio demonstration. The data model reflects real MENA recruitment operations for an AI talent platform.

Phase 1
Object and field design
Created the UpForJobs Lightning app. Built three custom objects: Candidate__c (11 fields including multi-select skills and availability picklist), UpPaq__c (service package catalogue), and Engagement__c (the placement record linking all three objects).
Phase 2
Relationship mapping
Lookup relationships from Engagement to Candidate, Account, and UpPaq. Auto-number field on Engagement (ENG-{0000}) for clean record identification. Validation rules on required fields at each stage transition.
Phase 3
Talent Matcher flow
Built the 3-screen Screen Flow — Client Brief, UpPaq Selection, and Confirmation. Each screen validated before progression. On submit: auto-creates Engagement record with correct lookups, status set to Briefing.
Phase 4
Data and pipeline
Created 11 candidate records across skills categories (LLMs, MLOps, UI/UX, Data Engineering). Five MENA client accounts — UAE and KSA weighted. Five Engagement records across all pipeline stages to demonstrate full lifecycle.
Phase 5
Dashboard
Four-component executive dashboard: Active Sprints metric ($31k), Revenue by Client bar chart, Active Engagements by Region donut (UAE vs KSA), and Candidate Availability breakdown. Pinned as UpForJobs app home page.
Architectural decisions

Key design notes

Custom Engagement over standard Opportunity
Salesforce's standard Opportunity object was considered for placement tracking. Rejected in favour of a custom Engagement__c — the UpForJobs business model is sprint-based, not deal-based. Custom stages (Briefing → Matching → Active Sprint) reflect the actual operation more accurately than a generic sales pipeline.
UpPaq as a separate object
Service packages could have been a picklist on the Engagement. Built as a separate UpPaq__c object instead — enabling rate fields, duration tracking, and the ability to update package details without editing every engagement record. Demonstrates consultative data modelling over the path of least resistance.
Portfolio reproduction framing
This build is explicitly a portfolio reproduction of a real consulting engagement. The data is anonymised, the company name is fictional, but the architecture and logic mirror what was delivered. This framing demonstrates both real-world application and the ability to translate a client engagement into a demonstrable portfolio artefact.