Founder Story

Why this tool exists

QST exists because I was losing sales, not due to a lack of products or demand, but because I couldn’t force myself to duplicate work I’d already done.

Every product lived in Shopify. Every additional marketplace demanded the same work again: rewritten titles, reformatted descriptions, resized images, trimmed text, policy checks and manual uploads. I knew the value of the listings, but the repetition was exhausting. Opportunities were slipping away simply because the process asked too much cognitive effort for too little return.

Part of that friction comes from ADHD, but it isn’t unique to ADHD. Many creators struggle when systems demand repetition without reward.

I didn’t need more motivation. I needed less friction.

The original intent (and the shift)

At first, this was meant to be a small personal helper just for me.

But once I experienced what even a basic version could do, and how much mental load disappeared when duplication was removed, it became obvious that this problem wasn’t personal. It was systemic.

If I could build something simple enough to understand, powerful enough to matter, and safe enough to trust, then other creators struggling with the same problem could benefit too.

If I kept the price fair, a genuine “no-brainer”, it could become sustainable, profitable and eventually allow me to leave a job that pulls time away from my family.

At that point, keeping it to myself no longer made sense.

The core constraint

From the beginning, one rule was absolute: Shopify is read-only. It is the source of truth and never something QST edits directly.

That decision shaped everything: no accidental overwrites, no hidden side effects and no “what changed and why?” moments. Edits happen locally. You see them. You understand them. You decide where they go.

From helper to application

What began as a Python script quickly exposed deeper complexity: variants vs products, images and pricing logic, platform limits, and subtle rules that cause silent failures.

Rather than chase shortcuts, the tool grew carefully: viewing products clearly, exporting clean text, creating Etsy and Vinted-ready packs, handling character limits and image resizing, and supporting bulk workflows that genuinely reduce effort.

The breaking points

There were two points where the project nearly stalled completely: getting eBay working, and OAuth.

eBay is not “upload a product and done.” It involves policies, categories, item specifics, OAuth flows, token expiry, sequential listing logic and errors that rarely explain what went wrong.

Instead of backing away, I set up a full developer environment and implemented real production flows. That was the moment the project stopped being a helper and became a real tool.

The line in the sand

QST exists to save creators time, mental energy and lost opportunities without taking control away from them. If it ever stops being simple, powerful and safe, it stops being the right tool.