Mobile-first product design, done solo
I help early-stage founders launch usable MVPs — from idea to working product.
This works best if you’re
An early-stage founder building your first product
Have an idea, but no clear product yet
Need to validate fast, not polish endlessly
Want a usable MVP, not slides or a long process
What I deliver
Focused on early-stage startups that need speed, clarity and a real product — not slides.
Mobile-first MVP
Core product flows, UX structure and usable interface — ready to test your idea with real users.
Product discovery
Turning a raw idea into clear product logic: user flows, priorities, scope.
UX/UI design
From wireframes to interactive prototype focused on clarity, usability and speed.
Handoff & launch support
Design ready for development or no-code launch. I stay until it works.
How it works
Clear steps. Clear outcomes.
Short call & scope
We clarify the idea, goals and define a clear scope.
UX Structure
Key flows, logic and priorities — mobile-first.
UI & Prototype
Usable interface and interactive prototype.
Delivery
Ready for development, testing or launch.
Selected case studies
A mix of real projects and self-initiated MVP concepts.
Why solo
One person. Clear responsibility. Faster decisions.
I work solo to keep product decisions fast, clear and focused. You collaborate directly with the person who designs your product — no layers, no handoffs, no noise. This setup works best for early-stage teams who need clarity, speed and a usable MVP — not a heavy process.
Direct collaboration
You work directly with the designer making product decisions.
Clear ownership
One person responsible for quality, scope and outcome.
Less overhead, more speed
No managers, no delays, no unnecessary process.
FAQ
Early-stage products, MVPs and mobile-first interfaces.
If you need speed, clarity and a usable product — we’re a good fit.
With a short call to understand your idea, goals and scope.
No commitments — just clarity.
Most MVPs take 3–6 weeks, depending on scope and complexity.
Pricing is based on scope, not hours.
It’s discussed after the initial call, once the scope is clear.
Yes. I collaborate with developers when needed or hand off everything ready for implementation.