Product and system logic
Define the user, business rules, scope and sequence before code hardens the wrong idea.
About Maco
A founder who builds the system—not just the pitch.
Two decades across the web, product, creative work, acquisition and entrepreneurship have produced a practical bias: understand the operation, remove the constraint, ship something the business can own.
Chiang Mai, ThailandBuilding on the web since 2005
- 012005
I grew up on the web, not inside a developer job title.
At eleven, I started taking raw HTML and CSS pages apart and rebuilding them. I did not learn the web inside a corporate IT department; I grew into it through curiosity, real projects and constant experimentation.
I worked through the static web, custom WordPress systems and ecommerce, then into Next.js product platforms and AI-assisted workflows. That continuity makes it easier to separate lasting product logic from whichever tool happens to be fashionable this year.
- 022010—
Product, creative, technology and acquisition belong in the same decision loop.
For more than a decade, I worked across UX, commercial photography, Photoshop, Illustrator and Premiere Pro, Google, Meta and TikTok campaigns, and full-stack development.
That range matters because a product decision changes the interface, a technical choice changes the operation, and the message changes acquisition. Instead of five separate handoffs, I can keep the commercial intent intact from the first sketch to production.
- 032017—
Operating my own businesses taught me the consequences.
From 2017 to 2020, I founded and operated Alagsor Live Room Escape Game in Budapest, building everything from the physical puzzles and game logic to the brand and booking system. For more than a decade, I also shaped the digital strategy and high-value enquiry systems behind Rugexpert and Varga Antik.
My own SaaS products, marketplaces and Hello Europe, launched in Chiang Mai in 2026, taught me that decisions show up in real customers, daily operations, support load and revenue. I bring that owner-operator responsibility to client work as well.
- 04NOW
MacoLabs is a model of accountability.
The person mapping the business problem also designs the interface, data model and integrations, then carries the system into production. Directness is not a style choice; it is quality control.
That is why I take on a limited number of clearly scoped engagements and work directly with the decision-maker. The aim is not to ship more features. It is to build a system that changes how the business operates and remains genuinely ownable after launch.
One decision loop
The work crosses disciplines because the business problem does.
I do not sell five disconnected roles. I connect them so the meaning of an important decision does not get lost between strategy, design, engineering and launch.
Creative direction and UX
Shape hierarchy, interaction and visual systems so the product is understood and trusted.
Full-stack and AI
Build interface, data model, integrations and controlled AI workflows as one production system.
Acquisition and iteration
Connect launch, measurement and customer feedback to the next product decision.
The owned ecosystem
I do not only hand over client systems. I operate products of my own.
Craft and stewardship
Build honestly. Make it dependable. Leave something useful behind.
As a Christian, a husband and a father of three, I see engineering as stewardship: tell the truth about trade-offs, keep promises realistic, work carefully and create durable value for the client.
Direct
No account manager or relay chain that loses decision context.
Commercial
The technical solution must serve an outcome or make the operation materially easier.
Ownable
Standard technology, documented systems and a real path to handover.
Websites · Online stores · Custom software
If you need an accountable product partner—not another anonymous supplier—let's talk.
Based on the brief, I will tell you honestly whether I am a good fit and what the sensible next step should be.
Brief your project