Monthly Business Signal Essay
Once a month, I publish an essay that shows how I see business and systems-level challenges. These pieces are different from my twice-weekly writing. They’re written for people who need someone who notices what others miss, whether that’s in a controller role, a project engagement, or something longer-term and advisory.
I’m currently operating on two tracks: seeking remote employment in senior accounting and finance roles and building an independent practice for founders and organizations who want structural clarity, not just clean books. If this resonates and you think we should work together, reach out.
Photo by Allison Saeng for Unsplash+
I am learning how to care for precision.
Not precision as perfectionism or rigidity, but precision as an instrument that detects misalignment before it becomes visible. My nervous system is not optimized for endurance through distortion. It is optimized for early detection. It registers when ethical load is unevenly distributed, when harm is quietly being absorbed so a structure can keep functioning, when language has stopped mapping reality.
This does not arrive as an abstract concern. It arrives like a violin protesting misalignment—a sudden squeal or bow chatter that hits the nervous system before thought intervenes. My spine wobbles. I swallow hard. My eyes close involuntarily. The body tightens because something structural is off, long before an obvious failure appears.
For a long time, I believed my sensitivity was the problem. That belief was reinforced in certain environments: when I struggled to move on, or when events lingered in my body longer than seemed reasonable. I saw it as a failure to regulate.
I see now that this was a category error. The sensitivity was never the issue. The issue was that neither I nor the systems around me understood the instrument I was actually playing.
Stewardship as Practice
Stewardship begins with recognizing what you’re actually holding. In my case, that’s a diagnostic capacity that functions whether I want it to or not. It sees who is carrying ambiguity and who is being asked to override their own signals to keep things running smoothly. It notices when processes depend on memory, vigilance, or informal workarounds. It registers the gap between what a system claims to do and what it actually requires of people.
This has shown up in most environments I've worked in — sometimes as design problems that could be fixed, sometimes as capacity constraints that needed acknowledgment. The accounting department where month-end close was “on time” but only because two people were working unpaid overtime and a third had built a shadow tracking system in their personal spreadsheet. The executive team presentation where the numbers were accurate, but the narrative required ignoring what the trend lines were actually saying. The founder who asked for help pricing a product, but what they actually needed was someone to name that their cost structure couldn’t support the business model they’d committed to.
In systems terms, this kind of detection identifies where good outcomes require constant compensation. Once those points are visible, the work is not about fixing people. It is about redesigning systems so coherence doesn’t depend on heroics.
That’s the work I’m interested in. Not just implementing processes or cleaning up messes—though I do both—but working with people who want their structures to actually hold.
The Hypocrisy Alarm
I have a powerful hypocrisy alarm, and it has made me inconvenient to work with in a few specific environments.
This is not about literalism or verbal missteps. I have no issue with mixed registers. I can navigate a conversation where enthusiasm arrives as “wow, girl!” and analysis lands as “look at your balance sheet.” I allow for clumsiness, growth, and the gap between what people mean and what they can yet enact.
The alarm sounds only when there is a structural decoupling between stated values and lived behavior. It sounds when a company markets an onboarding tool as “rigorously tested” while declining to use it internally. That is not a marketing pivot. It is an ethical displacement. The company is transferring unvalidated risk onto the customer while presenting certainty it has not earned.
This is often dismissed with phrases like “that’s just marketing” or “everyone overpromises,” as if naming the practice dissolves its impact. It does not. Those statements shift attention away from the actual issue: not whether overpromising is common, but where the cost of that overpromise lands. Normalization does not neutralize harm. It merely obscures responsibility.
My system registers this as unstable terrain not because harm is proven, but because language is no longer mapping reality. It is the sound of a string being bowed at the wrong angle—jarring, unavoidable, and diagnostic.
In an accounting context, this shows up constantly. The CFO who wants “aggressive but defensible” revenue recognition. The founder who describes their burn rate as “sustainable” while making payroll from personal credit cards. The controller who says controls are “adequate” while knowing three people have admin access they shouldn’t have and nobody’s reconciling petty cash.
These aren’t always ethical failures. Sometimes they’re capacity failures. The person knows the gap exists but doesn’t have resources to close it. But the gap still exists, and someone is absorbing the cost of maintaining the fiction that it doesn’t.
I won’t participate in that absorption anymore. When I work with someone, they get structural truth even when it’s inconvenient. That’s the filter. If you want someone who will make the numbers say what you need them to say, I’m the wrong person. If you want someone who will tell you what the numbers are actually saying—and help you build systems that can handle that truth—we should talk.
Challenge as Information
One clarification matters here. My instrument is not opposed to challenge. It responds well to rigor, disagreement, and being proven wrong when the evidence warrants it. I am not threatened by critique, nor do I require affirmation to remain oriented.
What I cannot abide is challenge that is performative, defensive, or structurally constrained.
I have seen what it looks like when systems treat challenge as information and allow it to change direction. Those experiences are numerous, formative, and real. In a handful of the systems I have challenged, however, disagreement is welcomed only in theory. The appearance of openness is preserved while the conditions required for genuine challenge are quietly removed.
When that happens, challenge stops functioning as information and starts functioning as risk. At that point, my signals become inconvenient not due to inaccuracy, but because they would require structural change.
This reframes a lifetime of intermittent, but confusing feedback that I was “complicated” or “oppositional.” The issue was never my resistance to challenge. It was my refusal to participate in systems that require coherence to be asserted rather than tested.
This matters for anyone considering working with me. I will tell you what I’m seeing. I will update that assessment when new information changes the picture. I will not soften structural problems to make them more palatable. And I will not stay in environments where my diagnostic capacity is treated as a liability rather than a resource.
Truth and Coherence
Because I come from neurodivergent communities that rightly prioritize lived experience over institutional authority, I want to be precise about truth. Truth is what holds under contact with reality. It is what remains consistent across time, behavior, and consequence.
Lived experience is crucial here not because it is infallible, but because it is where impact shows up first. Bodies register strain, confusion, and misalignment before institutions do. Truth that cannot support human thriving is not neutral. It is extractive.
So, when I say something is not true, I am naming a coherence failure. I am identifying a place where maintaining the official story requires ongoing compensation from human nervous systems. Where patterns cannot be challenged, tested, or refined without penalty, the system has already failed its own truth claims.
This is why certain events did not just hurt; they forced a recalibration of the map itself. When principles I organized my life around turned out not to be load-bearing, the injury was biological. It was ethical reconstruction—a refusal to live inside a model that no longer produced truth.
In financial and operational work, this distinction matters. A budget that “works on paper” but requires three people to quietly subsidize it with unpaid labor is not actually working. A process that’s “documented” but nobody follows because it doesn’t match how the work actually happens is not actually functioning. A control environment that “passes audit” but depends on one person’s vigilance is not actually controlled.
The work I want to do is about making those gaps visible and building structures that close them. Not through surveillance or rigidity, but through design that accounts for how humans actually work.
What I’m Building
I am building trust the long way, through clarity and a consistent signal of coherence that seeks resonance rather than market share. I am not trying to persuade anyone. I am trying to be found by people who are already looking for what I offer.
That means I work differently than most people in accounting and advisory roles. I don’t do performative marketing. I don’t send AI-generated follow-ups. I don’t promise certainty I haven’t earned. When communication is treated as a task rather than a relationship, coherence degrades. The cost doesn’t disappear; it’s simply no longer carried by the sender.
I won’t build my work on that transfer.
What I am interested in now is stewardship. Of my own instrument, yes, but also of the environments I choose to participate in. A fail-safe life is one with layers that absorb error before it reaches the core. Structural clarity. Temporal slack. Relational integrity. Ethical alignment that does not require constant self-betrayal.
This shows up practically in the work I take on. I am looking for people who want to be ready, not people I need to convince. Founders who sense something is structurally off and want help seeing it clearly. Controllers and finance leaders who know their systems are held together with informal workarounds and want to build something that actually holds. Organizations that are willing to reorganize when the diagnosis shows reorganization is what’s needed.
I do traditional accounting work—month-end close, reconciliations, reporting, financial modeling, systems implementation. I also do diagnostic work that sits between accounting and operations, finance and strategy. I can step into an environment, map how the pieces interact, and tell you where the load is landing and what that’s costing you.
If you are already in motion and want skilled partnership on equal footing, we should talk. If you need someone to validate decisions you’ve already made or smooth over structural problems with better messaging, I am not the right person.
I am not trying to be less sensitive. I am learning how to care for precision—and to work only in environments where that precision is a resource, not a liability.
Chris Stephens is a Wisconsin CPA with over 30 years of experience in accounting, financial operations, and systems-level thinking. She is currently seeking part-time or full-time employment in remote senior accounting and controller roles while building an independent practice serving founders and organizations who want structural clarity. You can reach her on LinkedIn.


