Salesforce Administrator · Service Cloud Consultant · Platform App Builder — building tools that give teams real visibility into their org health.
Surfaces technical debt by type, severity, risk score, and ownership — all in one place.
Formula-based risk scoring bubbles the highest-impact items to the top automatically.
Repeatable process for documenting risks, remediation steps, status, and admin ownership.
Screen Flows replace manual tracking and standardize how debt findings are captured and assigned.
Built entirely in a Developer Edition org (NexGen Living). Custom objects, formula-based risk scoring, Screen Flows, Lightning App Builder, and reports & dashboards — end to end.
Organized public report folder with five targeted reports covering type, severity, new items, fixed items, and critical open issues.
Multi-component dashboard showing risk by type and severity, fixed items this month, critical open items, and a live debt register.
Lightning App Builder page combining live dashboard charts, a "Highest Risk Items" list component, drill-through navigation, and an embedded Screen Flow for creating new technical debt records in a single admin workspace.
Custom object record with Age Score, Severity Score, Business Impact Score, and Final Risk Score formula fields — plus assigned admin, recommended fix, and status tracking.
Filtered list view sorted by Risk Score descending, showing only Active Issues — TDI-0014 scores 100 (Critical), making triage instant.
To mirror what a real governance team does in a weekly review meeting — but automatically — I built a
Schedulable
Apex class that runs nightly at 2 AM. It queries all Technical Debt Items where the Target Resolution Date
has passed and Status is still "New" or "In Progress," then bumps Severity up one level (Low → Medium →
High → Critical) and appends a timestamped note to the Description. A single bulk-safe DML call handles
any number of records in one transaction.
To improve data quality and platform governance, I implemented a custom Apex validation framework that prevents duplicate Technical Debt Item records from being created. The solution uses a custom Apex class and before-insert trigger to evaluate incoming records against existing open items — stopping duplicates at the transaction level with a clear user-facing error message.
NexGen Living is a PropTech startup concept I designed a complete Salesforce architecture for from scratch — a two-sided intergenerational housing marketplace that pairs senior homeowners with a spare room with young professionals or students who need affordable housing. The architecture spans seven Salesforce clouds, ten custom objects, a declarative matchmaking engine, and cross-cloud revenue enforcement — all built and documented in a single Developer Edition org with no code beyond one Apex duplicate-prevention class.
Queries both renter and senior pools nightly, scores compatibility across 8 criteria using formula fields, auto-creates ranked Match_Proposal__c records — no Apex.
Smart home sensors publish Platform Events. A Platform Event-Triggered Flow converts the payload into a Priority Critical Case in real time — rare on resumes.
An SLA breach flips a checkbox. A Record-Triggered Flow calculates the penalty, creates a Credit_Memo__c, and injects a negative line item into the next open invoice. Cross-cloud, declarative.
Haven (seniors), Base (renters), and Partner Hub (universities/brokers) — all from one org using profiles, permission sets, and sharing rules. No code deployment differences.
"NexGen Living is a two-sided marketplace, which means I had to build two completely different acquisition funnels, two distinct Experience Cloud portals, two separate Marketing Cloud journeys — and then have them converge at a matching engine. The matching engine is a Scheduled Flow that queries both pools, scores compatibility across eight criteria, and auto-creates ranked match proposals. No Apex. The piece I'm most proud of is the contractual enforcement chain: when a Service Cloud SLA is breached, a Record-Triggered Flow automatically calculates the financial penalty, creates a Credit Memo, and injects a negative line item into the next invoice through Revenue Cloud. The renter's contract enforces itself — that kind of cross-cloud data flow, done entirely declaratively, is what separates a Salesforce architect from someone who just builds flows."
Available for Salesforce Administrator, Consultant, or Platform Engineer roles.