How to publish your system to the Onremo Store.

A complete dreamer's playbook: what to prep before you submit, how the review works, what makes the difference between a system that gets ten downloads and one that gets a thousand.

April 14, 2026 12 min read Dreamer life

Pre-launch checklist

Think your system is technically working on Aigap? That's necessary but not sufficient. Before publishing to the Store, do this:

5-10 real users: Not friends — actual people with the problem. Have them try it for 1-2 weeks. The changes that come out of those tests are critical.
Performance testing: Are there slow spots? What happens with 100 concurrent users?
Visual prep: Logo, cover image (1280×720), 4-8 screenshots, optional demo video.
Written material: System name, short summary (140 characters), long description (300-1000 words).
Pricing strategy: One-time or subscription? How much?

Step 1: Dreamer Panel

Go to the Dreamer Panel. In the left nav, click My Systems.

You'll see your system in "Draft" status. Click it to enter edit mode.

Step 2: System details

Name: 60-character limit. Don't be too creative — pick something findable on Google. Like "Booking+".

Short summary: The 140 characters that appear under the card in the Store listing. Problem + solution format: "Solves booking chaos for salons; one panel for the staff calendar."

Long description: Markdown supported. Suggested structure:

What problem does it solve?
Who is it for?
Key features (5-8 bullets)
Who is it NOT for? (e.g. enterprise chains)
Version history / roadmap

Step 3: Visual assets

Logo (200×200 PNG): Aigap auto-generates a logo. If you don't like it, upload your own. Transparent background preferred.

Cover image (1280×720): Appears at the top of the product card and detail page. Show the strongest screen of your system.

Screenshots (1920×1080, at least 4): Frames showing different pages of the system. Tip: Before screenshotting, populate the system with realistic-looking mock data so it looks lived-in.

Demo video (optional but recommended): 30-90 seconds. Record with Loom or Screen Studio. A demo video lifts conversion roughly 40%.

Step 4: Category and tags

Pick one primary category: E-commerce, CRM & Sales, Finance, Productivity, AI, Vertical.

Add 3-5 tags: #booking, #salon, #small-business. Tags drive search results and filters.

Don't spam tags — adding "#accounting" when you're actually a booking system can get your listing rejected during review.

Step 5: Pricing

Three models:

(a) One-time: $20-500. Most systems serving SMBs sit at $50-200. Pros: customer pays once and forgets it, no churn pressure. Cons: one-shot revenue.

(b) Monthly subscription: $5-100/month. Suits AI assistants, CRMs — systems that operate continuously. Pros: predictable revenue. Cons: churn risk.

(c) Usage-based: Per-SMS, per-booking, per-sale commission. Makes sense at scale, cheap entry for small users.

First-launch recommendation: One-time, mid-tier price ($50-150). You can change it later.

Step 6: Submit for review

Click "Submit for review." Your system goes to "In review." The Aigap review team evaluates within 5-7 business days:

Technical tests: Performance, security vulnerabilities (XSS, SQL injection), accessibility (a11y).
Content review: Is the description accurate? Do the images represent the system correctly? Are the tags appropriate?
Price-to-value: Does the price justify what the system actually delivers?
Store content: Is there added value, or is this nearly identical to an existing system?

First-attempt approval rate is 52%; second attempt is 85%. If a revision is needed, you'll get an email.

The first week after launch

Once approved, you get a "New" badge featured for 24 hours. First-week to-dos:

Announce on Twitter/LinkedIn. Even a 200-500-follower account can drive first sales.
Share in relevant industry communities. Reddit subforums, Facebook groups, Slack communities.
Personally reach out to your first 5 buyers. Their feedback is gold for the next version.
Proactively ask for the first reviews. Politely ask satisfied customers to leave one. The first 5 reviews weigh heavily in the Store algorithm.

Subsequent versions

Successful Store systems ship at least one version per month (a bump like v1.2.0 → v1.2.1). Static systems get forgotten in 6 months.

Releasing a version from Aigap is one click; the Onremo Store listing updates automatically.

For every version, write "Release notes" — users see what's new and trust grows.