Case studies

One workflow, three honest product stories.

Keyword Astro is the method behind three tracks: PixelBoats, its own RC proof, and a QBO ops workflow. Every chart on this page runs on sample data — nothing is claimed past what the screenshots show.

Keyword Astro Explorer with sample run summary 3 ok, 0 failed Sample data · 3 ok / 0 failed

Real-world use flow

From seed keyword to store-ready metadata draft.

Five stops, one loop: collect, check health, compose metadata, save locally, and prove what ships. Screenshots are sample data from the app’s demo seed.

  1. 01 · Collect

    Seed one idea. Batch-verify three providers.

    Drop a seed keyword, toggle batch, and let Explorer query every source at once. Combined suggestions land first, with each provider’s own result and status beside them.

    Demo data · no provider calls made.

    attempted 3 / eligible 3 · 3 ok · 0 failed
    Keyword Astro Explorer with combined and per-service suggestions on sample data
    Keyword Astro batch progress with current seed status on sample data

  2. 02 · Health

    Failures stay visible.

    Service stats keep per-provider health in the open, and a 429 surfaces with its cause plus Retry and Disable. The tool shows what failed and why.

    Sample data · one provider returned HTTP 429.

    Per-service error surfaced
    Keyword Astro service stats toggles and health metrics on sample data
    Keyword Astro per-service 429 error with Retry and Disable on sample data

  3. 03 · Compose

    Draft all three store lanes in one view.

    Apple, Google Play, and Microsoft Store metadata live side by side, with character counters that keep fields honest.

    Example keyword field · 30/100 characters.

    Apple · Google Play · Microsoft
    Keyword Astro Store Drafts Apple lane on sample data
    Keyword Astro Store Drafts Google Play lane on sample data
    Keyword Astro Store Drafts Microsoft Store lane on sample data

  4. 04 · Save

    Everything stays on device.

    Runs, drafts, rank snapshots, and translations save into local Projects and export as clean TXT, CSV, or JSON.

    Local-first · no account required.

    Saved runs · drafts · snapshots
    Keyword Astro Projects list with saved runs on sample data
    Keyword Astro ASO drafts saved to a project on sample data
    Keyword Astro rank snapshots and translation drafts on sample data

  5. 05 · Proof

    Evidence-backed, and under your control.

    The feature matrix shows what ships today, while the shell keeps diagnostics and a two-click clear-local-data control in reach.

    Feature matrix · release-scoped.

    Matrix + local-data control
    Keyword Astro feature matrix snapshot
    Keyword Astro desktop shell controls
    Keyword Astro two-click clear local data confirmation

Interactive proof

The product demos itself.

The click-funnel demo replays the same workflow with 40 seeded visitors — sample data that stays in your browser.

Click-funnel demo seeded overview
Initial
Click-funnel demo after live clicks
Mid-progress
Click-funnel demo completion state
Complete
Worked example

Example values from the app's demo seed — a sample of the workflow, not a measurement.

StepExample output
Seed keywordsleep sounds
Combined suggestions (sample)sleep sounds black screen · sleep sounds for adults · sleep sounds rain · sleep sounds white noise
Apple keyword field (example)sleep sounds, rain noise, white noise — 30/100 characters
OutputsTXT / CSV / JSON export · project save · rank snapshot import

Case-study system

Three tracks, one claim discipline.

Each track documents what existed, what changed, the evidence we can show — and the claims we deliberately keep out of reach.

Lead case study

PixelBoats visual product track

From PixelBoats prototype to Android-first visual product: using ASO thinking before the store listing exists.

Before: Marketing language still reads like a prototype route demo.

  • Draft Google Play metadata around real intent: pixel art live wallpaper, pirate ship wallpaper, animated ocean background, and cozy nautical wallpaper.
  • Separate game-player copy from wallpaper-buyer copy.
View the visual product proof

Claimed

  • Product strategy
  • Visual direction
  • ASO metadata draft
  • Proof checklist

Not claimed without proof

  • Play Store approval
  • Ranking
  • Install growth
Full not-claimed list (5 items)
  • Play Store approval
  • Ranking
  • Install growth
  • Paid conversion
  • Production wallpaper readiness
Method proof

Keyword Astro on itself

Building a Windows-first ASO command center by using the product on itself.

Before: A useful Tauri and Svelte app existed, but the commercial story was buried in release tasks.

  • Reposition the product as a Windows-first ASO command center, not a clone.
  • Make Apple, Google Play, and Microsoft Store metadata lanes explicit.
Check RC status

Claimed

  • Source-labelled workflow
  • Local-first projects
  • Cross-store drafting
  • Screenshots

Not claimed without proof

  • Rank improvement
  • Revenue
  • Downloads
Full not-claimed list (6 items)
  • Rank improvement
  • Revenue
  • Downloads
  • Popularity or difficulty accuracy
  • Competitor extraction
  • Daily tracking
Constrained ops case

QBO Mail Dashboard ops workflow

Turning a boring QuickBooks mail dashboard into a productized operations workflow.

Before: Connects to QuickBooks Online via OAuth.

  • Treat UI labels, README language, and route metadata as product surfaces.
  • Replace bulk-email framing with controlled owner-managed communication.
Ask about ops productization

Claimed

  • Internal admin tool
  • QBO OAuth integration
  • Contact sync
  • Cached exports

Not claimed without proof

  • Public SaaS
  • Campaign platform
  • Compliant bulk email service
Full not-claimed list (4 items)
  • Public SaaS
  • Campaign platform
  • Compliant bulk email service
  • Proven time savings without metrics

Follow the evidence.

Every track ends in one place: check the RC screenshots, or read the workflow that produced them.

Check RC download status View screenshots Read the workflow

All screenshots show sample or demo data — captured, not judged. Canonical articles are planned for the Canopy blog; this page stays inside the claim boundaries above.