Frequently Asked Questions

That's me. As a digital product architect, I help turn an idea into a working product. From the first decisions to launch, strategy, user experience and development stay in one pair of hands. I've worked on digital products for more than a decade, and I'm building two of my own along the way: theuxbites and Modulyo.

I live in Austria, but most of my client work happens remotely, so it doesn't matter where you are. I work in English and in Hungarian, whichever suits you.

The cheapest test is a conversation. Find at least five people you think would need what you have in mind, and ask how they handle it today. Don't pitch your idea; listen to what they do now. If they already spend time or money on something that deals with the problem, that's a good sign: the need is real.

Yes, that's what I built Modulyo for. It takes you through your idea one question at a time, and at the end you have a clear plan.

My own tool that reviews your website and tells you, in plain words, what to fix first. Instead of a long list of problems, you get them in order, each one explained. Three audits a month are free.

My own tool for people who want to start a business but are still working out what it should be. It guides your thinking step by step and leaves you with a worked-out plan.

There is, it's called "Your first automation". For five days you get one email from me a day, each about 15 to 20 minutes of work. By the end, one of your tasks runs without you, built with the AI assistant you already use.

The same things a technical co-founder would decide: how the system is built, what the user experience should be, how the production code gets written, and what automation keeps it running. The difference is in how we work together. It isn't an open-ended engagement but a clearly defined package, with the scope, price and end date agreed up front.

Solo founders and small teams who need a complete digital product but don't want to, or can't, keep a development team of their own. Most are validating an idea or in early growth, working on their first SaaS product, an internal tool or a platform for their customers.

All prices are on the site, so you don't need to book a call to find out. A Product Clarity Day and an AI Clarity Day are €1,500 each, and a Product Audit is €4,500. An Automation Build starts at €12,000 and a Product Build at €18,000. The Clarity Days and the Audit have a fixed price because their scope is fixed. The Builds have a starting price because every project is genuinely different, and we agree the exact amount before any work begins.

A Product Build takes six weeks, an Automation Build four. We fix this up front; it doesn't emerge along the way. The work runs in two-week phases, and at the end of each you decide whether we continue, so you're never stuck for weeks in something that isn't working. If we first need to settle what to build, that's what a Product Clarity Day is for. Auditing a product that's already live, the Product Audit, takes two weeks.

A prototype is a clickable design or demo for trying out an idea, with no working system behind it. An MVP (Minimum Viable Product) is real software: real data, real sign-in and working flows that your users actually use. I build MVPs.

Fully remotely, and it works well: I work with founders across Europe and beyond. We talk through the important decisions on regular video calls, and in between we stay in touch in writing and with short video messages (in Notion and Loom), so not everything needs a meeting. Neither of us needs an office.

Most often Next.js, Supabase, Sanity, Tailwind CSS and Vercel, and Swift for mobile apps. I chose them because they let me move fast, they run reliably in production, and they stay easy to maintain years later. When a project needs something else, I work with other tools from the modern JavaScript ecosystem too.

It means AI tools such as Claude Code or Cursor help write, review and reshape the code. That makes building much faster than coding by hand. It doesn't do the thinking, though: I still decide what we build and what we don't, what can wait, and how the system will cope as it grows.

Yes. A Build runs the same way whether you have a team or not. A Product Audit is often the easiest way in: your developers get a ranked list and a roadmap they can import into their own tools and start on the next day. We work best together when the product decisions stay with you, and the architecture and the building stay with me.

If you like, I stay on as your Product Partner. Most people keep two days a month: €2,000 a month, cancellable monthly after the first three months. That covers small features, a second opinion before important decisions, and a monthly look at the numbers together. We book the time in advance, so it stays predictable for both of us. It works even if I didn't build the product.