The best first message is specific.
Tell me what the app does, who it is for and where you want to grow. Describe the obstacle in plain language: people are not finding the listing, visitors are not installing, or your team needs a plan for a launch. If you have evidence, summarise it; if it is a suspicion, say that too.
A useful enquiry does not need a deck. The form below goes through Paperform, with a direct form link available if the embed does not load.
What to include when you can.
Share both store links if the app is available on iOS and Android. Identify the country and language that matter most. Mention your release timeline, the people available to implement changes and any constraints. If you have a target budget, it helps shape a realistic scope.
Do not send passwords or account credentials. We can agree appropriate access or report sharing later if the work requires it.
Choose a topic—or ask for direction.
For a diagnosis, choose an ASO audit. For a defined deliverable, explore ASO services. For ongoing judgment and direct involvement, review consulting with Gabriel. You can also simply explain the situation and let the discussion establish the right starting point.
If you are comparing options, the pricing and scope guide explains the details that determine a proposal.
What happens after the enquiry.
I review the context to understand the fit and what further information would be useful. If the work is suitable, we define deliverables, responsibilities and timing before starting. Sending a form is an enquiry, not an agreement to purchase a service.
There is no automated promise of a ranking or outcome. The next useful step is a clear discussion of what your app needs.