Minor Updates

Small changes, handled continuously — not quoted one by one.

Text edits, small tweaks, and compatibility updates as devices and OS versions change — covered under your retainer, so day-to-day requests don't turn into a new invoice every time.

Included, not extra Minor updates are part of the Growth Retainer, batched into your regular cycle.

What's Included

What counts as a minor update.

Small, contained changes that keep the app accurate, current, and working smoothly.

✏️

Content

Content & Copy Changes

Text, prices, images, and other content updates as your business changes.

🎛️

UI

UI Tweaks & Small Fixes

Spacing, button labels, and minor layout adjustments to keep things polished.

Core 📱

Compatibility

OS & Device Compatibility

Checked and updated as new Android and iOS versions roll out, so the app keeps working.

📦

Dependencies

Third-Party Library Updates

Dependencies are kept current and secure as newer versions are released.

⚙️

Config

Small Config Changes

Settings, thresholds, and business rules adjusted as your operations evolve.

🗂️

Delivery

Batched Into Your Cycle

Requests are grouped and shipped together within the current retainer cycle.

How It Works

From request to a shipped update.

A lightweight process — no separate quote or approval cycle needed.

01

Request Submitted

You send the small change over WhatsApp or email — no formal ticket required.

02

Scoped & Scheduled

We confirm it's a minor update and slot it into the current retainer cycle.

03

Shipped & Confirmed

The change goes live and you're notified — no extra invoice attached.

Why It Matters

Billed per tweak vs. covered by your retainer.

Small requests add up fast when every one of them needs its own quote, approval, and invoice.

Typical Agency (Billed Per Change)

Every small request is a new invoice

  • A text change or button tweak gets its own quote and wait time.
  • Small requests pile up into unexpected monthly costs.
  • OS and compatibility updates are often reactive, after something breaks.
  • Hesitation to ask for small fixes because "it'll cost extra."

Our Minor Updates Coverage

Already covered by your retainer

  • Small changes are batched into the current retainer cycle.
  • No separate quote or invoice for routine tweaks.
  • Compatibility is checked proactively as OS versions change.
  • You can ask for small fixes without worrying about extra cost.

FAQ

Common questions about minor updates.

Straight answers about what's included and how requests are handled.

What counts as a "minor" update vs. a new feature?

A minor update is a small, contained change — text or image swaps, a button label, a spacing fix, a compatibility update. A new feature is a new screen, workflow, or capability the app didn't have before, and is scoped separately.

How many minor updates can I request per cycle?

There's no fixed cap — small requests are batched and handled within the current retainer cycle as capacity allows. If requests start adding up to significant new work, we'll flag it before treating it as a bigger scope.

What if my request turns out to be bigger than expected?

We'll tell you upfront. If a request grows beyond a minor tweak, it's scoped as a feature and covered by your monthly development time block instead, or quoted separately if it goes beyond that.

Do minor updates need a new quote?

No. Minor updates are already covered under the Growth Retainer, so there's no separate invoice or quote needed for them.

What happens if I skip a cycle without any requests?

Nothing is lost, but unused capacity doesn't roll over or get refunded — the retainer covers ongoing coverage and availability, not a fixed bank of hours.

Ready To Build

Questions about minor updates? Let's talk it through.