Staff Direct was a 2015 client project focused on connecting dental professionals with clinics and employers. While simple on the surface, it introduced user-flow concepts that later evolved into elements of the QRaway ecosystem.
In 2015, I took on a project for a client in the dental industry — a space I had never worked in before.
The assignment was straightforward but unusual for me: a paid recruitment platform for dental professionals, assistants, and doctors.
Both sides of the market participated:
job seekers registered, created profiles, and paid a small fee
clinics and employers did the same on their side
the platform owner manually matched candidates with suitable openings
The idea was simple, but the logic behind it was new territory.
The system included everything needed for a small, specialized hiring platform:
👤 User registration for both roles
🧑⚕️ Applicant dashboard with profile details, skills, and availability
🏢 Employer dashboard with position listings and requests
🛠️ Admin panel giving the owner full control over users, matches, and payments
Visually, the site was light, clean, and functional — made to be easy for non-technical users on both sides.
The platform ran in that form for about two years, after which the owner modified and expanded it using their in-house resources, without my involvement.
Staff Direct wasn’t a technically heavy project.
What made it stand out was the user-flow architecture: two sides of the same system, operating differently but connected through a single process.
It was a puzzle of interaction rather than engineering —
and that made it genuinely interesting.
This project introduced several user-logic principles that continued evolving across later work and now exist — in their N-th generation — inside QRaway:
dual-role dashboards
role-based routing
owner-managed workflows
structured onboarding flows
profile-driven matching patterns
The project may not have been large, but its influence stayed.
Staff Direct wasn’t a flagship system.
It didn’t push the limits of architecture the way other projects did.
But it refined how users move, interact, and transition across a platform — something that became essential later.
👉 It was an early step in shaping the user-interaction logic that runs inside QRaway today.
No events found for the selected period.
