We are a small group who got tired of watching good teachers and coordinators lose their week to scattered tools—and wanted something steadier.
We kept seeing the same pattern: music and tutoring groups were duct-taping spreadsheets, chat apps, and payment tools together. Teaching was squeezed around admin that never quite fitted. In-Tune grew from wanting one straight place for the week—people, schedules, money, and messages—without pretending a generic office stack was enough.
We are not trying to replace your judgement or your rapport with pupils. We want software that holds the fiddly, repeatable bits—so you stay with the parts that matter: planning a term, catching a phrase that needs another pass, or knowing who needs a gentle nudge this week.
We ship things we would trust with real student details and real money: clear enough that someone new on the team is not lost on day one, and careful enough that you are not lying awake wondering if a balance is right. When something feels off, we would rather mend it than polish the brochure.
Ryan has spent more than fifteen years in IT—networking, security, and development—and leads how In-Tune is put together and kept running.
He cares that the service stays dependable and that sensitive data is handled soberly, because a tutoring centre is not a place for flaky infrastructure or crossed fingers.
Simon builds the product day to day, with a background in programming and a soft spot for music—especially guitar—which keeps him fussy about rhythm in both code and screen flow.
He wants screens tutors can live in without another “training day” just to find the next button.
Ashar looks after business development—meaning he opens the right doors, not every door. He finds schools and partners who match how we actually work, so first conversations sound like comparing notes rather than sitting through a deck.
He keeps introductions human: honest fit, awkward questions welcome, nobody strong-armed into a trial they are not ready for.
Viktor is a full stack web developer with a particular strength in Ruby and Python, focused on the backend while picking up front-end work whenever it is needed.
He cares about building efficient, robust features you can rely on—and about keeping quality high as the product grows.