App Care for founders

Your app is live.
Give it a
maintenance plan.

You have launched. Now there are bugs to prioritise, updates to consider and a product to look after. Start with the app you have, then agree a practical plan for keeping it maintained.

For existing apps. Suitability and scope confirmed before paid work.

Review before commitment. Understand the app and access first.A finite monthly task allowance. Accept and prioritise a clear queue.You approve the scope. Extra work needs a separate agreement.
The work behind a maintained app

Launch was one milestone.
Upkeep is the next.

Maybe the original developer has moved on. Maybe the app works, but every update creates a new question. Agree what matters now without turning every request into an open-ended project.

  1. 01

    A clear first priority.

    Separate faults affecting existing users from ideas that can wait. You do not need to diagnose the code first: describe what users are experiencing and who holds the source.

  2. 02

    A manageable work queue.

    Choose the fixed monthly task allowance and agree which maintenance tasks and small changes fit. A reported sign-in problem needs investigating before an extra onboarding screen; effort and release timing still depend on the app.

  3. 03

    Visibility before commitment.

    Understand any assessment or catch-up work before choosing ongoing care. If you are unsure about the technology, say so. The initial conversation establishes what information is needed next.

Check the fit

Keep the app you have.
Start with its condition.

Ongoing care works best when the app can be maintained responsibly. A first review helps establish that starting point.

A sensible fit for ongoing care

  • You have an existing mobile app and want help with upkeep, rather than a new build.
  • You can arrange the source code and permission to access relevant accounts, or identify who can hand them over.
  • You want a small, prioritised queue with clear approvals and a fixed work allowance.

A different starting point may help

  • The app cannot build, the source code is missing or ownership is disputed: a handover or recovery scope may come first.
  • A rewrite, a major new feature or a move to a new platform needs a separate project scope.
  • A live outage needing immediate, round-the-clock cover needs an appropriate incident-support arrangement.
One shared care system

Fixed monthly care.
Clear scope.

Choose a plan for one existing mobile product. Native and hybrid apps are welcome, including iOS and Android. We confirm your technology, code and release setup before accepting the app. Your monthly price is fixed for the agreed scope.

For occasional maintenance

App Care

$750 USD / month

For a stable app that needs routine attention and occasional fixes.

  • One monthly review of agreed dependencies, available crash reports and relevant store requirements
  • Up to 2 accepted maintenance tasks per month
  • One planned release cycle per month for approved, ready changes
  • A monthly summary of work completed, open issues and next priorities

One product. One agreed queue. One task active at a time.

Discuss App Care
What counts as a task?
One contained changeA task is one contained change to one existing screen or function in one codebase, with one agreed acceptance criterion. Examples include fixing a reproducible validation error, updating an isolated compatible dependency or, on App Care Plus, adjusting an existing screen’s layout or text.
Native and shared codebasesThe same change in separate native iOS and Android codebases counts as two tasks. A shared-codebase change counts as one task when it fits the same boundary; supported-platform testing is included in that task.
Accepted after reviewWe reproduce or review the request before accepting it into the care queue. Investigation may show that a separate project is needed. A task slot is not an unlimited repair obligation.
Maintenance and improvementsMaintenance addresses existing functionality and routine upkeep. In App Care Plus, a small improvement must fit the same contained-change boundary. New screens, substantial features, integrations, redesigns, major framework/OS migrations, architecture changes and substantial backend changes need a separate fixed quote.
Monthly limitsOne task is active at a time. Unused monthly task slots do not roll over. Accepted tasks remain in the queue until completion without using another task slot; timing depends on scope, access and approvals. Extra work requires an approved fixed quote before it begins; no hourly overage is automatically added.
Review and releaseTesting covers accepted changes against the agreed device and OS list. One planned release cycle each month includes preparation and submission to the agreed stores when changes are ready and approved. Store decisions and review times remain with Apple and Google.
Establish the baseline

App baseline
assessment

$500 USD once

For one mobile product with up to two mobile codebases and accessible source and store accounts. The assessment covers an access and dependency inventory, a build attempt for each included codebase, a review of available crash and store notices, and a written priority list with a care recommendation.

This is an assessment, not a repair package or a comprehensive security audit. We confirm eligibility and access before you agree to it. Larger estates, missing access or specialist assessment requirements receive a separate fixed quote before work begins. Recovery or catch-up work is also quoted separately. There is no obligation to buy ongoing care.

