Medq started in a practice. Not in a boardroom, not from a pitch deck. From a real waiting room with real patients.
Built for one practice. Useful for many.
Medq started in a practice. Not in a boardroom, not from a pitch deck. From a real waiting room with real patients.
“My father-in-law runs a practice. He wanted patients to know when there was a delay, to see who had arrived, and to have a clear overview of his waiting room at any moment. As a developer, I could help with that.”
How Medq startedPatients want to know about delays before they leave home. Medq notifies them automatically so they don't sit in the waiting room for nothing, and calls them up the moment it's their turn.
Doctors had no clear view of who was in the waiting room or who had checked in at the front desk. Often, the doctor had to walk over and check in person.
If it takes more than 5 minutes to set up, we haven’t done our job. No consultants, no training sessions.
“My father-in-law runs a practice. He wanted patients to know when there was a delay, to see who had arrived, and to have a clear overview of his waiting room at any moment. As a developer, I could help with that.”
How Medq startedPatients want to know about delays before they leave home. Medq notifies them automatically so they don't sit in the waiting room for nothing, and calls them up the moment it's their turn.
Doctors had no clear view of who was in the waiting room or who had checked in at the front desk. Often, the doctor had to walk over and check in person.
If it takes more than 5 minutes to set up, we haven’t done our job. No consultants, no training sessions.
Born in a waiting room.
It started with a doctor at a practice who had no clear view of his own waiting room. Who was already there, who was still waiting, and how to call one specific patient up to the front desk or the consultation room without walking out every time to check. As a developer, I just wanted to try and help him fix it. The first version was small: a system that shows at a glance who is in the waiting room, with one-click call-ups to the front desk or the consultation room.
Once that overview existed, the rest followed naturally. Statistics to see the patterns in an ordinary week. A fully bookable and plannable calendar that connects the practice and the patient directly. And as a bonus, automatic delay notifications so patients always know when they are actually up next, and the doctor can keep giving the right care without rushing. No complex roadmap, just growing step by step from what a real practice actually needs.
Born in a waiting room.
It started with a doctor at a practice who had no clear view of his own waiting room. Who was already there, who was still waiting, and how to call one specific patient up to the front desk or the consultation room without walking out every time to check. As a developer, I just wanted to try and help him fix it. The first version was small: a system that shows at a glance who is in the waiting room, with one-click call-ups to the front desk or the consultation room.
Once that overview existed, the rest followed naturally. Statistics to see the patterns in an ordinary week. A fully bookable and plannable calendar that connects the practice and the patient directly. And as a bonus, automatic delay notifications so patients always know when they are actually up next, and the doctor can keep giving the right care without rushing. No complex roadmap, just growing step by step from what a real practice actually needs.
Every feature starts with a conversation.
We don't build features behind closed doors. We talk to the practices that use Medq every day, listen to what's working and what's not, and build from there. If you have an idea or run into something that could be better, we want to hear it.
A practice shares a frustration, a wish, or an idea. We get on a call, visit, or just read the message.
We prototype it, test it with real workflows, and make sure it actually saves time before shipping.
The feature goes live for everyone. No waiting for quarterly releases. When it's ready, it's out.
You tell us what works and what doesn't. We iterate. The cycle keeps going.
Got an idea? We're all ears.
Medq is shaped by the people who use it. If something is missing, annoying, or could work differently, let us know. We read everything and most feature requests end up on our build list.
Share your ideaEvery feature starts with a conversation.
We don't build features behind closed doors. We talk to the practices that use Medq every day, listen to what's working and what's not, and build from there.
A practice shares a frustration, a wish, or an idea. We get on a call, visit, or just read the message.
We prototype it, test it with real workflows, and make sure it actually saves time before shipping.
The feature goes live for everyone. No waiting for quarterly releases. When it's ready, it's out.
You tell us what works and what doesn't. We iterate. The cycle keeps going.
Got an idea? We're all ears.
Medq is shaped by the people who use it. If something is missing, annoying, or could work differently, let us know. We read everything and most feature requests end up on our build list.
Share your ideaGet in touch.
Have a question about Medq? Want a demo for your practice? Just want to say hello? We would love to hear from you.
Get in touch.
Have a question about Medq? Want a demo for your practice? Just want to say hello? We would love to hear from you.