Daniel Lewis and Gregory Kan founded Eddy Works in 2023 after a decade of running agencies and consulting as web developers inside other organizations' operations. They were not chasing a trend. Client after client, they were hired to fix the same coordination gap: work moving between people with no shared map of what happened or what came next. Eddy is the platform they wished had existed on every engagement.
2013–2023
Dan and Greg built bespoke coordination tools for clients across education, compliance, and operations: custom onboarding flows, compliance workflows, operational handoffs. The industries changed. The shape of the problem did not.
2023
Eddy Works Limited incorporated. The goal: a platform that lets people design, run, and improve multi-person processes without needing developers.
2023–2025
The product evolves from a simple linear form builder into a map-first process platform with branching logic, role-based coordination, and structured data capture. The team grows across product, design, engineering, and communications.
2025
The Work Environment Week goes live. 145 employees, 86.4% satisfaction, and 10+ processes now running across compliance, IT, procurement, and data governance.
2026
Tightening the platform, preparing for public launch and investment round.
Co-founder
Gothenburg, Sweden
Dan is co-founder of Eddy Works. He trained in architecture: how designed environments shape how people live and work together. At Eddy his work is connective: keeping strategy, resources, and momentum coherent across the company. Years of watching important work depend on processes held in people’s heads left him noticing that games were often better at roles, states, and what comes next. Eddy is the tool he wanted for that problem.
Co-founder
Wellington, New Zealand
Greg is co-founder of Eddy Works and Eddy’s lead developer and architect. He has a background in literature, philosophy, and computer science, and nearly a decade building software with Dan as a developer and consultant. What drives him is the coordination and collaboration problem, which he believes tech as an industry has yet to solve in a robust or impactful way.
Technical Lead
Wellington, New Zealand
Elise is a senior developer with a soft spot for accessibility, responsivity and design systems, as well as a track record leading and teaching other developers. At Eddy she tightens the bolts on the app, and adds polish and finesse to make it a first-class experience. The challenges of a general-purpose tool excite her because it has the vast potential to improve people's working lives.
Media & Marketing
Madrid, Spain
Joriam works across media and content creation at Eddy, where he helps shape voice and storytelling, kicked off video production, and keeps messaging clear across channels. He uses media to build strong communities and is excited by Eddy’s narrative potential: turning processes into stories, even adventures, that people can move through.
Design
Gothenburg, Sweden
William is a graphic designer and art director from Gothenburg, shaped by branding, campaigns, and visual production across agency floors and freelance briefs. At Eddy he owns how the product looks and feels and the visual language we use to talk to the world. He is drawn to making messy coordination visible and intuitive, not merely functional.
Communications
Gothenburg, Sweden
Sofia comes from film and from communications work that spans content, education, and research, and still makes film in Gothenburg. At Eddy she handles stakeholder communications: newsletters, case studies, and related content. She is drawn to Eddy as a different approach to administrative work, providing structure with enough flexibility for people to shape a process to their own needs.
Coordination is invisible labor until something breaks. Then everyone wonders why reminders multiplied, why the handoff was missed, why nobody can find the record. Our product thesis is blunt: honor that labor with structure that makes the next step obvious, captures the work as it happens, and turns every completed process into data you can learn from.
We run Eddy the way we think organizations should run. The team spans Wellington, Gothenburg, and Madrid, which means async coordination and proper handovers aren't optional for us. Clear writing, recorded walkthroughs, and deliberate handoffs are how we stay aligned across timezones. That's not a workaround. It's the same discipline the product is designed to bring to other organizations.
Our stakeholder substack is where hypotheses stay messy before they harden into roadmap. Read along if you enjoy unpicking institutional theatre alongside us.
Browse the process templates that show how Eddy turns handoffs, roles, and records into something teams can actually run.
