Astrooly: Paid SaaS in Three Languages

Natal charts, localized Stripe checkout, cash referrals and analytics, built end to end

Astrooly needed a full product: chart engine, AI readings, three-language payments, country pricing, cash referrals and analytics. We built all of it; organic clicks came within 10 days.

SaaS · Full-stack product build

Astrooly: Paid SaaS in Three Languages
Client
Astrooly
Languages
3, including Stripe checkout
Payments
Stripe, country-based pricing, promo codes
SEO result
Organic clicks visible in 10 days
Stack
Next.js · Stripe · GTM · GA4 · Clarity

SaaSNext.jsStripeMultilingualReferral systemSEO + GEO

What Astrooly needed

Astrooly turns birth data into a natal chart and AI-assisted readings. It needed a real product from day one: three languages with payments in each, server-side country pricing, promo codes, cash referrals, an admin view and full tracking. No starter kit covers that, so we built it end to end on Next.js. SEO and GEO shipped in the first release, on a domain with prior history. Organic clicks appeared in Google Search Console within 10 days of launch.

Astrooly natal chart wheel, a personalised birth chart visualisation
Natal wheel generated from birth date, time and location

Constraints we had to design around

  • 01

    Stripe checkout in three languages

    Stripe's locale parameter translates the interface, not your product names. Users arriving from a Czech session had to see Czech product descriptions on the hosted checkout page too.

  • 02

    Country pricing with imperfect detection

    VPNs and corporate proxies produce wrong country signals. Pricing had to stay consistent and never break the Stripe session on an unexpected result.

  • 03

    Cash commissions need exact attribution

    Referrers get paid, so the funnel from click to paid conversion had to be accurate and never overcount.

  • 04

    Organic growth from a standing start

    The product had no content authority in its niche. SEO and GEO had to be part of the architecture, not a later marketing task.

Architecture and what we shipped

  1. 01

    Chart engine with AI-assisted readings

    Planetary positions calculated from birth data, rendered as a visual natal wheel, then structured readings for natal charts and compatibility reports.

  2. 02

    Localized Stripe checkout with country pricing

    Stripe locale sets the checkout language, custom fields carry translated product text, and server-side geolocation picks the price tier before the session exists. Promo codes included.

  3. 03

    Server-side referral attribution

    Each referrer gets a unique link. Clicks, signups, paid conversions and commission are tracked server-side, surviving ad blockers, and shown in a referrer dashboard.

  4. 04

    Admin dashboard on the same stack

    An authenticated admin route shows free charts, paid charts and compatibility reports generated, and by whom. No separate internal app to maintain.

  5. 05

    Technical SEO and GEO in the first release

    Server rendering, structured data, canonical URLs and hreflang from the start, plus AI citability and entity clarity work built in rather than bolted on.

  6. 06

    All tracking through GTM

    Google Ads conversions, Meta Pixel, Microsoft Clarity and GA4 events run as GTM tags. The codebase stays clean and tag changes need no deploy.

Proof from the first weeks

Shipped in three phases

Core product first, then money (payments and referrals), then growth (SEO and analytics). Organic clicks appeared within 10 days of launch.

  1. Phase 1

    Core platform

    Chart calculation engine, natal wheel, AI-assisted readings, UI in 3 languages

  2. Phase 2

    Payments and referrals

    Stripe with country pricing, 3-language checkout, promo codes, cash referral system, admin dashboard

  3. Phase 3

    SEO and analytics

    Technical SEO, GEO, structured data, GTM with Google Ads, Meta Pixel, Clarity and GA4

Outcome

10 days

From launch to first measurable organic clicks in Google Search Console

3 languages

Supported end to end: UI, Stripe checkout and product descriptions

4 tools

Analytics and ad platforms connected via GTM: Google Ads, Meta Pixel, Clarity, GA4

Questions teams ask about SaaS builds

Can you build a multilingual SaaS with Stripe checkout in each language?

Yes. We set Stripe's locale for the checkout interface and pass translated product names and descriptions through custom fields, so users see their own language across the whole payment flow, including the Stripe-hosted page.

How does country-based pricing work technically?

The server reads the request IP and runs a geolocation lookup before creating the Stripe session. The country maps to a pricing tier that sets currency and amount. If detection fails, a default price applies, so checkout never breaks.

How do you build a referral system that pays cash commissions?

Each referrer gets a unique link. Clicks, signups and paid conversions are attributed and stored server-side, which survives ad blockers. Referrers see the full funnel and their commission in a dashboard inside the app.

Why did organic results appear within 10 days?

The domain had prior history, which gave an authority head start. On top of that, server rendering, structured data and GEO work were in the first release, so Google could crawl, index and trust the site quickly.

How do you set up tracking without cluttering the codebase?

All tags, Google Ads conversions, Meta Pixel purchase events, Clarity and GA4, run through Google Tag Manager. Marketing can change tags without a code deploy.

Payments, referrals, analytics, SEO. One team, one fixed price.

If your product needs more than a landing page and a Stripe link, tell us what it must do. We'll scope it and quote the build.

Tell us what you're building

Prefer to talk? Pick a 30-minute slot.

sales [at] yarify.tech WhatsApp Telegram