Product.ai
Try Product.ai
THE VERIFICATION LAYER FOR COMMERCE CHECKED DAILY · OCTOBER 23, 2026
Kelli Schall, Operations Lead at Product.ai
Operations Lead

Kelli Schall

Operations Lead · Product.ai

Leads the content-operations team behind SimplyCodes’ pages and owns the merchant catalog that backs them — its quality gate and its backend. Her job is turning work the team used to do by hand into automated systems.

The operator who catches what’s about to break before it breaks. She finds the problems at the seams between engineering, merchant data, and the live catalog — then steps in herself when waiting on someone else would cost the launch.

LinkedIn → SimplyCodes →
Owns
The SimplyCodes merchant catalog
Studied
Library & Information Science (MLIS)
Origin
Joined as a taxonomist · grew into operations
Based
Los Angeles, CA
~47K
merchant pages backed by the catalog she runs
MLIS
Master's in Library & Information Science
Taxonomist
how she joined the company
About

The operations lead who turns catalog work the team used to do by hand into automated systems — so the data behind SimplyCodes fills and checks itself.

~47K
merchant pages under her quality gate
backend
what she owns on the merchant catalog
MLIS
library-science foundation
systems
what manual catalog work is becoming
The range

01 · The core discipline

Catalog convergence

Owns the seam where merchant data, engineering, and the live catalog meet. Without someone holding that seam, pipelines fragment and things stop shipping on time.

02 · The core discipline

Automating manual work

Writes down every process the content-operations team runs, then decides which become agent-run, in what order, and which get deliberately retired.

03 · The core discipline

The quality gate

Decides which merchants clear the bar to enter the catalog — enforced in the pipeline itself, not by sweeping after the fact.

04 · How she leads

Direction calls

Decides fast and adjusts if the call turns out wrong. She’d rather make the call than wait for more information.

05 · How she leads

Affiliate revenue hygiene

Runs her own queries against commission data to catch broken affiliate links early — before they surface in a revenue report.

06 · How she works

Loop me in, then follow through

Wants to be brought in early on decisions about anything she runs, and wants people to come back when something changes rather than let it drift.

The path

From taxonomist to the operations lead running the catalog.

Founding era · Product.ai
Product.ai · SimplyCodes
Operations Lead
Leads the content-operations team behind SimplyCodes’ pages and owns the merchant catalog that backs them — its quality gate and its backend. The job is turning work the team used to do by hand into automated systems, so the catalog behind the pages that fund the company fills and checks itself. Grew into this from a taxonomist role as the catalog grew up around her.
Owner of the SimplyCodes merchant catalog
Before Product.ai
Earlier · Library & Information Science
Master's · Library & Information Science
MLIS
The discipline of how information is classified, retrieved, and made findable. That instinct now runs the merchant-catalog and quality-gate decisions behind SimplyCodes — what counts as a clean, complete merchant record is upstream of what shoppers ever find.
The foundation under the catalog
The through-line

How a library-science background ended up running a commerce catalog.

Kelli came into the company as a taxonomist — the person who decides how things are categorized so they can be found. The merchant catalog grew up around her, and she grew with it: into QA, into the quality-gate decisions that decide which merchants and offers are clean enough to go live.

The library-science training turned out to be structural, not ornamental. Information classification, retrieval, and findability are the underlying physics of how a commerce catalog stays trustworthy — and of which merchant records earn a spot in it at all.

Today she leads the content-operations team and owns the catalog’s backend. She spots the failure points before they surface, makes the call fast, and steps in herself when a process is stuck. The job title changed; the instinct that built it didn’t.

I own the convergence across multiple workstreams. Without that, pipelines fragment and things stop shipping on time. Kelli, on the through-line from taxonomy to operations
Operating code

Principles that show up across her automation work and her QA.

01 Stance

If I’m on it, it gets done.

Owns the convergence across multiple workstreams and steps in herself when waiting on someone else would cost the launch. The title is Operations Lead; the substance is the calls and the catches.

“I’d rather make the call and adjust than wait for more information. If the call turns out wrong, we fix it.”

02 Method

Automate what used to be swept by hand.

Writes down every process the content-operations team runs, work nobody had ever written down before, then decides which become agent-run, in what order, and which get deliberately retired.

“Catching what’s going to break before it breaks, at the seams between engineering, merchant data and the live surfaces.”

03 Orientation

Read the commission data, not just the dashboard.

Runs her own queries against commission data to find a broken affiliate link before it ever shows up in a revenue report, and QAs whatever her automation touches.

“Running my own queries against commission data to catch broken affiliate links early. Before they show up in a revenue report.”

04 Operating mode

Loop me in, then follow through.

Wants to be brought in early on decisions about anything she’s running — so she can speak to it. When she raises something, she needs action on it. Silent drift is the one thing she can’t work with.

“If you committed to it, follow through. Or come back and let me know what’s changed.”

05 Through-line

Craft over churn.

Cares about great data and great finished products. Would rather ship fewer things done well than a pile of things half-finished. If something works, she’s already thinking about how to make it work better. She doesn’t settle at “fine.”

“If the data’s good, I want it richer. I don’t settle at ‘fine.’”

Scope

What she owns. What she leaves off her plate.

Owning everything is a recipe for owning nothing. Kelli’s discipline is what stays on her plate — and what stays off it.

The SimplyCodes merchant catalog

owns

Its quality gate and its backend — what counts as a clean, complete merchant record.

The catalog behind the pages that fund the company has to fill and check itself without manual sweeping. That is the job.

The content-operations team

leads

The team that has run the catalog by hand; her job is converting that work into systems.

She is the team’s point of contact on big decisions, because she is the one who answers for the catalog.

Merchant discovery

owns

Finding and adding high-demand merchants the catalog is missing.

Built to find a gap automatically, rather than wait for someone to notice one.

Revenue and the affiliate networks

owns

Relationships, rates, broken links, revenue tracking.

Runs her own commission-data queries to catch a broken affiliate link before it costs a revenue report.

SimplyCodes as a product

leaves off

The page experience, the search strategy, and the site’s authority sit with a different owner.

Her plate is the catalog underneath, not the product on top. One operator, one accountable layer.

Silent misses

leaves off

Anything she committed to but can’t carry alone.

She won’t carry a miss forward in silence. She escalates early instead.

What sets her apart

Combinations that are rare individually. Unusual to find in one operator.

The operations lead who is also the QA

Most operations leads hand QA to someone else. Kelli QAs whatever her automation touches herself — including surfaces she no longer runs day to day.

Library science running a commerce catalog

The library-science background isn’t decorative — it’s structural. Classification, retrieval, and findability are the underlying physics of what makes a merchant record clean enough to clear the gate.

Reads the commission data, not just the dashboard

Runs her own queries against commission data to find a broken affiliate link before it ever shows up in a revenue report.

Decision speed without recklessness

Decides fast and doesn’t second-guess. If the call turns out wrong, she fixes it and moves on.

Turns manual work into systems, on purpose

Writes down every process the team runs, then decides which become agent-run and which get deliberately retired — rather than automating for its own sake.

Escalates instead of absorbing

Won’t quietly absorb a new ask that threatens the automation work. She says so, instead of carrying it silently.

Role and background on this page are independently verifiable — her career history is public on LinkedIn. See the record →
The through-line

Spot the failure points early. Make the call fast. If you’re on it, it gets done. The catalog behind the pages that fund the company has to fill and check itself, building that is the work.

Product.ai builds with operators like Kelli — people who own a system end to end and catch what others miss. See open roles →

Get in touch with Kelli See the team