Mashdun
AI GrowthWorkCapabilitiesIntegrationsProcessLabsMarketplaceBlogAbout
Get in Touch
Mashdun

Full-stack web developer, AI engineer & growth marketer. Building production-grade apps and intelligent solutions.

Navigation

  • Portfolio
  • Capabilities
  • Process
  • Labs
  • About

Resources

  • Blog / Notes
  • Marketplace
  • Contact
  • RSS Feed

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Do Not Sell or Share
  • Delete my data

© 2026 Mashdun. All rights reserved.

Built with Next.js, Tailwind CSS & Prisma

    All Labs
    Marketing
    Scored CRO
    Explainable
    Test Planning
    Brand Voice

    Growth Studio

    Point it at a live landing page. A deterministic rubric — readability, jargon density, reader focus, CTA strength, specificity, passive voice, seven measures with published weights — scores the copy with no model involved, and that scorecard becomes the brief the model rewrites against. Every variant is re-scored by the same code, so the improvement is measured rather than claimed, and what a rewrite traded away is reported alongside what it gained. Promote a variant to the results ledger, enter what the traffic did, and a two-proportion z-test calls the winner — which lets the ledger do the thing tools like this never do and grade the rubric: how often did the higher-scoring arm actually win? A competitor diff scores several pages against the same measures with no model at all, and a stability check runs one prompt repeatedly to show how much the model disagrees with itself. Ad variants, SEO briefs, and brand-voice enforcement round out the lab.

    Growth Studio

    Scored CRO
    Results Ledger
    Competitor Diff
    Model Stability

    How it works

    1. Landing: fetch a live page, score it on a deterministic rubric — no model involved
    2. The scorecard becomes the brief, and every variant is re-scored by the same code
    3. Ledger: enter what the traffic did, and the z-test — not you — calls the winner
    4. Which lets the ledger grade the rubric: how often did the higher score actually win?
    5. Stability runs one prompt several times to show how much the model disagrees with itself

    From real client work

    Anyone can generate landing copy now, so generating it is not the product. The rubric is: seven measures with published weights, run identically on the original and on the model's rewrite, in code the model never sees. It reports what each variant traded away as readily as what it gained, prices the test, and then — the part that costs something to admit — records what really happened and scores the rubric against it. If the higher-scoring arm keeps losing, that is the rubric's problem and this says so.

    Read the results when the test finishes