top of page

ABOUT.

Headshot of Eli Parker, Founder of Lucent

Nothing in business should ever take priority over doing right by people. I'll never minimize my expectation that profitable practices can be built without sacrificing decency, compassion, and responsibility for everyone we work with and the patients we serve. 

ELI PARKER, MBA

FOUNDER OF LUCENT
FORMER CHIEF STRATEGY OFFICER OF FORGE SPECIALTY PARTNERS

Eli brings ten years of experience applying a background in analytical biochemistry and revenue strategy to maximize profitability and operational efficiency in both hospitality and dentistry, most recently as Chief Strategy Officer at Forge Specialty Partners, an oral and maxillofacial surgery DSO.

Professional Work Experience Flowchart Depicting Positions Eli has Held in Revenue Strategy and Dental Industries.

Solve problems with solutions that return time to the team and deliver exceptional care to patients.

  • Do Good and Be Truthful: Profitability and principled practice are not mutually exclusive. Lucent operates on the conviction that building a more efficient, more profitable practice requires no compromise to decency, compassion, or the responsibility to do right by every client and team member served.
  • Aim for Perfection without Becoming a Limitation: Lucent holds a high standard, and though perfection may not be attainable, we consider the pursuit of perfection worthwhile. When 'good enough' becomes the operative standard, culture tends to follow. The goal is consistent progress toward an ambitious benchmark, for the benefit of patients, team members, and the practice.
  • Embrace Failure: Well-functioning systems are not static achievements, they are products of iteration. Lucent operates on the understanding that every system developed and implemented should anticipate breakage - accounting for the errors end users will inevitably encounter, and building a clear path to course correction, adaptation, and resolution. Flaws are naturally occuring in operational systems and should be embraced for the value provided to innovation when avoidance is not possible.
  • Client relationships are a deliberate part of how Lucent operates. The partnership process is structured to ensure that before any partnership begins, the working relationship is a genuine fit for both the business and the people involved. If Lucent is not the best fit, we will recommend other options outside of Lucent that may be better suited, including making introductions as needed.

Profitability and principled practice are not mutually exclusive. Lucent operates on the conviction that building a more efficient, more profitable practice requires no compromise to decency, compassion, or the responsibility to do right by every client and team member served.

do good and be truthful

Lucent holds a high standard, and though perfection may not be attainable, we consider the pursuit of perfection worthwhile. When 'good enough' becomes the operative standard, culture tends to follow. The goal is consistent progress toward an ambitious benchmark, for the benefit of patients, team members, and the practice.

AIM FOR PERFECTION WITHOUT BECOMING A LIMITATION

Well-functioning systems are not static achievements, they are products of iteration. Lucent operates on the understanding that every system developed and implemented should anticipate breakage - accounting for the errors end users will inevitably encounter, and building a clear path to course correction, adaptation, and resolution. Flaws are naturally occuring in operational systems and should be embraced for the value provided to innovation when avoidance is not possible.

embrace failure

Client relationships are a deliberate part of how Lucent operates. The partnership process is structured to ensure that before any partnership begins, the working relationship is a genuine fit for both the business and the people involved. If Lucent is not the best fit, we will recommend other options outside of Lucent that may be better suited, including making introductions as needed.

only partner when it is good for the client

  • Is [the operational change being considered] good for the team?
  • Is [the operational change being considered] good for the patient?
  • Is [the operational change being considered] good for the practice?

Any solution that is genuinely good for the team will, in turn, be good for the patient. Any solution that is good for the patient will produce meaningful gains for the practice.

 

Lucent is built around a straightforward premise: practices can be profitable without compromising patient care, patient experience, or team well-being.

​

Every solution Lucent offers is grounded in experience with having worked toward real operational outcomes from each seat on the team — new patient acquisition, scheduling conversion, case acceptance, recall rates, patient retention, profit margins, and team morale. Every engagement is deliberate from determining the right scope, to the right solution, to the right implementation process. Nothing is added because it is billable. Every action is taken to benefit the client and the patients we serve.

​

Lucent approaches operational challenges from a broad perspective by identifying bottlenecks and gaps that appear consistently across practices, then solving for them with a practical understanding of how each role contributes to the success of the improved workflow based on personal experience in each role. Where others may offer a playbook, Lucent offers one clear solution to one discrete operational challenge at a time, and sees that solution through to implementation.

I'm originally from Charleston, South Carolina, but I'm currently living in the Shenandoah Valley in Virginia. An ideal day is exploring a new hiking trail or vineyard with my husband, trying a new restaurant, and closing out the day watching a movie at home with the cats. 

Apart from loving what I do, I enjoy a dry white wine or a gin and tonic, anything cooking-related, reading, watching sumo wrestling, collecting minerals, and experiencing something new - whether it be a new city, vineyard, food, book, etc. 

Visual Depicting Eli's Personality Types: Myers-Briggs is INTJ; Enneagram is a 1 wing 2; DiSC is a Solid D; and 16 Personalities is The Architect

Working style

communication style

I work best in roles that require high-level accountability, systems design, and quality control. Autonomy is essential to how I work, both in my own process and in the systems I develop. Every outcome is designed to address a precise need.

 

Clear standards and expectations bring out my highest quality work, though I adapt quickly when clarity is not available. I make the most meaningful progress toward a finished result through working in long, uninterrupted blocks of focused production, rather than managing multiple simultaneous tasks. This approach to managing producing hours is balanced with my ability to maintain availability for meetings and daily communications to keep projects on track.

My communication style is direct and thorough. I lead with all relevant information upfront to prevent exchanges from becoming extended back-and-forth or generating unnecessary calls.


I treat meetings as the venue for making decisions or working through challenges too complex to resolve in writing. For information sharing, a thoughtful email or a brief message is almost always the more efficient choice.


Effective communication, as I see it, comes down to delivering the most value in the least burdensome way, as promptly as the situation allows.

leadership style

decision-making style

Leadership is a privilege and a responsibility I take seriously above all others, because the influence it carries can help or harm, and that line is often narrower than it appears. I do not aim to be a popular leader. I aim to be a genuine one, making decisions that reflect honest consideration of everyone they affect. Every situation calls for a careful balance of objectivity and empathy. Achieving the right outcome matters, and so does acknowledging the emotional investment of the people involved.


My leadership pillars are straightforward: do the most good for the most people, treat everyone with respect through honesty and individual attention, and never ask something of someone I would not be willing to do myself.

I make decisions grounded in verifiable standards and data rather than consensus or intuition, while always heavily weighing the impact on the team responsible for executing or receiving them.


Every decision is made with as much foresight as the available information allows. Planning for downstream outcomes is, in my view, one of the most worthwhile investments of time in operations. Decisions made in haste are sure to generate costly rework in the future. At the same time, I am deliberate about not allowing thorough consideration to become prolonged deliberation at the expense of the team or the work itself.

bottom of page