Hi, I'm Eddie.
I built Veyl because I needed it.

So I started listening more

Making a conscious effort to really listen helped a lot. But I still wished I had something quietly beside me that understood the conversation and could help when I needed it.

Not something that would take over the meeting, just something that could help me stay present, keep track of what mattered, and move the conversation forward when I needed a next line.

So I built Veyl

Veyl listens alongside me and keeps track of the conversation. If I lose my train of thought, I can quickly ask it where we are, what I may have missed, or what might be worth asking next.

I don't need to spend the whole meeting staring at suggestions. The help is simply there when I need it.

There are other meeting tools out there, and I don't claim to have invented this idea. But I wanted something I could shape around the way I actually communicate. If something important was missing, I wanted the freedom to improve it, rather than wait and hope another company eventually would.

Built personally. Used personally.

Veyl is independently built by me, and I use it in my own meetings every day.

I originally made it for myself. But I believed that if it helped me feel clearer and more confident in conversations, it might help someone else too.

That's still how I approach it today: build something genuinely useful, keep it honest, and improve it through real use, not hype.

We already have a few users despite no marketing at all. That means more to me than any launch campaign.