A system built for the way you work, not the other way around

Timing depends on scope, integrations, security, stakeholder availability, and decision speed. Discovery first separates the smallest useful release from features that can wait. A serious estimate states assumptions, stages, and risk factors rather than offering an arbitrary date.

Yes. A limited but genuinely usable scope helps validate workflows, business rules, and adoption before investing in a complete platform. The first release should still include security, documentation, and a foundation clean enough to evolve without restarting the project.

Rights are defined in the agreement before development. Client data and paid client-specific work are generally delivered under the agreed terms, while generic libraries or pre-existing Lethavia elements may remain licensed. Domains, production accounts, and essential access should remain controllable by the client.