Need a digital product built without a full team?
I am a digital product architect. I build my own software products, I work with founders and small teams through the fixed-scope packages below, and I join larger engagements as an embedded architect alongside agencies and partners.
The packages cover two things: building a digital product without assembling a team around it, and working out what to automate before the wrong things go to a machine. Each one has a fixed scope, a published price, and a date it ends.
What does a digital product architect actually do?
A digital product architect does what a technical co-founder does, without the equity, the payroll, or the hiring process. I take a product from idea to working software: defining the architecture, designing the UX, writing the code, and automating the workflows that keep it running.
Four layers built over more than a decade sit behind that: analytical thinking from business analysis, user empathy from UX design, design-to-code fluency from no-code building, and full-stack delivery through AI-assisted development. One person owns the whole path, so nothing is lost in the handover between a strategist, a designer, and a developer.
Because one person owns the whole path, the scope of a piece of work is knowable before it starts. That is why the work comes as three fixed-scope packages rather than open-ended consulting: a day to decide what to build, two weeks to audit a product that is already live, and four or six weeks to build it.
Why fixed scope: I work alone, with AI as my team. That lets me price the outcome instead of my hours.
What type of digital builder are you?
Answer 10 quick questions and discover your Digital Persona, then see exactly how I can help you move forward.
What should you automate, and what should you keep?
Pick the tasks that fill your week and get three lists: what to automate, what to automate with your approval, and what to keep. A few minutes, no email needed.
Product Partner: what happens after launch?
Most founders keep two days a month after the launch. Small features, decisions worth a second opinion, a monthly review of what the numbers are telling you. Booked in advance, so the work stays calm on both sides.
Product Partner · 2 days a month · €2,000 · minimum 3 months
For agencies and teams
I also work as part of existing teams on bigger programmes: data platforms and complex enterprise systems, in international settings. There I take a slice of the work, as large as it needs to be. It is agreed individually, alongside the four packages above.
Recent work: Magyar Telekom, GLS, and others.
Which package should you start with, and what comes after?
Start where the uncertainty is. If you do not know what to build, that is a Product Clarity Day. If you do not know what to automate, that is an AI Clarity Day. If it is built and the numbers are wrong, that is a Product Audit. If you already know what you need, that is a Build. None of them requires the one before it.
Ways in
You are shaping an idea in Modulyo
My app for turning a business idea into a structured plan.
A Product Clarity Day settles what to build first, what to leave out, and what the first version realistically costs.
You ran a scan on theuxbites
My tool for finding UX and performance problems on a live site.
A Product Audit turns that scan into a ranked plan, with your three most important user flows walked by hand.
You came out of a workshop or a talk
Either Clarity Day is the smallest paid step, and both end with a written decision you can act on with me or without me.
Someone on your team does the same job by hand
An AI Clarity Day maps that work as it runs today, then names the first process worth automating.
What comes after
After a Product Clarity Day
You leave with the decision in writing. A product that is already live usually goes to a Product Audit next. A new one goes straight to a Build.
After an AI Clarity Day
The decision brief puts the processes in order. An Automation Build turns the first one into a working system, or your own team takes it from here.
After a Product Audit
You have a ranked list and a roadmap your developers can import. A Build implements what the audit marked critical, or you take the roadmap in house and stop here.
After a Build
The software is yours, documented, and it runs without me. Keeping two days a month on it afterwards is a choice, not a dependency.
How I build
Next.js, Supabase, Swift, Webflow, Framer, and AI assisted development across all of it. More than a decade as a business analyst, then a UX designer, then a no code builder, now this. The stack follows the problem, not the other way around.
How I work
Fixed scope, two week phases, no crunch. I build systems that run at machine speed without asking a human to. You get something you can operate, not something that needs a hero to keep it alive.
Questions
Same price, same format, different subject. A Product Clarity Day decides what to build: what goes into version one, and what it realistically costs. An AI Clarity Day decides what to automate: which parts of your operation should become a system, and which stay human. Both are €1,500 for one day, and the full €1,500 comes off a Product Audit or a Build booked within 30 days of the session. That credit applies once.
Start with a Clarity Day. If what you need turns out to be something else, I will tell you, and the day still leaves you with a decision brief you can hand to anyone.
Yes, and openly. AI writes code, runs scans, and drafts documents faster than any team I could hire. What it does not do is decide what to build or which problem matters first. AI collapsed the cost of producing. It did not touch the cost of being wrong. That is what you are paying me to reduce.
Because you should not carry the risk of how long something takes me. A fixed price means we agree on the outcome, not on my hours.
You deal directly with the person writing the code. There is no account manager in between, and no brief handed from a strategist to a designer to a developer. I own the architecture, the UX, and the delivery. The scope, the price, and the end date are fixed before we start. What an agency has that I do not is capacity. I take one Build at a time.
Yes. theuxbites.com runs an automated audit of your site for a subscription. Many people start there and only book time with me once they know what they are looking at.
I run an Austrian sole proprietorship and work across the DACH region and remotely in English. Most clients are founders, small product teams, and agencies.
How do I build a real product without a full team?
Architecture, UX and engineering in one pair of hands.
One person carries the decisions from idea to live product, so nothing gets lost in the handoffs between strategist, designer and developer. More than a decade of business analysis, UX and engineering sits behind it, and I always start with the same question: who is this really for, and what do they need?
How do I ship faster without sacrificing quality?
AI does the execution. The judgment stays with me.
With AI-assisted development (Next.js, Supabase, Claude Code) we get in weeks to where it used to take months. But speed only counts when it takes you in the right direction. So I spend the speed on the code, and I keep the judgment in my own hands.
How do I go to market without building the wrong thing?
The right decision first, then the build.
Before anything gets built, we decide together what's worth building, what to leave out, and in what order. That way the first version already serves real users, and the automation that follows gives you time back instead of adding weight.
How do I build without burning out?
A sustainable pace, not a 60-hour week.
Nobody makes good decisions while running on empty. I work in fixed scopes and two-week phases, and hand over systems that run without you, not ones that need a hero. I build my own business the same way, and on the blog I write about what works and what doesn't.
My Favorite Success Stories
A few hand-picked projects I loved designing and building: from automation to headless commerce and AI-assisted tools.
Virág Sárosdi
Special Education Teacher & Logopedist, Founder of Skillo
Working with Dávid is a fantastic experience. He guides you through every step of the process with precision and consistently meets every deadline. Most importantly, the quality of the work he delivers is exactly what you envision. While our first project together was the redesign of my website, I am certain that we will collaborate on many more in the future!
Bernadett Gaál
Web Designer
Wonderful and meticulous work, with thorough documentation for those who are completely new to Figma or just getting to know it. All my respect, David, I can only congratulate you for putting so much energy and valuable information into the freebie! You've provided enormous help for web design projects because finally, there's no need to spend hours surfing the community when I want to speed up the design process! Thanks!
Virag Guesthouse
Premium guesthouse in Tokaj-Hegyalja, Hungary
David is a reliable, precise, and professional expert. Throughout the entire process, he handled our needs with flexibility, patiently addressing our many questions and requests while explaining the technical background each time. His kindness, approachability, and the resulting smooth communication greatly contributed to the perfect end result!
Antal Dittrich
Co-Founder & CEO, Actlico Hungary
From David, we received much more than tasteful design and beautiful plans for the user interfaces. A complex system design. The precise, detailed, and logical elaboration of our sometimes vague or superficial ideas, all accompanied by endless patience, flexibility, sensitivity to problems, and a good mood. Thank you.
Zoltan Megyesi
CTO, CTL Software
Highly qualified designer with a keen eye and dedication for a good user experience. Easy to work with through his good communication skills, and great toolset.
Let's Build Your Digital Future
Whether you need something built, a system automated, strategic product advice, or a perspective on staying grounded while building at speed: let's talk. I bring more than a decade of thinking about what makes digital products work, for the people who use them and for the person building them.