This page summarizes ownership, project scope, outside costs, data exports, and delivery. The signed proposal controls each project.
Clients retain their client-supplied content, trademarks, and customer data. Domains should be registered in the client’s account whenever practical. Each proposal identifies ownership or license terms for custom code, Mithra’s pre-existing tools, and third-party components.
At the agreed delivery point, Mithra will provide the client-owned data, domain and DNS information, configuration records, and transfer-eligible project materials identified in the proposal.
The proposal identifies the included pages, features, integrations, revisions, testing, launch work, and any correction period. New pages, redesigns, new features, migrations, large content changes, and new integrations require a separate approved scope.
When a request falls outside the approved project, Mithra will provide the scope, price or range, assumptions, and timing before starting. No out-of-scope development charge should appear without the client’s written approval.
Known third-party costs are identified before activation. These may include payment-processor fees, premium domains, software licenses, email or messaging volume, paid data services, taxes, and vendor seat charges. Mithra does not add an automatic per-user fee unless it is listed in the signed proposal.
The CRM owner can download a broad machine-readable backup covering business records and system history. Handoff formats and any provider-specific limitations are documented before termination.
Your proposal should name the deliverables, revision allowance, billing owner for each vendor, outside costs, data-export format, and handoff responsibilities.
Talk about your project