Skip to content

Someone still responsible after launch — by arrangement, not obligation.

Monitoring, bug fixes, releases, analytics and continuous improvement.

Service Care Plans

01 — Problems

You are probably here
because of one of these.

  • An app that stopped working after an OS update and nobody noticed for a week.
  • A store listing failing review because a platform requirement changed.
  • Analytics installed at launch that nobody has looked at since.
  • Security patches nobody is tracking.
  • A small improvement that needs a whole new project to happen.

02 — Capability

What we actually do.

How we picture it: A product pulse that keeps running after launch.

  • Uptime and error monitoring
  • Defect fixes within an agreed response time
  • OS, framework and dependency updates
  • Store release management
  • Analytics review and reporting
  • A budgeted allowance for small improvements

03 — Scope

What is in, and what is not.

The right-hand column is the one most studios leave out. Naming the exclusions up front is how a fixed price stays fixed.

Deliverables

  • Monitoring and alerting on the paths that matter
  • Agreed response times by severity
  • Scheduled dependency and security updates
  • Monthly usage and stability report
  • Release management for both stores
  • A named person who knows your system

Not included

  • New features beyond the plan allowance — those are scoped and quoted separately
  • Third-party service outages
  • Hosting and API costs
  • Changes to systems we did not build, until we have audited them

05 — Technical approach

What we build it with.

Chosen per project against your constraints — not a fixed house stack, and not a logo wall. The test is what your team can maintain after we hand it over.

Monitoring

  • Uptime checks
  • Error tracking
  • Performance monitoring

Analytics

  • GA4
  • Event taxonomy
  • Funnel reporting

Release

  • Play Console
  • App Store Connect
  • Staged rollouts

Maintenance

  • Dependency updates
  • Security patches
  • Backup verification

How this gets proved

  • The 30-day post-launch warranty is included in every project, whether or not you take a care plan — the two are deliberately separate.
  • Response times are stated by severity in the agreement, not left to goodwill.
  • Monthly reporting says what actually happened, including the months when the answer is "nothing".

06 — Delivery

Checkpoints and timelines.

You sign off at each of these

  1. Onboarding Monitoring in place and baseline recorded
  2. Monthly Usage and stability report issued to you
  3. Quarterly Improvement backlog reviewed and reprioritised
  4. Renewal Plan tier reviewed against actual usage

Typical timelines

Warranty (included with every project)
30 days from launch
Care plan
Monthly, cancellable
Improvement cycle
Quarterly

Ranges, not promises. Your actual timeline is fixed in writing in the proposal once the scope is agreed.

08 — Questions

The ones people actually ask.

No, and that is the point. You own the source code and every account, so any competent team can maintain the product. A care plan is worth buying when you would rather it were us.

Project qualification

Get a fixed-price proposal.

Tell us the problem, the stage you are at and the budget band. You get a discovery call, then a written proposal with exact scope, milestones and a final number — within 24 hours.

Response
Fixed-price proposal within 24 hours
Confidentiality
Mutual NDA signed before any project detail is discussed

Prefer to just talk? WhatsApp is answered fastest during studio hours.