Every small jewelry store has one.
Not the best jeweler. Not the one who closes the biggest sales. The one who knows where everything is, who set up whatever system the shop actually runs on, and who gets asked when something doesn’t work.
In a four-person shop, three people make and sell jewelry. One person does everything else — and “everything else” turns out to be the software, the intake process, the follow-ups, the vendor calls, and the answer to any question starting with “how do I…”
Nobody hired her for that job. There was no job.
What the role actually is
Read the list of what falls to this person and it’s a full-time position at a bigger company:
She’s the systems analyst — the one who notices the paper intake failing before anyone else does. She’s the implementer — the one who builds the replacement. She’s the trainer, the help desk, the vendor relationship, the person who evaluates new software, and the one who migrates everything when a tool changes.
She also works the floor.
And the whole time, this role is invisible on the org chart, because in a four-person shop there is no org chart. It’s just what she does after the other things she does.
The buying criterion nobody asks her about
Here’s where it matters commercially, and where most vendors miss her entirely.
When she evaluates a tool, she is not asking what you think she’s asking. She’s not comparing feature lists. The purchasing requirement, stated plainly, is always some version of: what is the quickest, easiest way to do this — with people in the building who aren’t tech savvy, and no time to train anyone.
That is the purchasing requirement. The tool has to work for the least technical person in the building, on a busy day, without training. Not “has an onboarding flow.” Without training — because there is no time to train anyone, and if she has to be the help desk for it forever, she’s just bought herself a second job.
That’s a harder bar than most software clears, and almost nobody is asked about it during a demo.
Why vendors keep missing her
Software gets sold on capability. The pitch is what it can do, and the demo is run by someone who knows the product cold.
But her decision doesn’t hinge on the ceiling. It hinges on the floor: what happens when the person who is least comfortable with computers has to use this during the busiest hour of the week, and she’s with a customer and can’t come help.
If the answer is “they’d figure it out” — she doesn’t believe you, because she’s watched people not figure it out.
If the answer is “there’s training” — she’s hearing that she’s the trainer.
So the tool that wins isn’t the most capable one. It’s the one with the shortest distance between opening it and getting the thing done.
If this is you
A few things worth knowing.
The role is real even though it’s uncompensated and unnamed. You’re doing systems work. The fact that it happens between customers doesn’t make it something else.
Your instinct to keep it simple is not a limitation. It’s the correct read of your constraint. A system your team won’t use is worth less than a worse system they will.
Write down what you built. The auto-numbering, the print that produces three documents, the naming convention only you know. Right now the shop’s operating system lives in your head, and that’s the single largest risk in the building — bigger than any software decision you’ll make this year.
Quick and easy for everybody is a legitimate requirement, so make vendors answer it. Ask them to show you the least technical version of their product. Ask what happens when someone gets it wrong. Their answer tells you whether they’ve met you before.
And if you’re selling to her
She isn’t behind. She’s the kind of person who builds a working system out of a spreadsheet and a printer while running a sales floor.
She just doesn’t have room for one more thing that only works when she’s standing there.