MVP scope
AIUNSEEN Studio builds scoped MVPs and first working versions. Production hardening, advanced compliance, enterprise security, scaling, uptime SLAs, and long-term operations are quoted separately unless included in the signed scope.
Engagement Model
How AIUNSEEN Studio scopes, prices, builds, and hands off MVP projects.
Scope and acceptance
No build starts without a signed, feature-by-feature scope. The scope should define features, exclusions, assumptions, revision rounds, acceptance criteria, timeline, third-party dependencies, and client responsibilities.
Payment milestones
Standard payment terms are 50% upfront, 30% after working demonstration, and 20% before source-code handover, unless a different milestone schedule is agreed in writing. For small projects, a higher upfront percentage may be required.
Client-owned infrastructure
The client owns and pays for domain, Cloudflare, hosting, Supabase/Firebase, email provider, Stripe, Apple Developer, Google Play, analytics, monitoring, SMS, API providers, and any other infrastructure required for the project.
Handoff and IP
Source-code handover and IP ownership transfer occur after full payment, subject to third-party licenses and AIUNSEEN Studio's retained pre-existing tools, templates, reusable components, methods, and know-how.
Warranty and support
A 14-day warranty covers defects against the agreed scope and acceptance criteria. Ongoing maintenance, monitoring, uptime commitments, app-store resubmissions, dependency updates, and new features require a support plan or separate quote.
Change requests
Any work outside the signed scope requires a written change request with price, timeline impact, and acceptance criteria before work begins.
Mobile app submission
Flutter MVP projects include one Apple App Store and Google Play submission support cycle when scoped. Approval is not guaranteed and depends on platform policies, client-provided materials, legal content, account status, and app behavior.