Three days in Katowice that moved Saelia from a shared prototype into an incorporated company with a sharper product wedge and coordinated operating priorities.
Saelia was formally incorporated in Katowice on 24 August. The team aligned the immediate product around voice, summaries, timelines and memory relationships, while placing trust, user research and disciplined communication ahead of speculative infrastructure.
Foundation and working sessions.
Including Vienna House follow-up.
Confirmed outcomes are separated from future directions discussed during the sessions.
The company was founded in Katowice on 24 August 2026. The executed corporate documents now provide the authoritative legal baseline for ownership, governance and company activities.
The immediate product loop should transform recordings into useful summaries, chronological events and relationships between people, places, memories and supporting media.
Saelia needs explicit consent, understandable controls, immediate user value and an accessible experience that can be validated with older, non-technical and internationally distributed users.
Market personas, willingness to pay, cost-to-serve, staffing, infrastructure and financing must be modeled by phase rather than presented as one unsupported end-state forecast.
Dominika will lead the messaging framework and English-first podcast preparation. Website, dashboard, decks, team profiles and social channels must express one focused promise.
Dedicated infrastructure, physical avatars, specialized hardware, creator marketplaces and advanced identity reconstruction require separate feasibility, legal and market validation.
Pre-foundation work covered the removal of Dario Cadei, correction of names and alignment of company activity codes with software, AI, communication, conferences and potential device resale. Final legal facts must always be checked against the executed documents.
Current AI can identify topics, summarize stories, extract events and organize recordings. Saelia can therefore create a credible product experience without waiting for proprietary models or a complete digital reconstruction of a person.
A personal archive becomes more valuable when users can see connections across people, places, dates, photographs, videos and recurring themes. The visual model should make order visible without implying that AI possesses consciousness.
Longitudinal data can support more advanced experiences later, but each materially new processing purpose requires clear user choice. Existing recordings must not silently become inputs for an undeclared identity feature.
Saelia succeeds when people actively contribute, not when accounts simply exist. Progress indicators, prompts and immediate outputs can encourage continuity, but should remain respectful of the emotional nature of the archive.
A segmented cohort of approximately 50 participants was proposed to test interface clarity, privacy comprehension and perceived value. Older and non-technical users are essential because voice capture, playback and correction must feel self-explanatory.
External European infrastructure is a defensible starting point if storage and processing are communicated accurately. Dedicated servers, local inference and specialized hardware should follow workload measurements and specialist security review.
The team discussed failures of premature photorealistic reconstruction. Voice and restrained visual representation are more credible early interfaces; advanced avatars require significant technical work, testing and ethical review.
The business plan should define a small set of primary personas before estimating adoption. Potential segments include people preserving family knowledge, users building a personal longitudinal archive and creators sharing selected expertise or experiences.
A free allowance and paid recording or storage tiers were discussed as a plausible first model. Pricing remains an assumption until user research establishes value, expected contribution volume and infrastructure cost.
Communication guidelines should define tone, approved vocabulary and terms to avoid. An English-first studio podcast is targeted for preparation in September, with the broader content system expected to mature through October.
Each founder should submit a concise plan with responsibilities, dependencies and indicative dates. The plans will be consolidated into one visible operating roadmap so product, legal, business and communication progress remain synchronized.
Near-term work extracted from the sessions, without turning exploratory ideas into commitments.
File the executed foundation documents and ensure internal shareholder, governance and activity-code records match the legally effective versions.
Specify recording, transcription, summary, event extraction, timeline and memory-graph states as one demonstrable workflow.
Prepare participant criteria, tasks and questions covering interface clarity, privacy, trust, recording and correction.
Connect personas, pricing assumptions, technical resources, operating costs and financing scenarios to clear development phases.
Prepare tone-of-voice rules and review podcast answers so ambitious vision, current capability and research direction remain distinguishable.
Validate studio, interviewer, video production, cost and the English-first recording window targeted for September.
Reserve priority social handles, define ownership and start only with a cadence the team can sustain.
Each founder provides responsibilities, dependencies and indicative milestones for consolidation in the operating pipeline.