Your app is live. The link works. Now you need someone to try it.
If you built it through vibe coding with Lovable, Bolt or Replit, you already know how far a clear prompt can take you. Finding your first users takes another kind of work: choosing an audience, showing them something useful, and helping them get started.
Hamla, your AI marketing team, connects those steps to what happens inside your app. Your coding agent can handle the integration; you choose the audience, review the campaign, and decide when to launch.
Start with two things: connect the app, then run one focused launch.
Connect your app while you build
Give the setup to your coding agent
For a coding agent that can edit your project—such as Cursor, Claude Code or Codex—start with Hamla’s installation instructions. The same procedure is available as a Claude Code skill or Cursor rule.
You can start with a request like this:
Read https://hamla.io/AGENTS.md and install Hamla on this app. If I do not have a Hamla business yet, request a claimable install, add the returned snippet, and give me the claim link.
The public install API returns a business ID, a website snippet, and a single-use claim link. That lets your agent add Hamla before you have an account. You then sign in or create your own account and claim the installation within 72 hours.
The agent creates an installation, not your personal account. Before you claim it, the installation records anonymous activity only. Collecting contact details, issuing secret API keys and launching campaigns require ownership. Keep the claim link private: the person who uses it takes ownership.
Send the moments that matter
The website snippet shows you visits and sources. Hamla Events tell you what happens inside the product.
Take a fictional app that turns scattered client requests into a project plan. A signup matters, but creating a plan is the first sign that someone has used the feature. After claiming the installation, ask your coding agent to connect three moments:
- account_created: someone registered.
- project_plan_created: someone created a plan.
- subscription_started: someone paid. Send this from the payment handler with type: purchase, the amount and currency.
These are example event names; use names that fit your app. Link them to the right person using your app’s stable customer ID.
Then configure the campaign around the outcome you want. A signup event can start a welcome sequence. Creating the first plan can be its conversion goal, stopping the remaining follow-up steps once the person succeeds. Events also give you a way to build audiences from product activity.
Ask your agent to follow the developer reference. Keep secret keys on the server and use the same idempotency key when retrying a server event. Before launching, run a test signup and create a test plan. Check that both appear in Hamla.
Keep using your preferred assistant
You can use ChatGPT to work through your audience, offer and launch copy. To have an assistant act on your Hamla business, it needs access to Hamla’s tools.
The installation skill helps your coding agent wire up the app. Hamla’s MCP connector lets a supported assistant work with your Hamla business after you sign in through OAuth.
You can ask that assistant to prepare a campaign or inspect the reporting with Hamla’s available tools. Your connected accounts and permissions determine what it can do. You can also work directly in Hamla’s dashboard.
How to get your first users after vibe coding
Market your app to one audience with one useful demonstration
For the project-planning app, start with freelance designers dealing with unclear client briefs.
“An AI productivity app” describes a category. “Turn a messy client brief into a project plan” gives a designer a reason to try it.
Use a brief you have actually run through your app, with private information removed. Show the input and the resulting plan. Then ask Hamla to prepare the launch post:
Create a LinkedIn post for freelance designers using this before-and-after example. Show how the app turns a client brief into a project plan. Invite people to try it with their own brief, and link to my app.
With a connected LinkedIn account and your supplied images, Hamla can prepare a post for you to review and publish.
Choose where that demonstration belongs: your LinkedIn audience, a design community you participate in, or a conversation about the problem. You handle community participation and outreach; Hamla can prepare content and publish supported posts through your connected accounts.
Give interested people a clear next step
If the app is ready, guide visitors toward creating their first plan. If you are collecting early interest, offer a waitlist instead. Choose the action that matches what people can actually do today.
Hamla can create an onsite signup form or popup once its website SDK is installed on your claimed business.
A signup is the beginning. Your product events let you see whether that person goes on to use the feature—and help you configure follow-up around that next step.
Review, launch and learn
Review the campaign’s content, audience, links and setup before approving the launch. The approval card appears in your Hamla chat, including on mobile, so you can review it from your phone.
After launch, compare the available channel reporting with your product events. Did people visit? Did they sign up? Did they create their first plan?
Visits without signups give you a reason to examine the page and its offer. Signups without a first plan give you a reason to examine the first-use experience. A small launch gives you questions to investigate; it does not prove what caused the result.
Start with one audience, one useful demonstration and one activation goal. Let your coding agent connect the app, then use Hamla to prepare the campaign and learn what needs to change next.
Screenshots show illustrative demo content.
Give your coding agent Hamla’s installation instructions, or open Hamla to prepare your first campaign.
