Saelia must be positioned as digital identity infrastructure.
The wedge is not another biometric dashboard. It is a longitudinal personal archive that can become a mirror coach, a living legacy and a future optionality layer.
Saelia strategic product session
A working session to align the Saelia product narrative, demo priorities, data strategy, launch path and business setup.
Strategic product session.
In-person working session.
Simone Asperti
Open the meeting keynote as a focused presentation page.
Open keynoteOpen the full strategic notes as a clean reading page.
Open notes
Summary
Complete meeting summary
Transcript normalized into English, grouped by product, narrative, technology, go-to-market and governance.
Summary depth
Executive view
Product narrative and life stages
The product should not be presented as a single post-mortem concept. The stronger framing is a circular life-cycle model: younger users can work on self-knowledge, adults can use a mirror-coach layer, mature users can preserve legacy, and older users can decide how much continuity they want to leave behind. A missing segment was identified: parents or adults preparing a future record for children and future generations.
Post-mortem positioning and ethical boundaries
The post-mortem area remains strategically powerful but must be handled carefully. It should not promise immortality, resurrection or medical certainty. It can be positioned as an emotional, moral and memory protocol, with optionality, explicit consent and a visible kill switch. The safest route is to keep it present but nuanced, possibly as a future or premium track until the product has stronger validation.
Website and dashboard separation
The public website and the authenticated dashboard should be treated as two different layers. The website explains the vision, credibility, roadmap and future ecosystem. The dashboard is the user product: account, consent, data intake, recordings, timeline, reports and daily interaction. The first demo should show both, but the dashboard must be compressed into a clearer, simpler experience.
Conversational onboarding
The onboarding should feel less like filling out a form and more like speaking with Saelia. The assistant can ask for name, age, context and initial reflections, then gradually adapt tone and memory. Over time the experience may evolve from a standard Saelia voice into a more personal companion, but the first version should remain simple, controlled and easy to explain.
Storytelling as product layer
The meeting emphasized the need for narrative, not just functions. Examples included personal stories, the idea of a consciousness-color test, illustrated cutscenes, guided drawing and moments that make users feel safe sharing experiences they usually do not discuss. These ideas are not all first-demo requirements, but they define the emotional direction of the brand and future experience.
Data strategy
Audio is the first practical data source. The product should also prepare for integrations with external sources such as smartphone health data, Google Fit, wearables and future biometric devices. Biometrics alone are not enough because a heart-rate spike cannot explain whether a person is excited, afraid or stressed. The useful layer comes from combining voice, text, context, physiology and repeated patterns.
Biometric directions
The meeting identified heart activity, voice, perspiration, breathing and repeated behavioral signals as possible future inputs. These should be validated with people who can read and interpret the data correctly. The product should start with accessible integrations and leave specialized hardware for later phases or partners.
Core dashboard modules
The current conceptual dashboard includes account access, consent, kill switch, data collection, upload, browser recording, audio archive, timeline, emotional reports, digital twin/chat, time bubbles, maps and post-mortem protocol. The meeting conclusion was to simplify this into fewer visible modules so first-time users are not overwhelmed.
Market and cultural adaptation
The European product should be built with future internationalization in mind, but an Asian launch would require local partners and adapted interface patterns. Chinese and European users may expect different density, flows and interaction models. The architecture can stay global, while UX and communication should adapt by market.
Launch and pilot path
A small pre-launch event was discussed as a way to make the project tangible: selected guests, a meaningful location, photo/video documentation and a short presentation. The pilot could start with curated users from the founders' network plus a waiting list. The first alpha/beta should use external technologies where useful to reduce time and cost.
Business setup and governance
The preferred immediate path is a lightweight contract or memorandum of understanding covering the first build, responsibilities, economic terms and future company intent. Company formation can happen when the demo is closer to launch. Open topics include ownership structure, decision rights, spending approvals and who represents the project publicly.
Immediate next steps
Proceed with the public website and demo dashboard, define brand tone of voice, reduce dashboard complexity, prepare the first contractual framework, clarify initial budget/tranche, map pilot users and keep legal, privacy and AI-governance constraints visible from the start.
Strategic reframing: from feature list to life-cycle architecture
The session clarified that Saelia should not be reduced to a technical demo or a post-mortem promise. The stronger strategic frame is a life-cycle system that accompanies different human needs over time. The product can start with self-knowledge and reflection, evolve into a mirror-coach for adults, support family and professional legacy, and only later expose more delicate continuity or post-mortem experiences. This circular model is important because it makes the product more understandable, more scalable and less exposed to pseudoscientific interpretation.
Target segments and the missing early-life layer
Four core moments were discussed: self-knowledge for younger users, personal coaching for adults, legacy for mature users and post-mortem continuity for older users. A missing layer emerged during the discussion: adults and parents preparing a future record for children. This creates a stronger circular logic because the product can start before the user is fully conscious of its value, then become useful again later in life. The product story should therefore avoid a linear age ladder and instead show Saelia as a recurring relationship with memory, identity and personal data.
Post-mortem: keep the tension, control the claim
The post-mortem area is one of the most emotionally powerful parts of the vision, but also the most sensitive. The meeting aligned on keeping it present without letting it dominate the first product narrative. It should be framed as a controlled memory, moral testament and emotional support protocol, not as resurrection or immortality. The language must make clear that users decide if and how their data can be used after death, with an explicit opt-out and a visible kill switch. This makes the idea provocative enough for marketing while keeping the product ethically defensible.
Website and dashboard as two separate surfaces
The public website and private dashboard should be designed as different products with different jobs. The website explains the idea, the positioning, the roadmap, the governance, the technical seriousness and the future ecosystem. The dashboard is where the user interacts with Saelia: account, consent state, recordings, archive, reports, timeline, data controls and eventually conversation. The first demo should make this split explicit because investors and early users need to understand both the public narrative and the actual product experience.
Dashboard simplification and cognitive load
The current dashboard concepts contain many possible modules: login, consent, kill switch, upload, recording, archive, timeline, reports, emotional charts, digital twin, time bubbles, maps and post-mortem protocol. The meeting identified a clear UX risk: if everything is visible at once, the product becomes intimidating, especially for older or less technical users. The dashboard should be compressed into fewer visible actions and should progressively reveal complexity. The long-term ambition is a calm interface where the user mostly speaks with Saelia and the system handles structure in the background.
Conversational onboarding as the first emotional contract
Onboarding should not feel like software setup. It should feel like the beginning of a relationship with Saelia. The assistant can ask simple questions, collect personal context and introduce consent in a human way. Over time Saelia could adapt tone, memory and voice, but the initial demo should remain deliberately simple. The onboarding is also where brand tone, trust and privacy are established, so it should avoid cold forms and move toward guided conversation, short prompts and controlled disclosure.
Storytelling, philosophy and emotional entry points
The transcript repeatedly returned to the need for story. Saelia should not only explain functions; it should give people a reason to care. Ideas included personal stories, the color of consciousness test, guided drawing, illustrated transitions and narrative moments that help users share experiences they normally keep private. These are not all first-phase requirements, but they define the product's emotional territory. The brand manual should later translate this into tone of voice, visual rhythm, microcopy and onboarding scripts.
Data model: audio first, multimodal later
Audio is the most practical starting point because it can be recorded directly in the browser and immediately connected to memory, tone, emotion and context. The future system can integrate text, voice analysis, timeline events, health data, wearable signals and user-declared context. A key insight was that biometric data alone is insufficient: a heart-rate spike does not say whether a person is happy, anxious, scared or excited. Saelia becomes valuable when physiological signals are interpreted together with voice, narrative and repeated behavioral patterns.
Biometric and external integrations
The meeting mentioned heart activity, voice, perspiration, breathing, repeated habits and REM/theta-related research as possible future directions. For the demo, the realistic path is not custom hardware but integration readiness: Google Fit, smartphone health data, wearable APIs and later specialized devices. This keeps the early product feasible while giving investors a credible path toward deeper biometric intelligence. Any advanced interpretation should involve specialists who can validate what the data can and cannot support.
Internationalization and market adaptation
The discussion touched on Asia and China as future opportunities, but also acknowledged that a European startup should not enter those markets directly without adaptation. Interface density, cultural expectations, language, user flows and trust signals can differ substantially. Saelia should therefore be architected for future internationalization while the first go-to-market remains focused. The product structure can be global, but the interface and communication should be localized with partners when entering new markets.
Marketing tension and public narrative
The product needs a strong, memorable statement, but it must be balanced with credibility. The transcript explored provocative communication around continuity and living forever, while also recognizing the risk of fear, misunderstanding or religious and ethical backlash. The strongest communication path is to keep the big idea emotionally sharp while using the product experience, privacy controls and scientific humility to reduce perceived danger. Public appearances, podcasts, selected testimonials and high-quality launch content were discussed as possible future accelerators.
Pilot, launch event and early community
A curated pre-launch event was discussed as a concrete milestone: selected guests, a meaningful location, quality photography/video and a short presentation. The event should create a documented founding moment rather than a broad public campaign. A pilot could begin with curated users from each founder's network, possibly combined with a waiting list. The first group should be diverse enough to test usability and emotional reactions, while still controlled enough to manage privacy and product risk.
Business setup, payment and operating agreement
The meeting moved into practical structure: whether to form a company immediately, start with a lightweight contract, or prepare a memorandum of understanding before the full corporate setup. The preferred near-term approach is to avoid slowing the product down with premature company formation, while still documenting responsibilities, economic terms, ownership intent, spending approval and future governance. An initial tranche was discussed to cover real development and infrastructure costs, with broader economic structure to be formalized before public launch.
Operational next steps
The immediate path is to continue with the public website and demo dashboard, define the brand tone of voice, simplify the dashboard modules, prepare an initial contractual framework, clarify the first payment tranche, map early pilot users, and keep legal, privacy and AI-governance constraints visible from the beginning. The demo should be built with enough architectural discipline to evolve, but without overbuilding the advanced AI, biometric or post-mortem layers too early.