Platera: waste and cost control for restaurant kitchens
My own restaurant operations system: daily logs, waste tracking, weekly stock counts, recipes and cost control, with separate staff and admin logins.
The live dashboard is private, so the cover shows example data.
AI Fashion Shopping & Outfit Recommendation Platform
Designed a modern AI-powered fashion shopping platform that helps users discover personalized outfits and shop smarter.
The concept combines AI-driven outfit recommendations, style matching, virtual outfit previews, and a personalized wardrobe experience in a clean, premium interface.
Before you add AI to your product, find the screen where your users already copy and paste.
That's usually where the real AI feature lives. Not a chatbot in the corner, but a step people already do by hand: summarising a ticket, drafting a reply, tagging an upload, pulling fields out of a PDF.
Here's the order I follow when a founder asks me to add AI to an existing SaaS:
1. Pick one workflow, not "AI everywhere." Watch where users leave your app to paste something into ChatGPT and come back. That round trip is your feature.
2. Keep the model behind your own API. One service owns prompts, retries, logging and cost limits, so you can switch providers without touching the frontend.
3. Make it tenant-aware from day one. Each customer's data, prompts and usage stay scoped to their account, or the first enterprise security review will stop you.
4. Ship a draft, not a decision. Let the AI suggest and the user approve. You earn trust and get real feedback before you automate anything.
5. Measure accepted output, not tokens. If users rewrite most of what it produces, the prompt or the context is wrong, and that's your real roadmap.
Most AI features that flop didn't fail because of the model. They were bolted onto the wrong step.
What's the one task your users still copy into ChatGPT?