← Selected workSUPPORTING TECHNICAL WORK

Technical Work

Explore the customer-operations intake demo, owner views, SQL model, and Power BI files. These separate learning artifacts show the supporting technical work; they are not a fifth case study or a deployed production system.

Read Before We Commit →
CUSTOMER-OPERATIONS WORKSPACE

One request, from missing information to review.

Use the sample intake to see how I would check a handoff. The owner dashboard, SQL model, and optional Salesforce mapping below are retained learning artifacts. They do not resolve commitment 388763 or verify its quantity, specification, or timing.

Two separate examples: the owner dashboard summarizes December 31, 2025 work. Riverside is a historical readiness review dated September 10, 2025. It illustrates the missing-confirmation problem; it does not establish that the same issue remained unresolved in December.

TRY ONE HANDOFF

What would make this request ready for its next owner?

  1. Request arrives. Select Westbridge’s sample commitment-readiness request. The account is active, but that alone is not customer confirmation.
  2. Identify the blocker. Leave customer confirmation unchecked and try saving. The request stays outside the ready queue. The historical Riverside review below explains why a location-level answer matters.
  3. Preserve the evidence. Select the location, record confirmation, and attach the source before saving. These are sample checkboxes; a real workflow needs the underlying record and confirmation date.
  4. Assign the next step. Save to see the assigned queue and follow-up target. An individual owner must still accept the work. Submit again to test a possible duplicate.

Fictional, browser-local demonstration. “Ready for owner” means ready for review, not approved for release. Saving does not update the source data or connect to a CRM.

TEST ROUTING AND READINESSWorking intake demo

Sample account: A006. One representative location per account in this demo; the source model’s 74 locations are not editable here.

WORKFLOW RESULTNeeds information
Queue
Customer Operations
Follow-up
Same day as intake

The request cannot be saved until required inputs are checked.

  • Select the sample location
  • Record customer confirmation

Local demo records (0)

Saved in this browser across refreshes, separately from the 44 source requests and 120 source actions.

No sample requests saved yet.

SUPPORTING PROTOTYPEExplore the owner dashboard and connected recordsSeparate December snapshot · six owners · 120 actions
MY WORK

Noah Brooks

All assigned accounts · featured account A006
ASSIGNED TASKS20Across 10 assigned accounts
OPEN TASKS1All assigned accounts
OVERDUE TASKS1All assigned accounts · Dec 31, 2025
FEATURED ACCOUNTWestbridge GroupInternal review
QUESTION WORTH ASKINGHistorical example: which Riverside quantity was customer-confirmed?

A written review prompt based on this featured account’s visible condition. The prototype does not generate a question for every action.

Open connected record ↓
CONNECTED ACCOUNT

Westbridge Group

Source Account ID · A006
Active customer
ARR
$150K
Modeled risk tier
High
Adoption change
−0.6 pts
Open or escalated cases
0
VALIDATION RULERequired context

Block Ready status without an account, request type, applicable location, customer confirmation, and source evidence.

PROPOSED DUPLICATE RULEMatch before create

Implemented for local demo records: the same account, sample location, type, and received date is flagged before saving. A production workflow would review possible matches rather than assume they are the same issue.

ROUTING LOGICRoute and suggest follow-up

The demo saves a queue and follow-up target with each accepted sample request. External task creation remains a proposed implementation.

PROPOSED ACTIVITY HISTORYKeep the audit trail

Track owner and status changes while preserving source evidence, follow-up work, and final resolution.

OPTIONAL CRM IMPLEMENTATIONHow this workflow could be configured in SalesforceObject mapping, validation, routing, Flow, reports, and acceptance tests

The workspace above is a conceptual customer-operations prototype, not Salesforce Lightning and not evidence of a deployed org. The supporting specification maps the same workflow to standard and custom Salesforce objects as one possible implementation path.

View optional Salesforce specification ↗
SUPPORTING ANALYTICS

The workflow totals reconcile to the SQL and Power BI model.

The workspace, SQL model, and Power BI files share source IDs and record definitions. North Star is a standalone workbook with different account IDs, so only its published totals and five named queue accounts are reconciled here—not presented as row-for-row lineage.

MeasureWorkflow recordSupporting sourceVerified value
Customer accountsAccount recordSQL + Power BI60
Operating locationsLocation recordSQL + Power BI74 · 15 Westbridge
Follow-up workAction recordactions.csv + Power BI120 · 38 open · 11 overdue
Support historyCase recordcases.csv + Power BI470 · 49 escalated
Decision historyRequest recordWho Decides? + SQL44 requests
Modeled review groupPortfolio viewNorth Star Excel + Power BI22 accounts · $4.149M ARR
Leadership subsetReview queueNorth Star Excel5 accounts · $2.358M
Readiness review evidenceEvidence recordSupporting evidence CSV32 Riverside + 4 account context

The supplied fictional risk score creates the review group; it does not predict churn or lost revenue. Workspace ownership and follow-up views use the same 120 action rows as the SQL and Power BI files.

RELATIONAL ARCHITECTUREInspect the underlying data modelDimensions, activity tables, relationships, and record grain
DATA MODEL

Why I kept the tables separate

Accounts, locations, cases, actions, and decisions do not represent the same kind of record. Keeping them in related tables—and joining them only where the IDs match—lets the report connect the work without inflating counts or ARR.

DIMENSIONAccounts60 rows · one per customer
DIMENSIONLocations74 rows · 15 for Westbridge
DIMENSIONPeopleRecorded title + formal authority
DIMENSIONDatesShared reporting calendar
ACTIVITYMetrics · Cases · Actions · Requests · EvidenceSeparate grains, shared IDs
DESCRIPTIVE BRIDGERelationshipsShows access patterns, not why someone acted
FILES + QAInspect the build files and reconciliation checksSQL, Power BI, DAX, source data, and complete build pack
FILES + QA

How I built and checked the model

SQL

Schema and analytical queries

Primary and foreign keys, constraints, indexes, joins, CTEs, conditional aggregation, latest-record logic, and window functions.

View SQL queries ↗
QA

Visible reconciliation checks

60 accounts, 22 accounts in the modeled High-risk group, $4.149M in group ARR, a $2.358M top-five subset, 470 cases, 11 overdue actions, and 44 decisions all reconcile.

Download model + build pack ↓

The Power BI Project (.pbip), source workbook, and setup notes show the supporting model. These are learning-project artifacts, not production implementation or measured business results.