Research time follows scope.
One listing in one market is different from two stores across several languages. Existing product knowledge, usable reports and access to the right people affect how quickly a diagnosis can be formed. Missing evidence can require investigation before a responsible recommendation is possible.
Agree the scope first. The pricing and scope page explains why apps, stores, markets and deliverables change the size of the engagement.
Production has its own dependencies.
Copy, design, localisation and approval are separate tasks. A screenshot brief can be ready while the underlying product screen is still changing. A translation may need native review. A legal or product claim may need internal verification.
Put owners and dependencies on the schedule. Treating all of this as “ASO delivery” hides the reason a date moves and makes accountability harder.
Publishing is not the same as implementation approval.
An internally approved recommendation still needs to be prepared and released through the relevant store workflow. Coordinate listing changes with your product release and campaign plan. Record what actually became visible, not just the date a document was handed over.
The consulting process separates recommendations, publishing ownership and evaluation. A timestamped change log is more useful than relying on memory.
Learning time depends on the question and data.
A comprehension problem may be visible immediately in a review. A behavioural hypothesis needs appropriate evidence. Experiment duration depends on traffic, baseline behaviour, the effect being investigated and the test configuration. A quiet listing cannot be expected to provide the same amount of evidence as a busy one.
Use the available platform planning tools and a defined hypothesis. Do not promise a conclusive result by a convenient reporting date.
Review signals without declaring victory early.
A short-term change in ranking or conversion can coincide with campaigns, seasonal demand, a release or a different audience mix. Compare relevant periods and document those changes. One favourable day is not a durable outcome.
An audit helps establish the baseline. Review the same definitions later so the comparison does not silently change.
Ask for milestones you can hold people to.
A useful plan names the dates for a brief, research review, draft, approval and handoff, with dependencies attached. It also identifies when evidence will be reviewed and what happens if the data is inconclusive. These are more meaningful commitments than a guaranteed position by a deadline.
If you need work completed around a launch, share the date early through the project enquiry. Scope can be prioritised around constraints without pretending the store’s response is under our control.
