Made By an Engineer
Built by someone who actually does the work.
Hi, I'm the engineer behind Saylss.
I didn't start Saylss clearly as a "SaaS founder" looking for an exit strategy. I started it because I was tired.
Tired of manually scanning through hours of podcasts, songs, and broadcast audio just to find that one stray "f-bomb" that could ruin a release. Tired of clunky, automated tools that chopped up the audio or missed the context entirely.
The "Vibe Coding" Journey
Building Saylss wasn't a straight line. It was late nights, endless coffee, and what I call "vibe coding"—iterating until the software didn't just work, but felt right for an audio workflow.
I wanted to build something that respected the audio. Something that understood the difference between a hard "P" pop and a plosive that needed cleaning. Word-level precision wasn't a feature on a roadmap; it was a necessity for the quality I demand in my own work.
Why This Matters
When you use software built by a corporation, you're a row in a database. When you use software built by an engineer, you're a colleague. I know the panic of a deadline. I know the frustration of a crash right before export.
That's why Saylss is different. It's built to solve the actual problems we face every day in the studio, not just to tick a box on a feature list.
I'm committed to keeping this tool sharp, fast, and respectful of your creative process. If something sucks, tell me. I'll fix it. Because I use it too.