SymBioVault had an idea, a patent, and a problem they knew was real.
People’s own microbiome and associated data — the biological makeup of their skin, gut, and body — have significant scientific value. Researchers developing truly personalised medicines need it. But the infrastructure to collect it, store it, and share it in a way that keeps users in control doesn’t exist.
Their concept: a platform that connects individuals, clinics, and research facilities. Users get their microbiome samples collected at regular doctor visits, analyzed, stored securely for possible future use, and linked to a digital record they own. Researchers get access to data at a volume and quality that currently doesn’t exist in the market. Clinics get a new service to offer without changing their existing workflow.
Blockchain, they believed, was the answer. Specifically, they came in with a plan built around NFTs.
Before committing to development, they needed two things: confirmation that the technical approach made sense, and a package of materials they could put in front of investors. They had a meeting booked. The timeline was tight.
They started with CoreLedger’s Launch Package.
The concept had real merit. But it had questions that needed answering before any architecture could be designed.
The Launch Package runs as a structured sprint. Every client exits with the same four outputs. What changes is what’s inside them.
1. Blockchain Concept
The first workshop started with SymBioVault’s existing assumption: they needed an NFT platform.
It didn’t survive the session.
An NFT creates a tradeable asset. SymBioVault didn’t need that. What they needed was a permanent, verifiable link between a person and their stored microbiome sample, a record that can be owned and accessed but not traded. The right architecture was a non-fungible document: a cryptographically hashed record written on-chain, with no token mechanics attached.
That single clarification changed the entire build direction. And it happened before any development began.
The analysis also defined the on-chain/off-chain boundary, arguably the most important architectural decision for any platform handling personal health data.
Personal data, sample metadata, and analysis results stay off-chain in compliant storage systems. On-chain lives the proof layer: ownership records, consent events, access permissions, audit trails. The blockchain doesn’t hold the data. It holds the truth about the data.
Key findings:
NFT concept redirected to non-fungible document architecture
On-chain layer defined: ownership proofs, consent events, access permissions, verifiable audit trails
Off-chain layer defined: personal health data, sample metadata, microbiome results
Custom wallet structure specified: no seed phrases, no visible blockchain complexity for end users
Access credential model designed for three distinct user types — patients, clinics, and researchers
2. Work Breakdown Structure (WBS)
With the architecture direction confirmed, the WBS translated the platform vision into a development plan.
SymBioVault’s ecosystem has three stakeholder groups with different needs and different interfaces: patients who want to view and control their data, clinics that need a simple sample-collection workflow, and research facilities that need permissioned access to data. Each required its own feature set. Each had its own priority level for the MVP.
The WBS mapped out:
All three user journeys (patient, clinic, researcher) are broken into discrete features
Consent and access permission management as a core system
MVP feature set separated from long-term product vision
Development effort estimates across all required resources
The output: a development plan transparent enough that any investor can evaluate it, and specific enough that a development team can act on it directly.
3. Wireframes & UI/UX Design
Investors evaluate user experiences, not architecture diagrams.
S-PRO translated the platform concept into designed wireframes in Figma to showcase a navigable product experience.
Key flows included:
One design constraint guided every screen: a user should feel like they’re using a secure personal health vault. The blockchain layer should be completely invisible. No wallet terminology. No chain references. No app download needed. No complexity surfaced to a user who doesn’t need to understand it.
The prototype gave SymBioVault something to put in front of investors that works. They could demonstrate the platform, not describe it.
4. Final Presentation
All outputs, the blockchain concept, the WBS, the wireframes, and the development plan, were consolidated into a presentation deck to provide a solid foundation for discussions with investors.
The deck covers:
With the Launch Package, SymBioVault now has everything needed for successful investor meetings.
At the end of the Launch Package, SymBioVault received a complete set of deliverables, each one a working asset for their project:
The project also clarified something the client came in uncertain about: the architecture is designed to be extensible.
The first pilot targets clinics and the women’s health segment. The infrastructure can support other medical data types and expand across European markets without rebuilding from scratch.
Most platforms that try to use blockchain in healthcare fail at the same point: they build first and figure out compliance later. Or they overcomplicate the blockchain layer and make it impossible to explain to a clinic receptionist.
SymBioVault spent weeks validating the architecture before committing to development. They changed their core technical assumption from NFT to NFD before a line of code was written. That decision alone likely saved months of rework.
That’s what the Launch Package is for.
Ready to validate your blockchain concept before you commit to building?
Book a discovery call. We’ll tell you what’s worth building, and what isn’t.