Building MitraAI | Software Engineer @Quantiphi
I tweet actionable insights on #AI, #Startups, and #Growth.
Follow for your daily signal in the tech world.
๐ Meet Mitra AI: The AI Sales Assistant that embeds into YOUR website!
Helps customers find the BEST product from your catalogue in seconds. No more guessworkโboost conversions like magic!
Who's ready?
#AISales#EcommerceIndia#Beta
From discovering Product Hunt for products to launching one... it's been a journey.
Check out @askmitraai on @ProductHunt and grab up to 2 months free trial: https://t.co/nKldNZZPid
๐จ WE ARE LIVE ON @ProductHunt !
Meet Mitra AI: The AI Sales Assistant that turns passive browsers into active buyers.
- Intent-Based Search ๐ง
- Instant Shopify/Woo Integration ๐
- Abandoned Cart Recovery ๐
Check & grab your 30-Day Free Trial: ๐https://t.co/S3vNUyW2XA
Why join? Early testers shape Mitra .
First 10 get exclusive perks. Spots filling fastโact now!
DM for signup. RT if you're building e-com! ๐
@Shopify @WooCommerceIndia
๐ Meet Mitra AI: The AI Sales Assistant that embeds into YOUR website!
Helps customers find the BEST product from your catalogue in seconds. No more guessworkโboost conversions like magic!
Who's ready?
#AISales#EcommerceIndia#Beta
Beta launch NOW! Seeking 10 e-com owners for FREE testing.
โ Lifetime access
โ Custom tweaks
โ Priority support
If you have a product catalogue, DM "BETA" or reply with your site URL. Let's make sales smarter!
#BetaTestersWanted#SaaS
PostgreSQL vs MongoDB vs Redis for your next project
The answer depends on ONE questionโฆ
(Most developers choose wrong โ and regret it 6 months later.)
๐งต My framework for choosing the right database:
#PostgreSQL#MongoDB#Redis#Backend#Scaling
While working on ScrollOs, I noticed something odd:
Power users didnโt ask for features.
They asked for defaults.
Curious how much UX is really about removing choice.
As a dev, my output improved when I:
- reused the same project structure
- reused the same deployment flow
- reused the same debugging steps
Less creativity.
More shipping.
Switching to search-first queries changed everything:
- candidate emails dropped by ~95%
- sync finished in seconds
- same infra, different architecture
The biggest win wasnโt speed.
It was not doing work at all.
When we first tested ScrollOS on real inboxes,
the naive approach failed immediately.
A user with ~18k emails:
- full fetch attempt โ timeout at ~12s
- API quota burned fast
- zero usable output