Day 31 of building DocuPulse AI. Simple question a client will always ask: "what does this cost t...Day 31 of building DocuPulse AI. Simple question a client will always ask: "what does this cost t...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Day 31 of building DocuPulse AI.
Simple question a client will always ask: "what does this cost to run?" Until today my honest answer was "…I'm not sure." Not good enough.
So now every AI query the system makes logs its token usage and calculates the exact cost. Turns out it's about a sixth of a cent per question — roughly a dollar or two a month for a thousand queries. Now I can answer the question with a number instead of a guess.
The bug that ate my time was almost funny: AI prices are quoted "per million tokens," like $2.50. I'd written the price as a per-single-token number instead — $0.0000025 — AND divided by a million in my formula. Did the same division twice. Every cost came out a million times too small, logging as $0.00. The fix was one decision: bake the "per million" into the price OR into the formula, never both.
Small lesson, but it's the whole discipline of this kind of work — a system that silently reports $0.00 looks like it's working. You only catch it if you stop and ask "does this number actually make sense?"
#AIEngineering #Laravel #BackendEngineering #BuildInPublic
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started