An in-person alignment session on dashboard priorities, MVP scope, data infrastructure, investor materials and the next operating milestones.
The team confirmed that the priority is not adding more modules, but building a reliable foundation: Overview-first dashboard, frictionless data collection, AI processing and a user experience that creates recurring engagement.
Product development session.
Convallaria office.
The dashboard Overview becomes the central hub and first proof of product value.
Target date for alpha website, dashboard, investor deck and light business plan.
AI recap normalized into a working record: product priorities, dashboard principles, data strategy, communication split and concrete follow-up dates.
The Saelia vision remains unchanged, but the near-term focus is execution. The dashboard is still under development, several areas remain placeholders, and the Overview should become the central user hub. The first user experience must show value immediately and set the tone for long-term adoption.
The dashboard should not feel like passive storage. It must show that Saelia understands, processes and gives meaning to user information. Navigation should be extremely intuitive, with a minimal learning curve and immediate access to useful insights.
The product needs reasons for users to return regularly: feedback, progress indicators, personalized insights and visible processing. The goal is to become part of a routine, not an occasional archive that users forget after uploading data.
The immediate objective is a reliable MVP, not the complete long-term product. The MVP should prove the core loop: data collection, secure storage, automated processing, dashboard visualization and meaningful outputs. More advanced features should come only after the foundation is validated.
The real value is the infrastructure that collects, organizes and interprets personal information. The team confirmed that an internal audio recording workflow is already available: direct recording, original file storage and AI processing after recording. This creates a practical starting point for future multimodal data expansion.
The initial platform should stay cloud-based. Communicating proprietary server infrastructure too early would be misleading. Dedicated infrastructure can become relevant later, after the product has reached enough scale to justify it.
Public communication can remain emotional and visionary: legacy, memory, continuity and personal history. Investor communication must stay pragmatic: data collection, proprietary technology, scalable architecture, AI capabilities, business model and measurable product validation.
Fundraising should begin only after the MVP can demonstrate real value: working platform, real users, collected data and clear product-market direction. As the project grows, the team will need AI engineers, data engineers, backend developers, data scientists, UX specialists and infrastructure expertise.
Dates collected from the post-meeting follow-up email. They are treated as working targets to validate with the team.
Target date: 24 July 2026. The Saelia website and dashboard alpha release should be ready, including investor presentation and light business plan version. This is coherent as a focused alpha milestone if the scope remains strictly Overview-first and avoids adding new modules.
Working window from 31 August to 2 September 2026 for the company foundation process in Poland. This timing is coherent if legal/accounting preparation starts before the trip.
Target window for the first public presentation after 28 September 2026. Venue to be defined. This timing gives enough space after company setup to refine product, narrative, investor materials and launch assets.
Operational decisions extracted from the meeting recap.
The Overview should become the core experience and the first proof that Saelia can turn collected data into meaningful, understandable value.
The infrastructure should remain cloud-first during early development. More proprietary or dedicated infrastructure can be planned only after scale and product validation.
The public narrative can be visionary, while investor materials must stay grounded in technology, data, architecture, business model and measurable execution.
The team should approach investors after the MVP can show working product, active usage, real collected data and clearer product-market direction.