Product Manager, SimplyCodes Website · Product.ai
Owns the entire SimplyCodes website — the store pages, the merchant landing pages, the templates, and the structured data Google reads. Makes the call on what ships, when, and with what level of risk.
The operator who catches what’s about to break before it breaks. She finds the problems at the seams between engineering, SEO, merchant data, and the customer experience — then steps in herself when waiting on someone else would cost the launch.
The PM who owns all of SimplyCodes — the product that funds the rest of the company — and catches what’s about to break before it breaks.
Owns the seam where engineering, SEO, merchant data, and the customer experience meet. Without someone holding that seam, pipelines fragment and things stop shipping on time.
Meticulous review before launch — mobile, desktop, the structured-data validators, the search-result preview tools. Catches issues at the gate, not in the field.
Reads what Google reads. Caught a missing product-markup gap before it shipped — one edit, no fabricated data, validated green.
Builds the case, routes it with evidence, and takes the call. She decides fast and adjusts if the call turns out wrong.
Runs queries against commission data to catch broken links early — before they surface in a revenue report. Monitors the live pages so nothing drops silently.
Tweaks prompts, audits the output, and makes generated copy read less templated. She picked this skill up on the job — the same way she picked up QA and front-end fluency.
Kelli came into the company as a taxonomist — the person who decides how things are categorized so they can be found. The website grew up around her, and she grew with it: into QA, into front-end product instincts, into the structured-data decisions that govern how Google understands a store page.
The library-science training turned out to be structural, not ornamental. Information classification, retrieval, and findability are the underlying physics of how a commerce surface gets discovered — and of which pages deserve to be indexed at all.
Today she owns the whole surface. She catches what’s about to break before it breaks, makes the call fast, and steps in herself when a launch is stuck. The job title is Product Manager; the substance is the calls and the catches.
What Google reads about a store page is upstream of what shoppers ever find. That’s a library-science problem wearing a commerce hat. Kelli, on the through-line from taxonomy to PM
Owns the convergence across multiple workstreams and steps in herself when waiting on someone else would cost the launch. The PM work — QA, coordination, rollout — is the surface; 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.”
Pre-publish QA on mobile, desktop, and the structured-data validators before anything ships. A missing-markup gap that would have shipped across an entire batch of pages got caught pre-publish and fixed in a single edit.
“I had the audit pressure-tested before handing it off. Eight items became two real fixes, one judgment call, and the rest dropped. Cleaner handoff.”
Runs scans for pages losing search visibility, audits the structured data, and verifies fixes in the live page before she calls it done. The surface lives in what the crawler sees — not what the design intended.
“I was looking into search-traffic droppers one morning. Seven things surfaced from that scan. None of them were on a to-do list.”
Wants to be brought in early on decisions about anything she’s running — so she can speak to it and stand up for the team. 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.”
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.”
“Always making things better. If the data’s good, I want it richer.”
Owning everything is a recipe for owning nothing. Kelli’s discipline is what stays on her plate — and what stays off it.
The full surface — store pages, merchant pages, templates, schema, reveal patterns.
Except the blog, the website is hers. One operator, one accountable surface.
A new template generation, rolling out in tested phases.
Launches the first test set, watches the early results, and makes the scale / tweak / revert call on evidence rather than instinct.
Redirecting ~400K old pages into SimplyCodes behind a quality gate.
A multi-signal quality gate governs which pages earn an index spot — so the migration captures traffic instead of diluting it.
The structured data Google reads about every store page.
Validators, product-vs-brand markup decisions, and a live verify in production before any change is called done.
Routes the work to engineering with traces and fix patterns.
She finds the bug and hands off a clean, pre-pressure-tested fix — she doesn’t write the code herself.
Anything she committed to but can’t carry alone.
She won’t carry a miss forward in silence. She escalates early instead.
Most surface PMs delegate QA or trust the engineering tests. Kelli runs the pre-publish QA herself — mobile, desktop, structured-data validators, live-page verification — because that’s where the catches live.
The library-science background isn’t decorative — it’s structural. Classification, retrieval, and findability are the underlying physics of how Google reads a store page and what the migration’s quality gate actually decides.
Most PMs check the analytics dashboard. Kelli runs scans for pages losing search visibility and finds the handful of real issues that surface — none of which were on anyone’s to-do list.
Decides fast and doesn’t second-guess — paired with the discipline of writing the case up with evidence before routing a direction call for sign-off.
SimplyCodes is the revenue engine that funds Product.ai’s bigger bets. Kelli is the single PM who owns that surface — the seam between today’s cash engine and tomorrow’s category bet sits on her plate.
The stretch she’d take is deeper taxonomy and information-architecture work — alongside the website, not instead of it. A direction that deepens what she already runs, not a pivot away from it.
Catch what’s about to break before it breaks. Make the call fast. If you’re on it, it gets done. The product she owns today funds everything else Product.ai is building — defending it and growing it is the work.
Product.ai builds with operators like Kelli — people who own a surface end to end and catch what others miss. See open roles →