One Founder. AI-Powered Development. Independent Security Validation.
How a solo healthcare founder used independent manual penetration testing to find and fix vulnerabilities before launch, validate critical security controls, and confirm that testers could not reach another practice's or client's records.
SoloistHealth
Building Healthcare Technology as a Solo Founder
SoloistHealth is an electronic health record (EHR) and practice management platform for health and wellness providers who run a solo practice. The product includes two distinct experiences: a provider portal for the practitioner and a client portal for their clients (the patient side of the product). Because the platform handles protected health information (PHI), Ray, the founder, needed to build security in from the start.
For Ray, that responsibility mattered because he was building the product while also preparing the business to enter a market where trust and security are fundamental to customer relationships.
Ray builds with AI coding tools, letting one person ship far more code than they can review line by line. Every change runs through automated tests and a staging check before release, but that is still the builder checking his own work.
As Ray explained:
"AI-written code also tends to look right, which makes it easy to trust."
Code that looks correct isn't necessarily secure. Ray recognized that independent security validation is an important way to challenge development assumptions and assess the platform from an attacker's perspective.
The Challenge: Establishing Trust Before Launch
Healthcare organizations have specific expectations when evaluating technology providers. Business Associate Agreements, HIPAA-related documentation, independent penetration testing reports, and evidence of security safeguards can all factor into vendor evaluations.
Ray understood these expectations from his previous experience in healthcare technology. He wanted SoloistHealth to show its security posture to the providers who would trust it with their clients' records. Rather than waiting for someone to ask for proof, he decided to get ahead of the question.
As a solo founder, Ray also had to decide where to invest limited resources. He evaluated different testing options, including full-coverage and risk-weighted approaches. His priorities included manual testing, a named lead penetration tester, HIPAA Security Rule-aligned reporting, and documentation that could support future business conversations.
Most importantly, he wanted to validate the platform's more complex architectural risks, particularly the boundaries between provider and patient experiences.
The Approach: Manual Testing Across Both Portals
Software Secured conducted a manual penetration test of SoloistHealth, covering both the provider and patient experiences. Ray specifically wanted both portals assessed because despite sharing a codebase and some routes, the two experiences have distinct functionality and security boundaries.
The assessment examined whether a user could access information or functionality beyond their authorized permissions, including scenarios involving different patients, providers, and portal types. Pentesters could not access another practice's or another client's records. The assessment documented vulnerabilities and mapped them to relevant HIPAA Security Rule considerations.
The Business Impact: Launching with Confidence Instead of Hope
Penetration testing documentation directly impacts sales or procurement by letting you confidently show the platform has been independently tested.
SoloistHealth's security page states that Software Secured independently tested the platform and that the attestation letter is available on request.
As a one-person company asking clinicians to trust him with their clients' health information, being able to answer the question "Has anyone outside actually tested this?" before it is even asked helps establish credibility. When asked about the biggest business benefit of the engagement, Ray described it simply:
"Launching with confidence instead of hope."
The value wasn't just knowing that a security assessment had taken place. It meant real vulnerabilities were identified, fixed, and retested before the platform handled real patient information. The engagement also provided independent testing documentation to support SoloistHealth's security efforts and future customer conversations.
When AI Writes the Code, Independent Testing Matters
AI coding tools have enabled solo founders to build and ship increasingly complex products, but generating more code doesn't automatically mean having the time or expertise to review every line for security issues. For Ray, this is why independent penetration testing matters.
AI-generated code can look convincing while still containing vulnerabilities. Whether software was written by a developer or generated with AI, those vulnerabilities still need to be identified.
Ray's perspective captures the value of an independent assessment:
"An independent tester doesn't care how the code was written. They go at it the way a real attacker would, and that's the check that counts."
Rather than relying solely on development assumptions, manual penetration testing evaluates how the application behaves when someone actively tries to exploit it. For founders using AI to accelerate development, this provides an important additional layer of validation. Building faster creates opportunities, but security testing remains essential, particularly when the product handles sensitive information.
Advice for Other Solo Founders
Ray's experience offers a practical lesson for other founders building healthcare and SaaS products: build security into the development budget and launch plan from the start.
His advice:
1. Budget for security from day one.
Treat independent security testing like insurance, not a nice-to-have expense at the end of development.
2. Conduct your own security review first.
Do an internal review before bringing in an independent tester. This lets the paid assessment focus on complex problems rather than easily identifiable issues.
3. Test every side of the product.
Don't overlook the patient-facing experience or other parts of the application. In healthcare, the patient side is within attackers' reach.
4. Leave time for remediation and retesting.
A penetration test should not be the final item on your pre-launch checklist. Build in enough time to address vulnerabilities and have them retested before going live.
For Ray, that preparation made a meaningful difference. SoloistHealth didn't have to wait until real patient information was at stake to discover and address vulnerabilities.
Security as a Foundation for Growth
Building a healthcare technology company as a solo founder requires balancing product development, business priorities, and the responsibility of protecting sensitive information. Ray's approach demonstrates why independent security validation belongs in that process.
By investing in manual penetration testing before launch, SoloistHealth identified and resolved vulnerabilities, validated important architectural controls, and gained independent documentation of its security efforts. The company launched with those issues addressed, a clearer understanding of its security posture, and a stronger foundation for conversations with the healthcare providers it hopes to serve.
For founders building increasingly complex products with smaller teams and AI-assisted development tools, the lesson is straightforward: shipping faster should never mean skipping independent security validation.
Continue your reading with these value-packed case studies
Resources from our team

Top 10 Cybersecurity SaaS Companies Protecting Cloud-First Businesses
The cybersecurity SaaS market is crowded and confusing. Many tools promise one-click safety yet ship noisy dashboards that do not plug into developer workflows.
.avif)

