An empty shift is a small emergency with a large supporting cast. A manager starts calling. A coordinator opens a folder. Somebody checks a license, somebody checks a calendar, and somebody discovers that the person who is free lives an hour away. The vacancy may be only one line on a schedule, but filling it is an opera performed with telephones, spreadsheets and the stubborn hope that everyone answers in order.
Ray Wahab built Diem Health for that ungainly space between need and availability. Based in Fremont and working from nearby Pleasanton, he arrived at the problem through operations. California records identify him more fully as Abdul Ray Wahab and connect him with A Plus Home Health Care, A Plus Hospice, Norcal Home Care and Norcal Hospice before Diem was incorporated. One federal provider record names Abdul Wahab as president and CEO of A Plus Hospice. The paperwork came before the platform.
That sequence is the useful part of his story. Diem was not a founder wandering into a fashionable marketplace category and searching for a customer. Its product followed the shape of work Wahab had already encountered: finding qualified professionals, proving that they were qualified, matching time to demand, carrying information into a visit and moving payment afterward. The company tried to turn a staffing desk into a screen without pretending the desk had only one drawer.
01 / The operator's eye
A founder shaped by the back office
Wahab's path is written clearly in dates, operating roles and a product whose menus betray what its builders considered important. The details are practical because the work was practical.
The cluster of California care companies appeared in 2015. Four years later, Diem, Inc. was filed as an online technology company. Wahab was listed as chief executive officer and secretary; Farsheid Jeff Assifi was listed as chief financial officer, with a director role also attached to the Assifi name in later records. The corporation was small, local and pointed at a task its founder could recognize without a trend report.
In operations, bureaucracy is rarely decorative. A professional license must be current. Availability has to be real. A request needs an address, a duration and enough context to make the assignment legible. The calendar is not a lifestyle accessory. The profile is not a social-media flourish. Each field bears weight.
Diem's clinician app turned that administrative weight into a pitch about autonomy. Professionals could search by time and location, book from a phone and pursue work around the rest of their schedule. Its language was impatient with intermediaries: “No middleman or staffing agency!” The exclamation point did more than add cheer. It named the cost and delay the company wanted users to notice.
For a facility, however, the middleman had been doing several jobs at once. Removing one meant rebuilding recruiting, credential checks, coordination, records, communication and payment. Diem's ambition lived in that less quotable second sentence. The company was selling freedom to one side and dependable orchestration to the other.
02 / The product
A map is useful only when the dots can work
Diem's surviving product views reveal a straightforward journey. A facility could search a pool of professionals, filter by category or title, inspect availability and verification, move to a profile and send a visit request. Map views made distance visible. Records held education, work experience, licenses, CPR cards, identity documents and payment details. Scheduling and invoices lived nearby.
The map made for the most attractive screenshot, but the credential record carried the argument. A nearby person is not useful merely because a pin places them nearby. The facility needs the right role, evidence and availability. Diem tried to let geography begin the conversation while verification completed it.
This is where Wahab's operating background becomes visible without requiring him to narrate it. The product did not stop at a directory. It continued into the visit form, asking when, where, for how long and with what accompanying information. It recognized that discovery creates a new administrative obligation. A polished marketplace that hands the user back to email after the match has solved the photogenic half of the problem.
Diem's company description also emphasized cloud software for credential management and onboarding automation. That positioned it between two familiar species: workflow software sold to organizations and a two-sided marketplace linking organizations with labor. Each could help the other. Useful software might attract facilities before the network became dense; more facilities could make the network worth joining for professionals.
03 / Two promises
Flexibility on one side, certainty on the other
Every marketplace tells two stories. The professional story was time. A shift should fit an open afternoon, a preferred radius and a desired rate. The facility story was certainty. A person displayed on the screen should be qualified, available and ready to accept the work. One side wanted optionality. The other wanted the option to become a commitment.
One platform, two different jobs
Those bars are a diagram of emphasis, not company metrics. The equal length is the point. A marketplace cannot lavish attention on the person booking work and treat the manager filling it as an afterthought. Wahab's product spread its attention across both surfaces: a mobile app for professionals and a facility dashboard for the people assembling coverage.
The capital had to stretch across both. Diem raised a reported $510,000 convertible note in August 2019. The clinician app reached version 1.1 in October, weighing 87.77 MB and supporting iPhone and iPad. It was free to download and promoted a free 90-day trial. The supplied company record lists two employees, which makes the surface area of the attempt look especially large: mobile software, organization software, onboarding, records, payment and the local network required to make every screen useful.
Half a million dollars is enough to make a serious attempt. It is not enough to purchase a thriving marketplace by decree. Density has to be earned neighborhood by neighborhood, role by role and shift by shift. A professional returns when the work is worthwhile. A facility returns when a request reliably becomes coverage. The software can reduce friction, but it cannot charm an empty network into abundance.
04 / The quiet record
The filings kept speaking across the years
Diem, Inc. entered suspended status in 2021, returned to active status in September 2023 and filed a statement of information in March 2024. Registry-derived data updated in March 2026 still listed Wahab as CEO and secretary.
A legal entity's active status establishes a filing condition rather than a measure of product scale. Wahab's LinkedIn identity continues to point to Diem Health. Together, the profile and filings extend the chronology beyond the product's 2019 launch without asking a corporate status label to say more than it can.
What remains visible is a pattern of attention. Wahab went from organizations that delivered care into software for the people arranging the workforce. He chose a problem full of plain nouns: map, calendar, license, visit, invoice. He raised a modest note, shipped an app and attempted to make those nouns cooperate.
05 / What builders can steal
Begin with the folder everyone resents
The sharpest lesson in Wahab's story is the choice of starting material. Founders often hunt for a dazzling behavior to invent. Operators notice a dull behavior repeated badly. The folder that gets rebuilt for every hire, the phone tree activated for every absence and the schedule nobody entirely trusts are already products. They are simply products made from labor and patience.
Diem's second lesson is to connect the moments that belong together. Discovery without verification leaves a manager with a list. Verification without a request leaves a qualified professional sitting in a database. A request without scheduling creates another conversation. The product becomes useful when each screen anticipates the next obligation.
The third lesson is less comfortable. A marketplace promise is a bundle of operational promises. “No middleman” sounds like subtraction, but the builder inherits every useful thing the intermediary used to do. The triumph is not removing a company from the diagram. It is making the work behind that company legible, reliable and less expensive.
Ray Wahab's story is most persuasive in the uncelebrated detail: an operator knew where administrative friction accumulated and tried to give it an interface. There is something appropriately per diem about the work: one day, one shift, one request at a time. The ambition was broad. The work arrived in small rectangles on a calendar.