The idea was birthed at six in the morning, while laughing.
Not the good kind of laughing — the delirious kind. My colleague and I had pulled a
straight all-nighter fixing a stack of returns against a deadline someone was counting on.
We'd started in the afternoon and never stopped, and some time after the sun crept through
the shade, we realized we'd hit that wall where everything's funny because your brain has
given up.
But underneath the laughing was something that wasn't funny at all. We were typing letters
into number fields. Putting an email address where the phone number goes. Reading the same box
three times and still not processing what we were looking at. You come to and realize five
minutes have gone by and you don't know where they went.
And it was funny, in a “what are we even doing right now, we are definitely too
tired for this” kind of way —
but these were people's returns. Somebody's refund.
Somebody's mortgage approval. Somebody who trusted a professional to get it right, and we were
making decisions about their money with our eyes half-closed.
So we closed the laptops. Not because we were finished.
Because we'd become dangerous.
And in the middle of it, one thought cut through the exhaustion:
“What if this didn't have to take all night?”
I didn't do anything about it yet, but the question wouldn't leave.
Then April came. The procrastinators poured in all at once, and we were up again —
night after night this time, trying to get everyone's return complete. We couldn't. People
had to go elsewhere if they didn't want to wait. Watching good people walk because there
weren't enough hours in the day — that one stuck.
Strike one was the all-nighter. Strike two was April. Strike three was quieter: it was
the off-season, when everyone else finally gets to breathe — and I was still working
just as hard. I remember thinking, why is my time never my own?
Three strikes, one question, over and over: what if we could just do this faster?
So I decided to build the answer.
I taught myself to build an automation engine that does in minutes what used to take us
all night. I did it in the margins — because I wasn't quitting my job to chase a maybe.
I work Sunday through Wednesday, twelve-hour days. Thursday through Saturday, I'm at my
second job. And every hour I'm not at either one, I'm at my laptop doing returns —
from the time I get home until I fall asleep. I built this in those cracks, refusing to
risk my family's stability on a dream until the dream could stand on its own.
Because that's what this is really about: family. Not as a slogan — literally.
“Every name in this company is one of my kids.”
The company is named for my biological children. My daughter Jourdyn — we call her
Judy, and from that, Ju. And my son Stephaun Jr., who we call Deuce — his name
is where the sound finishes, the -ce. Put them together, and you get Juece.
My kids, built into the name of the thing itself.
And the product has a name too — Audenix — because my bonus sons belong
in this just as much. Austin and Ayden, with an x at the end for my wife, Erika.
Austin, Ayden, Erika — Audenix.
JUECE™
Ju — Jourdyn (“Judy”) + ce — Deuce (Stephaun Jr.)
My biological kids, built into the name of the thing itself.
AUDENIX™
Austin + Ayden + x for Erika
My bonus sons, and the x for my wife. The software carries theirs.
So the company carries my biological kids, and the product carries my bonus sons and my wife;
between the two names, my whole family is at the foundation of this. That was on purpose.
This was never just a tool. It's a legacy with everyone's name on it, and it's already
taking root.
My daughter Jourdyn sat beside me one evening and watched it work — really watched
it, the kind of quiet focus that tells you something actually landed. No tutorial. No
walkthrough. She just followed along and understood what she was seeing. That moment
confirmed something I already believed about what we'd built: when a tool is designed right,
it doesn't need to be complicated to be powerful.
You don't have to be a tech person. If you know returns, you'll know this.
My bonus son Austin watched me build this night after night and caught the fire himself;
he's learning to build websites for businesses now, chasing his own version of it. That's
the whole point. Best case, my kids run this someday. Worst case, they and their children
benefit from it for the rest of their lives.
Here's what I learned building it: the thing I was really after was never faster returns.
It was my time back — to be present with my family instead of buried in a laptop until
midnight. And the beautiful part, the part that turned this from a tool into a mission, is
that it doesn't just give me my time back. Every firm that uses it, every preparer drowning
the way we were — it gives them their time back too.
That's what Juece Enterprises is. We built the answer to one
exhausted question at 6 A.M., and the answer gives everyone their time back.