Healthcare · Genetic testing
KolGene, a genetic-testing marketplace that turned lab search into one request flow
KolGene connected clinicians with genetic testing labs, so one test request could become comparable lab offers instead of a long email chase.
The story behind
KolGene was a health-tech startup with a practical problem: genetic testing had too many doors. A clinician could know the patient needs a test and still lose time finding the right laboratory, checking availability, comparing terms, and moving the sample forward. The product moved that work into a request marketplace.
The important part was the request itself. A lab cannot quote from "blood test etc." and a clinician cannot compare offers if every lab asks for details in a different format. So the workflow captured the test name, budget, quantity, turnaround time, regulatory approvals, location, and sample context before offers came back. Less romance, more fields. Software often grows up that way.
The other side mattered just as much. Laboratories needed a place to review incoming requests, submit offers, manage account details, and track samples without turning every quote into a thread. A marketplace without state is just email wearing better shoes.
Business value
- Clinicians could request a genetic test once and compare lab offers in one workflow.
- Laboratories could respond to qualified demand instead of waiting for scattered inquiries.
- Price, location, turnaround, approvals, and sample details became comparable.
- The product worked across desktop and mobile surfaces, so the workflow was not tied to a desk.
Project scope
- Public landing pages and role-based sign-up for clinicians and laboratories.
- Clinician request flow with test details, quantity, budget, turnaround, and preferred location.
- Laboratory dashboard for reviewing requests and submitting offers.
- Offer comparison surfaces for clinicians choosing the best lab option.
- Request status, notification feed, and sample handling views.
- Mobile-ready presentation for iOS, Android, and responsive web use.
Deliverables
- A named KolGene product experience for clinicians and genetic testing labs.
- Clinician workspace for creating and reviewing test requests.
- Laboratory workspace for profile details, offers, and incoming requests.
- Request-detail and offer-comparison screens.
- Notification and status surfaces for request progress.
- Supplied portfolio visuals showing desktop and mobile product screens.
Tech stack
Frequently asked
Why is KolGene named?
KolGene was a public startup, and the supplied portfolio visual uses the product name. We still avoid private patient data and keep the page focused on workflow, product shape, and the visible interface.
Why are there no performance metrics here?
The old visual and public descriptions explain what the product did, but we do not have approved delivery metrics for this case. So the page keeps the proof to the named product, the workflow, and the supplied screens.
Can you build this kind of two-sided marketplace?
Yes. The hard part is not the listing page. It is the state: one side creates a structured request, the other side responds, and both sides can see where the work stands.
What makes genetic-testing workflow different from a normal marketplace?
The request has to carry enough detail for a lab to quote safely: specimen, test name, quantity, turnaround, location, approvals, and price constraints. If those fields are vague, the marketplace turns back into email with a login screen.
Does this replace a laboratory information system?
Not by default. A marketplace like this sits around discovery, request, offer, and status flow. The clean integration point depends on how the lab already handles orders and samples.
Have a workflow that needs this?
Tell us the shape of the problem. Scoped estimate, usually within 3 to 5 business days. No card, no obligation.
Estimate this buildor email business@highcraft.io