DevRetainer provides subscription-based software planning, design, build, deployment support, managed-service setup, and maintenance services. Each subscription gives the client access to a structured service process, not unlimited on-call development.

Specific work begins after DevRetainer confirms the appropriate plan, first active request, required access, client responsibilities, and any scope assumptions.

Development work is handled as scoped active requests. A subscription may include ongoing access to software engineering capacity, but work is prioritized around one active development request at a time unless otherwise agreed in writing.

New features, new screens, new integrations, major design changes, platform changes, and meaningful changes outside the approved request may be treated as a new active request or separately scoped work.

Maintenance requests may include bug fixes, small updates, dependency updates, content changes, minor UI changes, health review, and routine upkeep for shipped work.

Maintenance does not automatically include major new features, full redesigns, system rewrites, large custom backends, regulated-data workflows, deep infrastructure, or unrelated new development.

Urgent issues are reserved for production-impacting problems such as outages, broken payment flows, access failures, security-sensitive issues, major user-blocking bugs, deployment failures that impair production, or critical business workflows that are blocked.

Clients may mark a request as urgent, but DevRetainer determines final severity after review. Requests that do not meet urgent criteria may be reclassified into maintenance or development handling.

Repeated misuse of urgent submission may result in urgent access being limited, requests being handled through the standard maintenance process, or the account requiring a different support arrangement.

After delivery of an active request, corrections and small refinements tied to the approved request may be handled during review. Issues caused by DevRetainer implementation are handled as corrections.

Requests that change the approved direction, add new functionality, expand scope, or introduce new requirements may become the next active request or require separate scope.

Clients are responsible for providing timely feedback, access, credentials, assets, approvals, business context, platform accounts, third-party service details, and accurate project information needed to complete work.

Delays in client feedback, access, approvals, third-party services, or platform availability may affect delivery timing.

Subscription payments are processed through Stripe. Stripe may manage payment methods, invoices, billing records, subscription status, failed payments, renewals, and cancellation workflows.

Some subscriptions may be configured as fixed-term or scheduled billing paths. A scheduled path may automatically change tiers, continue into maintenance, or end after the agreed phase.

Unless otherwise agreed or scheduled, subscriptions renew monthly until canceled. Cancellation stops future renewal but does not automatically refund completed billing periods or work already performed.

Refunds are handled case by case. Clients should complete a fit review before subscribing if they are unsure which plan fits their request.

For source-code plans, the client receives the source code for completed work after payment, unless otherwise agreed in writing.

Third-party platforms, hosting, domains, paid APIs, app stores, managed databases, authentication providers, payment processors, CMS tools, and similar external services are the client's responsibility unless otherwise agreed.

DevRetainer may use AI-assisted development tools to improve efficiency on planning, implementation, testing, documentation, and maintenance tasks.

The service remains engineer-led. Technical decisions, code review, deployment judgment, and accountability remain with skilled software engineers.

DevRetainer does not guarantee that unlimited scope, unlimited requests, or all client ideas can be completed within a single monthly billing period.

DevRetainer may decline, re-scope, or separately quote requests involving unusual build environments, device-adjacent work, firmware, regulated data, high-risk security requirements, enterprise infrastructure, large custom backends, or other work outside standard service plans.