Overview

מכינת עמי-חי is a ai platform project we designed and built. This case study walks through our approach, the decisions we made, and what we learned along the way.

The Challenge

AI products live or die by three things: the quality of the underlying model, the clarity of the interface around it, and the speed of the response. For מכינת עמי-חי, we had to design a product that respects all three.

Our Approach

We began by defining the user’s core question – what are they actually trying to achieve? – and worked backwards to shape the UX around that. We integrated LLM / generative AI services with fallbacks, guardrails, and cost controls, then wrapped the whole experience in a clean UI that keeps the user focused on the outcome, not the mechanics.

Technical Decisions

Architecturally, the platform relies on tightly scoped API calls, prompt engineering that’s version controlled, and infrastructure that can absorb traffic spikes. Where relevant, we integrated third-party providers (OpenAI, Anthropic, and others) and orchestrated them behind a single, coherent user-facing interface.

Core stack: Wix, custom Velo code, integrations.

Design Decisions

AI can feel intimidating. Our design brief was the opposite: make it feel obvious. Every screen answers ‘what happens next?’ before the user has to ask, and every state (loading, error, empty, success) is designed intentionally.

Outcome

מכינת עמי-חי demonstrates that a well-designed AI wrapper is not a thin layer – it’s the product. Getting the human-in-the-loop details right is what turns a technical capability into a business.

What We Learned

Working on מכינת עמי-חי reinforced a few beliefs we hold across every project: the interface is not the product – the outcome is; performance is a feature; and design details compound over time. Small choices about spacing, transitions, and error states add up to a product that people actually enjoy using.

Ready to build something like מכינת עמי-חי?

We work with founders, product teams, and organizations building software that people actually use. If you have an idea, a rough prototype, or an existing product that needs a rebuild – we should talk.