Hey everyone! 👋 I'm building Quotix
by•
Hey everyone! I'm Hisham, a software engineer and founder building Quotix.
I'm interested in the intersection of APIs, AI agents, and automation. One problem I'm exploring is how to keep business logic consistent across different apps and workflows, especially when pricing rules get more complicated.
That's what led me to build Quotix: a shared pricing engine that lets different apps and workflows use the same pricing rules instead of duplicating them everywhere.
I'm joining Product Hunt to connect with other makers, learn how you're building, and share what I'm working on along the way.
Excited to be here! What are you building these days?
8 views
Replies
Welcome Hisham. I build a consumer app that makes songs, and your problem shows up even in a codebase that small. Prices are in credits, the backend is the only thing allowed to charge them, and there is one constant for what a credit is worth that everything else is derived from. But the app also needs the price before it calls the backend, to tell someone they are short before they tap, so the app keeps a mirror of the per song cost, and a mirror is exactly the duplication you describe. Newer prices went the other way: the price of one feature lives in a config document the app reads, so there is nothing to keep in sync. The hard part for a shared engine, I would guess, is not the rules but that question: who is allowed to compute the price, and who is only allowed to display it.