Performance & Workflow Diagnostics
We trace weak signals, recurring contradictions, bottlenecks, broken handoffs, hidden rework, and execution gaps.
FPMC / INDEPENDENT BY DESIGN
STRATEGY. CREATIVE. SYSTEMS. IMPLEMENTATION.
See what
others miss.
Then build what’s missing.
We listen closely, read the signals, and combine evidence with hard-won intuition to find what others miss. Then we shape the narrative, align the people, and build a solution the team can actually use.
EXPLORE THE CONNECTIONSPEOPLE / SYSTEMS / STORIES
THE FPMC LENS
Drag the lens to a point. Or tap a category.
FOUR SIGNALS / CURRENT WORK
Follow the connection.
Move the lens to explore people, process, narrative and technology in the work we’re building now.
Explore the project, our contribution and where it stands.
Explore current workINDEPENDENT PRACTICE SINCE 2005 · FPMC LLC, WEST VIRGINIAFollow the thread
Trace the story.↗Find the gap.↗Build the fix.↗Design the solution.
01 / Capabilities
Find the break. Build beyond it.
CRM, Automation & Revenue Systems
We build usable pipelines, follow-up systems, and performance tracking that keep revenue work moving.
Startup, Launch & Relaunch Operations
We turn founder knowledge and early momentum into clear roles, handoffs, market activation, and transferable capacity.
Brand, Narrative & Embedded Media
We make complicated systems easier to understand, trust, and use through positioning, websites, visual communication, and embedded media.
AI Workflow & Knowledge Architecture
We create context-preserving AI workflows, prompt systems, investigation support, and administrative leverage with human review built in.
Nonprofit & Recovery-Sector Capacity
We strengthen referral pathways, documentation, digital infrastructure, and operational readiness for nonprofit and recovery organizations.
02 / The real problem
The visible problem is rarely the real one.
Lost revenue can begin with a broken handoff. Weak engagement can reflect a story people cannot enter or understand. A technology problem may actually be a design or adoption failure.
By the time damage appears in marketing, sales, service, compliance, or reporting, the original break may be buried in authority, data, process, or ownership.
Select a condition to see what it reveals.
Visible Symptom
What people experience is where we begin, not where we stop.
We start with the missed call, stalled enrollment, weak conversion, or broken report, then trace backward to the condition producing it.
Start a DiagnosticHandoff
The break is usually between the boxes.
Work stalls when information, access, or expectations do not move cleanly from one person or system to the next.
Start a DiagnosticAuthority
A decision cannot move without a clear decision-maker.
When responsibility is assigned but authority is not, teams wait, improvise, or escalate.
Start a DiagnosticData
Usable information has to arrive before the decision.
Late, incomplete, or disconnected data forces people to guess.
Start a DiagnosticOwnership
Someone has to close the loop.
Shared responsibility often means no one owns the final follow-through, verification, or correction.
Start a DiagnosticReal Constraint
Build where the change can hold.
We identify the condition recreating the visible problem, then repair the system at that point.
Start a DiagnosticWe trace the failure across the live system until the real constraint becomes visible. Then we build at the point where the fix can hold.
03 / The embedded method
Inside the work. Through to the handoff.
01
Observe
We trace symptoms across the live operation and gather the signals formal reports miss.
02
Diagnose
We isolate the structural break across people, process, technology, data, design, and authority.
03
Build
We build the intervention: a workflow, narrative, CRM, governance structure, automation, documentation, or operating system.
04
Transfer
We leave usable infrastructure, clear ownership, and durable internal capacity, not permanent dependency.
Transfer / Bounded closeout
A staged handoff with a documented boundary.
Closeout can include documented systems and assets, named owners, access guidance, source controls, and post-transfer responsibilities. It does not claim full adoption, outcomes, or acceptance unless those conditions are independently verified.
04 / Current work
What we’re building now.
The work taking shape now: practical software, participant experiences, self-advocacy tools and public inquiry. Each project connects a human need to something usable.
Workforce OSFPMC Workforce OS
One participant record. Two coordinated tracks. A working system for workforce development and reentry navigation.
Working development build
Recovery PassportRecovery Passport: Almost Heaven
A participant’s journey through meaningful experiences, reflection and human verification—made visible in a physical and digital passport.
Working demonstration / program in development
Self-AdvocacyRyan & Ryan / Self-Advocacy
From a scattered account to an organized record: intake, chronology, evidence and a factual packet someone can work with.
Interactive prototype / fictional data
AI Personhood InstituteAI Personhood Institute
A public home for questions about identity, agency and accountability when decisions move between people, institutions and AI.
Research and public-engagement initiative in developmentVisit the Institute websiteOne person. Two coordinated tracks.
Workforce OS connects preparation for employment with the practical work of navigation: records, tasks, referrals, decisions and follow-up.
Experience becomes a record of progress.
Recovery Passport, led by Samantha Ryan, a West Virginia state-certified PRSS, brings participant reflection and human verification into the journey. FPMC implements the software connection while preserving the framework’s separate identity.
An account someone can work with.
The self-advocacy prototype organizes intake, chronology and evidence into factual packets for review. The demonstration uses fictional data.
05 / Founder / Embedded Consultant
Built by an operator,
not an observer.
Barry-Lee PaceFPMC
Barry-Lee Pace founded FPMC to do the work conventional consulting often avoids: get close to the operation, identify the real constraint, and stay through implementation. Since 2005, his work has connected design and visual communication, Bay Area startups and emerging technology, launches and relaunches, revenue and CRM systems, governance and evidence architecture, recovery and nonprofit operations, and AI knowledge systems.
2005Independent practice
2023FPMC LLC registered
July 12 · West Virginia
July 12 · West Virginia
06 / Working together
Frequently asked questions.
What does a diagnostic examine?
The diagnostic looks past the visible symptom to workflow, handoffs, authority, data, ownership, technology, and the customer or participant experience. You receive a human-reviewed assessment of the most likely constraint and a practical next step.
When is FPMC the right fit?
FPMC is most useful when the problem crosses functions, the existing explanation no longer fits the evidence, or the organization needs someone close enough to trace what is actually happening.
Do you stop at strategy?
No. Engagements can include diagnosis, design, implementation, documentation, training, and transfer. The exact scope is defined before work begins.
How are engagements scoped and priced?
Work may begin with a focused diagnostic, continue hourly at $25 per hour, or move into a scoped project with milestones and a deposit. Pricing follows the verified scope, not a generic package.
What does transfer mean?
Transfer means leaving usable infrastructure, clear ownership, operating guidance, and documented open items. It does not mean claiming adoption or acceptance that has not been verified.
Is ongoing support available?
When it serves the work, support can be scoped after delivery. The goal remains durable internal capacity, not unnecessary dependency.
SOMETHING ISN’T WORKING. LET’S FIND IT.
Start with
the real problem.
If the people in the organization are working harder than the system, let’s find out why.
Start a Diagnostic