If you’ve been reading my posts for a while, you’ve probably seen me mention Crompt AI here and there while discussing model comparisons and prompt workflows.
I recently joined Crompt AI in a meaningful role (AI Product Strategist).
At a practical level, Crompt AI sits between developers and today’s leading AI models. Instead of committing to a single provider, it brings multiple models into one place for text and image generation, so you can experiment, compare outputs, and choose what actually fits your use case. For builders who care about reasoning quality, structure, and output differences, that flexibility matters.
Over time, I found myself referencing it not just as a tool, but as part of how I think about working with AI systems. Joining felt like a natural extension of that. I’m interested in reducing friction between ideas and execution, and in helping developers make clearer decisions about which models to use and why.
I’ll be sharing more about what I’m building and learning along the way. If you’re experimenting with multi-model workflows or thinking about how to structure AI into your stack, you’ll probably find the journey relevant.
-Leena:)
Top comments (3)
Congrats Leena,
Much More excited to see what this amazing product does!🤗
So happy for you😍😘
Thanks Olivia
Congratulations!
I've been reading your posts.
Would love to chat about Crompt and your practice in general - what's the best way to reach you?
I couldn't find you on Linkedin.