I created ALFRED in 2019 to make a growing collection of tools, automations, and connected services easier to communicate with. The Flow Response provided the software, operations, and people to put the idea into practice, including connecting people with human support while removing identifying details. ALFRED has continued to underpin my software work in different forms ever since.
Year
Context
Role
Focus Areas
ALFRED began as I was getting deeper into automation and exploring what computers could do for individuals and organizations, both digitally and in the physical world. I wanted to humanize that capability: bring different tools and processes together in a form that felt familiar and easy to communicate with.
The Flow Response gave me a real foundation for building it. I had the software platform, operational structure, and people needed to test whether the systems worked, learn from their use, and keep improving them. The platform served a few hundred users, with access through a paid service.
I introduced ALFRED publicly at ETHDenver in 2019. The early version was limited, but it gave me a practical way to explore an idea that has stayed with me: technology should meet people where they are and make useful things easier to do.
ALFRED brought tools, API connections, automations, information, and people together through a more approachable interface. The aim was to make their combined capabilities usable without asking someone to understand all the systems working underneath.
Within The Flow Response, that included identifying patterns in someone's work, life, or struggles, connecting relevant insights, and bringing in a human mentor when support was needed. ALFRED helped route the information and coordinate the exchange, with identifying details removed before they were shared.
Privacy was central to how the support worked. Removing identifying details was intended to help people speak openly, and let a mentor respond to what someone was experiencing without their name, position, or reputation shaping the conversation.
These videos from 2019 demonstrate ALFRED's functionality and the evolution of the system. The first video introduces ALFRED as it was originally conceived, while the second shows how the foundational patterns persisted and evolved in later work.
Building ALFRED in 2019 meant working with more limited tools than I have now. Even then, I was interested in how a familiar, conversational interface could connect people with a much wider range of useful actions and information.
The Flow Response let me test those ideas in an operating platform. I could build functionality, put it in front of people, see whether it worked, and refine the experience as I learned.
That practical foundation mattered as much as the idea itself. ALFRED became a way to keep experimenting with automation and interaction design through software that people were actually using.
Many of the people we worked with were experienced business leaders who could find it difficult to share their struggles. Giving someone a place to be honest meant thinking carefully about what information a mentor needed, and what could reveal the person behind it.
ALFRED could gather information, identify patterns, and bring a human mentor into the process while stripping away identifying details. The person could receive support and continue the exchange without having to make their identity part of the conversation.
The goal was to make vulnerability feel safer and give mentors room to respond on the substance of what was shared. Privacy supported the human relationship at the center of the experience.
The friendly character mattered to me. ALFRED had the energy of a helpful, capable presence, someone you could communicate with easily while a collection of tools and processes worked in the background.
That familiarity was part of humanizing the technology. I wanted people to have a usable way into its capabilities, with less friction between what they needed and the systems that could help.
The name and presentation could take different forms across projects, but the intention remained consistent: make the interaction approachable while connecting the right information, tools, and people behind it.
Since I started building ALFRED, it has powered the software I have built in one form or another. Sometimes the name changed, sometimes the presentation changed, and much of it worked quietly in the background.
The work has continued to connect tools, gather and route information, and make complex capabilities easier for people to use. The early system gave me a foundation I could keep building on as new technology became available.
That continuity is an important part of the project for me. ALFRED grew beyond its first interface and became a recurring approach to how I build software.
The lesson I keep coming back to is to simplify both sides of an interaction: how information comes into a system, and how it comes back to the person using it.
I am interested in creating different ways to gather and communicate information around the individual. People have different needs, habits, and ways of understanding things. The software should be able to adapt to those differences.
What interests me most is technology that can meet an individual exactly where they are. The aim is to reduce friction and aversion, make participation easier, and give the person the best chance of getting something useful from the experience.
Connected information, processes, insights, and people while removing identifying details from the material shared for support.
Brought human mentors into the process and maintained communication and feedback while keeping the person's identity out of the exchange.
Used automation to gather information and surface patterns in someone's work, life, or struggles, supporting the human mentoring process.
Treated privacy as part of the experience, with the goal of helping people share honestly and receive support with less concern about judgment.
Carried the underlying tools and approach into later software projects, under different names and presentations.
Explored ways to gather and communicate information around the individual, simplifying the interaction with connected tools and services.
ALFRED began with my curiosity about what automation could make possible. The part that has stayed with me is the human side: making powerful tools easier to communicate with, giving people room to ask for support, and building technology that adapts to the person using it.