ABOUT
I am Adrian Davies. I build systems where coordination tends to break first, whether that means connectivity infrastructure, fragmented mobility networks, legal-tech interfaces, or the operational layer around ambitious ideas. I am based between Vienna and London.
Most of my work sits somewhere where real-world constraints that make ambitious things hard.
I like problems with ugly edge cases. Cross-border regulation, broken interfaces between institutions, infrastructure bottlenecks, routing logic, adoption under constraint. The more a system touches the real world, the more interesting it usually gets.
This site is not a résumé in disguise. It is a public layer for the work, the thinking, the talks, and the systems I want to keep building over time.
PRINCIPLES
Constraints are usually where the real shape of a problem becomes visible. Regulation, hardware limits, fragmented markets, or missing infrastructure are rarely reasons not to build. They are usually the actual design brief.
I care less about narratives in isolation and more about whether the underlying system actually holds. If something cannot survive contact with operations, policy, logistics, or users, it is probably still just an opinion.
In many of the spaces I care about, regulation is not an external nuisance. It is a design variable. Treating compliance, governance, and legal structure seriously usually creates better products, not worse ones.
A lot of teams are not blocked by lack of ideas. They are blocked by fuzzy thinking, fuzzy language, and fuzzy decisions. Good systems, good strategy, and good communication all benefit from the same discipline.
AREAS
I am interested in how networks behave under stress, outside ideal conditions, and beyond centralized assumptions. Mesh systems, routing logic, resilience, and edge connectivity are recurring themes in my work.
I like technical systems that touch reality. Infrastructure, mobility, networked hardware, real constraints, and the coordination problems that come with operating beyond software alone.
My legal background is not a side note. It shapes how I think about emerging technology, institutional friction, and how products survive in regulated environments.
I enjoy the translation layer between concept and execution. Product direction, systems thinking, operational design, partnerships, and making complex things move in the real world.
QUESTIONS
WHAT ARE YOU WORKING ON NOW
Mostly connectivity, infrastructure, and the systems around getting ambitious things deployed under non-ideal conditions. See the Now page for a short snapshot.
WHAT KINDS OF THINGS DO YOU LIKE HELPING WITH
Hard early-stage problems. Product and strategy questions with real constraints. Connectivity, mobility, legal-tech, market structure, operational design, and situations where a strong thesis needs sharper systems thinking.
DO YOU SPEAK AT EVENTS
Yes. I speak on connectivity, systems, law and emerging technology, building in Europe, and the reality of starting early.
WHY LAW PLUS DEEP TECH
Because a lot of important technical systems do not fail at the demo layer. They fail at regulation, coordination, incentives, or adoption. Law helps locate those pressures.
WHAT ARE YOU OPTIMIZING FOR
Work that compounds. Systems that matter. A higher bar for clarity. Enough range to keep building across technology, institutions, and real infrastructure.