“And you currently have?”
“A dashboard.”
I actually laughed.
He did not.
“This isn’t funny.”
“No, Evan. It’s extremely funny. You sold a car and built the speedometer.”
“We’re going to lose the funding round.”
“That sounds possible.”
“Mom and Dad invested too.”
That stopped me.
“How much?”
“I don’t know exactly.”
“You absolutely know.”
“Claire.”
“How much?”
“More than they should have.”
I got out of bed.
“What do you want from me?”
“A prototype.”
“By Monday?”
“Functional enough for the demonstration.”
“No.”
“Please.”
“No.”
“I’ll pay you.”
“No.”
“Consulting rate. Whatever you want.”
“Evan, you need an engineering team, not your sister spending a weekend pretending three months of development can happen in seventy-two hours.”
“We have engineers.”
“Then why are you calling me?”
Silence.
Because he knew.
He needed somebody who had built systems like this before.
Someone who could create a simplified architecture that was honest enough to work but narrow enough to finish.
“Please, Claire.”
I closed my eyes.
Our mother called fifteen minutes later.
That was how quickly Evan activated the family network.
“Your brother is under enormous pressure.”
“I’m aware.”
“He says you can help.”
“I have a job.”
“He’s family.”
“So am I.”
A pause.
“Don’t make this difficult.”
There it was.
I should have said no.
Instead, I did what I had been trained to do.
I solved the problem.
But I did one thing differently.
Documentation.
Before I wrote a single line, I sent Evan a short consulting agreement.
Three weeks.
Defined scope.
Defined fee.
Core architecture retained by me unless separately assigned in writing.
Virelia would receive a limited internal evaluation license for the prototype.
Any production implementation would require either a formal IP assignment or a new license agreement.
I also disclosed the outside work to Hion’s compliance office because company policy required it.
My director approved it in writing as long as I used no Hion code, equipment, confidential design material, or client information.
I bought a separate laptop.
Created a private repository.
Used personal accounts.
Kept everything clean.
Evan signed without reading closely.
I know that because twelve minutes after I sent the agreement, the signature came back.
Then I worked.
Three weeks, not three days.
Evan postponed the investor demonstration by claiming integration testing had revealed an issue.
For nineteen nights, I came home from Hion, reheated dinner, and worked until one or two in the morning.
On weekends, I worked twelve-hour days.
I designed the routing layer.
Built the transaction state model.
Created fallback logic.
Designed reconciliation queues.
Wrote architecture notes.
Built a clean simulation environment so the demonstration could show authentic behavior without pretending to be a production-ready financial platform.
On the final Sunday, Evan came to my apartment.
He watched the system route a simulated transaction through three possible channels, reject the first based on latency thresholds, switch to the second, reconcile the result, and update the monitoring dashboard.
For once, my brother had nothing to say.
Then he whispered:
“This is incredible.”
I should not admit how much those three words mattered.
But they did.
After a lifetime of being the practical sister beside the impressive brother, hearing him recognize my work opened something stupidly hopeful inside me.
“You need a real engineering team to productionize it,” I said.
“We have one.”
“They need my documentation.”
“I’ll have them review it.”
“And the IP?”
“We’ll handle the paperwork.”
I looked directly at him.
“Evan.”
“I know.”
“The prototype remains mine until there’s a written transfer or licensing agreement.”
“I know, Claire.”
He hugged me.
“We’re going to make this right.”
Monday’s demonstration succeeded.
The investment round closed.
Virelia expanded.
Evan was interviewed by a regional business publication.
My consulting invoice remained partially unpaid.
Whenever I asked, he said cash was tight.
Then the company hired twelve new employees and moved into an office with polished concrete floors and a wall-sized logo.
The credit never came either.
Not publicly.
Not privately.
Six months later, I checked Virelia’s website.
Their new platform documentation described what they called the Virelia Flow Engine.
I opened the technical overview.
My stomach tightened.
The vocabulary had changed.
Some implementation details were different.
But the structural design was unmistakable.
Transaction state model.
Routing hierarchy.
Failover sequence.
Queue relationships.
Reconciliation flow.
It was my prototype architecture developed into a production platform.
I called Evan.
“Did your team use my architecture?”
“We used the prototype as a starting point.”
“That requires a license.”
“We changed it.”
“Changing an implementation doesn’t automatically change who created the underlying architecture.”
“Claire, don’t start.”
I became very still.
“Start what?”
“You were helping me.”