Request an app-care review

Need recovery
or a major change?

An app that will not build, has substantial inherited issues or needs a major new feature may need a separate project first. We agree that scope before starting ongoing care. Rebuilds, major migrations and new integrations are not automatically covered by a maintenance plan.

Care prices are in USD per month. Monthly billing starts after the app is accepted and the start date is agreed. Applicable taxes and third-party fees are identified separately in your proposal. Sending an enquiry does not start a subscription or authorise paid work. Store accounts, hosting, software subscriptions and third-party usage charges are separate. App Care Plus covers agreed small improvements; it does not include advertising, customer acquisition or a revenue guarantee.

Clear responsibilities before care begins.
Technical acceptanceNative iOS, native Android and hybrid apps can be considered. We confirm source access, build and release readiness, supported platforms, dependencies and existing issues before accepting ongoing care.
Support and urgencyOne nominated contact and an agreed request channel. Support hours, time zone, severity rules and response arrangements are confirmed in your proposal. A response target is different from a fix estimate. No 24/7 cover or guaranteed resolution time is included. Do not use this enquiry form as an emergency support channel.
Billing and cancellationMonthly in advance, with a one-month minimum. Cancel with 30 days’ notice; service ends at the end of the paid monthly period that falls at least 30 days after notice. No annual commitment.
Connected systemsBackend work, hosting, monitoring and security maintenance are included only where explicitly scoped. Your proposal identifies who owns each connected service and who handles issues outside the mobile app.
Customer responsibilitiesYou keep ownership of your accounts, arrange approved access and nominate someone to prioritise work, provide safe test cases and approve releases. Do not send credentials, source code or customer records through this form.
Start with the app you have

Review first.
Agree the next step.

An inherited app needs a technical check before anyone can responsibly promise ongoing care.

  1. 01

    Describe the problem.

    Share your public app link, the platforms involved and the issue you want to address. You can start even if you do not know the technology.

  2. 02

    Check condition and fit.

    We review your request and confirm eligibility for the $500 baseline assessment or quote any different assessment upfront. Existing problems, access and dependencies inform the recommendation.

  3. 03

    Choose an agreed scope.

    You receive a care proposal at the published plan price, a separately scoped project recommendation or an explanation of why the app is not a fit. Paid work starts only after agreement.

Before you decide

Your app.
Your questions.

Can I enquire if another developer built the app?

Yes. Tell us who built it and what access or documentation you have. We confirm whether we can support the technology and what needs reviewing before accepting ongoing work.

What if I do not know the technology?

Send the public app link and describe the problem. You can select “Not sure” in the form. Technical details can follow once we know who holds the code and accounts.

Can the plan include new ideas?

Small, defined improvements can be considered within an agreed allowance. A new core feature, integration or redesign needs its own estimate; it is not automatically included in care.

Will you fix everything before the first month ends?

No completion date is implied by a monthly plan. Investigation, complexity, approvals and platform review affect timing. We agree priorities and estimates after reviewing the work. Unused monthly task slots do not roll over. Accepted tasks remain in the queue until completion without using another task slot; timing depends on scope, access and approvals.

Do I have to pay to submit an enquiry?

No. The enquiry does not authorise paid work. The standard app baseline assessment is USD $500 once, subject to eligibility. Any different assessment receives a separate fixed quote before it begins.

A useful first step

Start with
the app you have.

Tell us what is working, what is not and what you want to maintain. We will discuss a sensible next step.

What happens next

Our team reviews your request and follows up by email. We clarify the app’s condition, access and priorities, then agree any assessment and the right next step. You see the scope and costs before paid work starts.

Prefer email? team@afinitiglobal.com

Tell us about your app.

Start with what you know. “Not sure” is a useful answer. Please use public links and leave out passwords, source code and customer data.

Native and hybrid apps can be considered. We confirm fit after reviewing the codebase.

A public App Store, Google Play or website link. Do not include private access links.

Describe the issue in plain English. Mention any handover difficulty or known deadline. Do not include passwords or customer data.

We record your enquiry in HubSpot CRM. This does not subscribe you to a newsletter.

This enquiry does not purchase a plan, book paid work or authorise access to your systems. Privacy policy.