Chapter 7 Asher
ASHER
Iwas in the conference room by five thirty, coffee in hand, reviewing the SEAS documentation for the third time.
My notes filled the margins of the printed specs, questions highlighted in various colors based on priority.
An hour of sleep and a cold shower hadn’t done much to clear my head, but I was sharp enough. Sharp enough was all I needed.
Mike let himself in at quarter to six, setting a fresh stack of reports on the table along with a coffee from the good place downstairs. The bastard.
“Anything on the parking garage footage?” I asked without looking up.
“Same pattern as the other incidents. Dark sedan, can’t get a plate. Someone circled her car for about ten minutes after midnight.” Mike settled into the chair across from me. “I’ve got a guy on it. Discreet.”
“Good. Keep it between us.”
Mike studied me. “You look like hell.”
“So I’ve been told.”
“Did you sleep at all?”
“Enough.” I turned another page of the SEAS specs. Every time I went through them, I found something else to be impressed by. The environmental safeguards alone were miles ahead of anything else in the industry.
“She’s still in the building, by the way,” Mike said, checking his phone. “Security logged her in yesterday afternoon. Never logged out.”
I looked up at that. “She’s been here all night?”
“Appears so.”
Twelve hours. I’d given her twelve hours to produce a full civilian implementation plan, expecting her to push back on the timeline, negotiate for more time, maybe deliver a rough outline and promise the rest by end of week.
Instead she’d stayed all night.
The door opened at five forty-five.
Charlie walked in carrying a clean folder and nothing else. No laptop, no tablet, no flash drive full of half-finished slides. Just the folder.
Her hair was pulled back in its usual knot, though more of it had escaped than usual. Dark circles under her eyes. She looked like she’d been up for twenty-four hours, which she had.
She also looked like she was ready to go twelve rounds with anyone who questioned what she was about to put on the table.
“Mr. Pierce.” She set the folder in front of me. “Mike.”
“Charlie.” Mike gave her a nod that held genuine warmth. She returned it. She was warmer with him than with me, which made sense. Mike hadn’t lied to her at a bar.
She sat, crossing her arms. “It’s on the server as well.” She said it confidently. Pointedly. I’d asked and she’d delivered.
I opened the folder.
Twenty-three pages. Executive summary, technical specifications, deployment timeline across three phases, cost projections, risk assessment, staffing requirements with individual role descriptions, and a section at the end I hadn’t asked for—a competitive analysis showing exactly how far ahead SEAS was compared to every other safety system on the market.
I read the first page. Then the second. By the fifth page, I’d stopped pretending to be casual about it.
The executive summary alone would have been enough to greenlight a project at Pierce Construction.
She’d identified twelve target clients she could approach within sixty days—not theoretical prospects, but companies with active underwater operations and documented safety gaps.
She’d pulled their incident reports. She’d calculated what SEAS would have saved them in the last fiscal year.
She’d put a dollar figure on every life that could have been protected.
Page eight was the deployment model. Three phases, each building on the last, with clear go/no-go criteria between them. No magical thinking, no optimistic hand-waving. Just rigorous, honest timelines backed by data she’d generated herself over three years of testing.
Page fourteen stopped me. The insurance liability model.
She’d built it using a framework pulled from my company’s public SEC filings—she’d researched Pierce Construction’s insurance structure overnight and found a way to slot SEAS into our existing marine operations rider.
It would save us eighteen months of legal work.
She’d done this in twelve hours. On no sleep. With every reason to walk away, to deliver the bare minimum, to prove a point about unreasonable deadlines.
Instead she’d built something better than what I’d asked for. And three things I hadn’t thought to ask for: a PR strategy for the first deployment, a training protocol for client teams, and a risk mitigation framework for the transition from lab to field.
I recognized this. Not just the quality of the work, but the desperation underneath it.
The ferocity of someone who’s been told no for so long that when someone finally opens a door, they don’t just walk through it—they bring the whole goddamn house.
I’d built Pierce Construction the same way.
Alone, underfunded, sleeping in my truck between job sites, refusing to quit because the alternative was admitting that Tommy had died for nothing.
She sat across from me, quiet, while I read. She didn’t fidget. Didn’t explain. Didn’t sell. Just waited.
When I looked up, she was watching me with an expression that dared me to find a flaw.
“Page fourteen,” I said. “The insurance liability model. You’re assuming the client carries primary coverage?”
“Yes. With Pierce Construction providing secondary through a specialized marine operations rider. I pulled the framework from your public SEC filings—you already have the infrastructure for it.”
“Page nineteen. The Phase 2 testing timeline. You’ve compressed it to eight weeks.”
“Assuming access to adequate facilities.” A beat. “Which I currently don’t have.”
I closed the folder and looked at her. She held my gaze, spine straight, shoulders back. Exhausted and unmovable.
“This is exceptional work, Charlie.”
Something flickered behind her eyes. Not gratitude—more like relief that she wasn’t going to have to fight for what was already obvious. She gave a short nod. “Thank you.”
The rest of her team arrived at six, filing in with their own coffees and materials.
Jason, the sandy-haired programmer from the bar, took the seat beside Charlie.
Two women I hadn’t met—software leads, from the look of their laptops and the way they immediately started pulling up code.
Two more engineers, both carrying prototype components wrapped in static-resistant fabric.
I noted how each of them looked to Charlie when they entered. Not to me, not to Mike. To her. Checking her face, reading her mood, adjusting accordingly. She gave them a small nod—we’re good—and they settled in.
That was loyalty you couldn’t buy.
Charlie walked them through the plan, and I watched a different version of her emerge.
Not the guarded woman who addressed me as Mr. Pierce, but the leader her team knew—confident, precise, generous with credit.
She referenced each person’s contribution by name.
She deferred to Jason on the sensor programming timeline, and when one of the software leads—Priya, dark-haired, quietly intense—pushed back on the Phase 1 integration window, Charlie didn’t shut her down.
She pulled up the data on the boardroom laptop, walked through the bottleneck, and adjusted the timeline on the spot.
Two days added. No ego. Just the right answer.
Jason caught my eye at one point and leaned over to mutter something to Charlie that made her suppress a smile.
She shook her head at him—not now—but the brief flash of warmth between them told me everything I needed to know about how she ran her team.
They’d follow her anywhere. Not because they had to, but because she’d never ask them to go somewhere she wouldn’t go first.
Her hands moved when she talked about the safety systems. Cutting through the air, shaping structures I couldn’t see.
The same way they’d moved at the bar when she’d told me about underwater construction.
She had no idea she was doing it. I remembered thinking I could watch her talk about this work forever.
That thought was no less dangerous now than it had been two nights ago.
“The acoustic deterrent system is where we’re furthest ahead,” she was saying, pulling up a schematic on the wall screen. “Instead of fighting the interference from varying water density, we use it as additional data. The system learns from every deployment, adapts in real time.”
“Predictive rather than reactive,” I said.
She glanced at me, surprised. “Exactly.”
“How did you solve the calibration drift in high-pressure environments?”
The question was genuine, and she knew it. Something in her posture shifted—not warmth, not yet, but a loosening. The willingness to talk to me as an engineer rather than an adversary.
“Dual-redundant sensor arrays with independent calibration cycles,” she said, leaning forward. “If one array drifts, the other catches it. The system flags the discrepancy and auto-corrects before it affects output.”
“Elegant.”
The word slipped out before I could filter it.
Charlie’s eyes met mine for a moment, and I saw the engineer light up underneath the exhaustion and the anger.
This was what she lived for—not the politics, not the power plays, but the work itself.
The problem-solving. The possibility of keeping someone alive who might otherwise die.
If we’d had technology like this when Tommy was still alive . . .
I forced the thought down and focused on the next page of her plan.
By seven thirty, we’d been through every page. I had questions. She had answers. For the few questions she didn’t have answers to, she said “I’ll find out” instead of guessing, which told me more about her integrity than any background check could.
“Your Phase 2 testing requires hyperbaric chambers and a full-scale underwater pool,” I said. “You don’t have that here.”
“No. Richard always deferred those investments.” The bitterness in her voice was controlled but real. Ten years of promises broken.