App Development Agency Studio

Start here: how this workspace runs

Clients

The companies the agency builds for, from first conversation to a long-term retainer.

Projects

Each app engagement with its stage, budget, launch date and the health of its milestones and bugs.

Milestones

The dated deliveries inside each project, from signed-off designs to store submission.

Bugs

Everything found in testing or by users, ranked by how much it hurts.

Sprints

Two-week sprints with goals, points and client demos.

Change requests

Work beyond the signed scope, priced and decided.

Store releases

Every build through App Store and Google Play review.

Retainers

Monthly support plans and hours used.

What lives where

The week

Your rhythm

Who does what

Account managers own clients, proposals and retainers. Project leads own milestones, sprints and change requests. Developers own bugs and builds. The studio owner reads contract value, approved changes and retainer income.

Numbers we use

Contract value now is the signed budget plus every approved change. Done (%) on a sprint is points done over points planned; under 80 percent two sprints running means re-plan. Hours left this month on a retainer going negative means a conversation with the client before the next invoice, not after.

Making it yours

Rename platforms, contract types and milestone kinds to fit how you work, set your own day rates, and delete the sample rows once your first real project is in.

Delivery at a glance. Charts read the live tables.

Milestones due in the next 7 days

Critical and high bugs

Launching in the next 30 days

How to read the numbers

Scope and releases

Retainer hours

Before the kickoff meeting

The kickoff meeting (two hours)

Discovery sprint

Design sprints

Design runs one sprint ahead of build. The client signs off each screen group before it is built; changes after sign-off are change requests.

First build sprint

Set the Sprint goal in one sentence the client understands, the Points planned, and book the demo. Close the sprint with Close sprint and write Points done. Two sprints in a row under 80 percent done means the plan is wrong, not the team.

Example

Sunrise Language Academy signed a time-and-materials contract for a lesson booking app. In discovery, interviews showed teachers mostly use phones between classes, so the plan put the teacher schedule first. A waitlist for full lessons came up and was logged as a change request rather than squeezed in.

Two weeks before release

Before submitting

Submitting

Set the release to In review. Watch the review status daily. Release manually rather than automatically, so the client can announce it.

When a build is rejected

Set it to Rejected and copy the reviewer's words into Rejection reason. Most rejections are about sign-in options, payments for digital goods, missing privacy details or a demo account that does not work. Fix, reply in the review thread, and resubmit the same day if you can.

Release day

After release

Phased release on the App Store lets you pause if something breaks. Google Play staged rollouts work the same way; start at 20 percent.

Example

Loyalty cards 1.1 was rejected because it offered social sign-in without Sign in with Apple. The team added it in a day, resubmitted with a note to the reviewer, and the build was approved the next afternoon. The rejection reason went into the kickoff checklist for the next project.

What counts as a change

Anything not in the signed scope: a new screen, a new integration, a second language, a different way of doing something already signed off. Bug fixes are not changes. Polish inside an agreed screen usually is not either; use judgment and be generous with small things.

How a change is handled

Fixed-price projects

On fixed price, every approved change adds to the contract. Contract value now shows the signed budget plus approved changes. Invoice changes with the next milestone payment.

Time-and-materials projects

The change still gets logged and estimated, so the client sees what they are buying and the launch date stays honest.

Swaps

Sometimes the client would rather swap: drop something not yet built and add the new thing at equal size. Log the swap as a change at zero price and note what was dropped.

Weekly check

Example

Greenfield Clinic Group asked for a Spanish version two weeks before launch. The lead estimated nine days, priced it at the project's day rate and showed it would move launch by two weeks. The clinic chose to launch in English on time and approve Spanish for the first update.