Work directly with Gabriel

ASO audit. Find the leak before buying another bucket.

Your app is live. Growth is flat. The report is somehow thriving. I review your listing, competitor evidence and available store data to identify what needs fixing, what needs investigating and what deserves a test. You get annotated findings and priorities your team can act on.

Get my ASO audit scope

The outputs, fee and handover agreed upfront. Work directly with Gabriel.

A cracked bucket reveals leaks at several levels, illustrating an ASO audit.

The diagnosis

Is this where your listing hurts?

You are about to rewrite the listing, buy more traffic or renew an agency contract without knowing what is holding the app back. Start here when you need a diagnosis, a second opinion or a sensible order for the work.

Tell me what’s going wrong ↗

The handover

What lands besides the invoice

  • A review of the agreed store, market and relevant competitors

  • Annotated findings showing the problem, evidence and proposed change

  • A ranked action list with owners and information still needed

  • A handover discussion so your team knows what to do next

We agree the stores, markets, outputs and review rounds before work starts.

The actual work

Diagnose. Fix. Hand it over.

  1. Baseline and context

    Agree the app, store, market and business question. Review console exports when available; a public-only review is explicitly limited to observable listing evidence.

  2. Research and diagnosis

    Inspect relevant competitors, metadata, creative and user-language themes. Distinguish confirmed problems, plausible hypotheses and information that is still missing.

  3. Prioritized handover

    Receive findings with evidence, recommended actions, confidence and ownership. Discuss what needs implementation, what needs testing and what the product team should investigate.

Inside the work

A deliverable, not a séance.

Illustrative finding: the opening screenshot promises automatic route planning, but the product is a manual hiking journal. The recommendation is to correct that expectation before testing cosmetic variants.

An illustration of the work. Your project starts with your own app and evidence.

Before the invoice

The work, the fee and the exit.

I’ll agree the deliverables, responsibilities, fee and schedule with you before work begins. A focused project is fine. Monthly management is optional.

Implementation, asset production, translations and campaign management are separate scope decisions. Rankings and install growth cannot be guaranteed.

What to send me

  • Store URLs, target markets and current objective
  • Relevant console exports if a performance diagnosis is needed
  • Recent listing changes, product releases and campaign context

The small print, readable

Questions before we start

How is this different from the free teardown?

The free teardown is a short review of the public listing. A paid audit investigates an agreed question in more depth, uses relevant console evidence when available and produces a prioritized action plan.

Will you rewrite the listing too?

The audit identifies and prioritizes changes. Copywriting, design production and publishing are included only when named in the project scope.

Do I need to give you console access?

A public listing review can start with a URL. Performance diagnosis needs relevant reports or agreed access. We decide what is needed for your question before the project starts.

Your turn

Get my ASO audit scope

Your store link and main question are enough to start. Include the priority market if you know it.

I’ll recommend a starting point and explain the scope, fee and information needed. No account-manager relay race.

Replies come from Gabriel, usually within a working day.

Prefer to do the surgery yourself?

Browse related lessons and tools

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.