About
Software built for the people who use it.
I’m Patrick Muns, and Lyto is what I do with my evenings. It comes from one conviction I picked up over a decade of running operations in tech: software works when the person using it is the person it’s built for — and it should be priced so a small team can actually have it.
What a decade in ops taught me
I spent ten years in strategy, operations and customer experience at fast-moving tech companies — leading support and operations at companies like Netflix and Navan, and heading support and digital at EVBox. For a good part of that time, my actual job was building the voice of the customer: turning what users and support agents ran into every single day into a triaged product roadmap, then working with engineering and data teams to ship it.
Do that long enough and a pattern becomes impossible to unsee. Software built from real end-user feedback gets used, gets liked, and quietly compounds. Software built from industry trends — by people convinced they can think for the end user — fails: features nobody asked for and nobody touches, vendor stacks configured by consultants at the request of people far from the actual work, and data so fragmented that nobody can trust it to make a decision.
The best software I ever saw wasn’t bought. It was built by internal teams for their own colleagues: close to the user, on one shared database, with data that connected across teams and actually showed where to focus.
So I’m building the opposite
Lyto is that internal-tool idea, turned into a product for small teams. One suite — CRM, helpdesk, projects, invoicing, time, reporting — on one database, so your customer and business data connect instead of fragmenting across six subscriptions and a pile of sync tools. Every feature has to solve a real problem quickly, or it doesn’t ship.
And because working smart shouldn’t be an enterprise privilege, it’s priced for small teams — the practical capabilities of big B2B software, for a fraction of the price. That’s not a promotion; it’s the point.
Learning to code in public
Here’s the part most companies wouldn’t put on their about page: I started learning to code in January 2026, with a Python course. By February I’d stopped doing exercises and started building Lyto — I learn by doing, and building with AI-assisted tools now lets one experienced operator ship real software at a pace that used to take a team. I’ve been building it evenings and weekends ever since, and I’ve enjoyed nearly every hour of it.
That history is also why feedback runs the roadmap. I spent years turning other people’s user feedback into products; now I get to do it with my own. Tell me what’s missing, and watch the changelog — everything I ship is written down where you can check it.
Where Lyto is today, honestly
Lyto is early. There’s no wall of logos or testimonials here, because I won’t invent one. What I can show you is the work: a public changelog of everything shipped and a roadmap of where it’s going. Read them and judge for yourself.
I love software. I’m building the kind I always wished my teams had — and I’d love for you to use it and tell me what to build next.
Come build the early days with us
Start free, use the feedback button, and watch it turn into product.
14-day free trial · card required · cancel in one click