Frequently Asked Questions
Common questions from founders and small teams before working with a Digital Product Architect.
What do founders typically ask before we start working together?
These are the questions I hear most often from solo founders and small teams who are considering building a digital product. If your question is not here, the contact page is the right next step. I respond to every genuine enquiry.
A Digital Product Architect makes the calls a technical co-founder would make: architecture, UX, production code, and the automation that keeps it running. The difference here is how you buy it. It comes as a named package with a fixed scope, a fixed price and a date it ends, rather than as an open ended engagement.
Solo founders and small teams who need a complete digital product built without assembling a full development team. Most of my clients are at the validation or early-growth stage, building their first SaaS, internal tool, or customer-facing platform.
The prices are published, so you do not need a call to find them out. A Product Clarity Day is EUR 1,500. A Product Audit is EUR 4,500. An Automation Build starts at EUR 12,000 and a Product Build at EUR 18,000. The Clarity Day and the Audit are fixed because their scope is fixed. Build starts from a floor because scope genuinely varies there, and the exact number is agreed before any work begins.
Every package has a fixed duration, so this is not a negotiation. A Clarity Day is one day. A Product Audit is two weeks. An Automation Build is four weeks and a Product Build is six weeks. Build work runs in two week phases, and at the end of each phase you decide whether to continue, so you are never six weeks deep in something that stopped working after two.
A prototype is a mockup or click-through demo used to test ideas. An MVP (Minimum Viable Product) is working software with real data, real authentication, and real workflows that actual users can use. I build MVPs, not prototypes.
Yes, fully remote. I work with founders across Europe and beyond. All collaboration happens asynchronously via Notion, Loom, and regular video calls — no office required on either side.
Primarily Swift, Next.js, Supabase, Sanity CMS, Tailwind CSS, and Vercel. The stack is chosen for development speed, production reliability, and long-term maintainability. Depending on the project, I also work with other tools in the modern JavaScript ecosystem.
AI-assisted development uses tools like Claude Code and Cursor to write, review, and refactor code significantly faster than traditional manual coding. It accelerates the execution layer without replacing architectural judgment or UX thinking — you still need to know what to build and why.
Yes. A Build runs the same way whether you have a team or not, and a Product Audit is often the easiest way in, because it hands your developers a ranked roadmap they can import and start on. I am most effective when you own the product decisions and I own the architecture and the execution.
Most founders keep two days a month as a Product Partner: EUR 2,000 per month, minimum three months, then monthly. Small features, decisions worth a second opinion, and a monthly review of what the numbers are telling you. The time is booked in advance rather than left open ended, which keeps the work calm on both sides.
Ready to ship the right product - fast enough to matter?
Whether you need an MVP built, a workflow automated, or someone to cut through the noise and make the right call: let's talk. One person. Full stack. 11 years of judgment.