Daniel Dines co-founded UiPath from a bootstrapped Romanian startup to a public company before starting Crew Capital, giving him a rare perspective as a non-US Eastern European founder who went from earning roughly a dollar a day to becoming one of Romania's most successful tech entrepreneurs. He brings an automation-first worldview to venture investing while continuing to actively run UiPath, so portfolio founders get real-time advice from someone currently scaling a large software company rather than just retrospective stories.

• Deep interest in the evolution of automation toward agentic AI, specifically how software agents can autonomously execute complex tasks rather than just following simple rules. He frequently highlights advancements in this space, such as integrating new computer use models from major tech partners to expand what autonomous systems can achieve in a business setting.
• A pragmatic view of software engineering that prioritizes business logic and architecture over raw coding speed. He has shared that for seasoned developers, writing code is a small fraction of the work compared to understanding the underlying business problems, noting that AI cannot yet fully replace the nuanced architectural thinking required for complex systems.
• Emphasis on enterprise-grade reliability, security, and auditability as non-negotiable prerequisites for adopting AI. He argues that large organizations will only embrace speed and intelligence if they retain control and transparency, citing scalability as the primary factor that moves a technology from a cool experiment to a transformative business tool.
• Respect for the grit required to bootstrap a company, often referencing his own long journey of outsourcing work just to keep the lights on before finding product-market fit. He values persistence and humility, drawing parallels between the discipline of elite athletes and the resilience needed to build a global tech company from modest beginnings in Eastern Europe.
• Strong belief in customer-led product development rather than building for the sake of technology. He attributes his own major turning points to a shift in mindset where the team stopped building features that appealed to them as developers and started listening strictly to what clients needed to move beyond proof-of-concept phases.