RETRACTED, 2026-08-06
We used to claim Storia was the first AI SaaS wedding-planning platform built for the Philippines. We have withdrawn that claim. We are no longer asserting it, and we are not asserting it was correct either.
When we published this claim on 2026-05-15, we committed to one thing above all: if a competitor satisfied all four of our criteria and shipped before 2026-05-13, we would retract within 48 hours of confirming it. We withdrew the claim on 2026-08-06. This is us keeping the promise.
Correction, 2026-08-08. Our 2026-08-06 notice said we had "confirmed" that a competitor met all four criteria before our cutoff. We had not. That word was wrong and we are removing it. See the correction note directly below.
What we found. A competitor, Vowly-ph.com, now advertises six AI assistants including an invitation writer, a seating optimiser, and a timeline generator, which are planning outputs rather than writing helpers. On its current public surface it appears to satisfy all four of our criteria. That is a statement about today, not about May.
What that means for each claim. We are not the only such platform, and that word stays withdrawn. Whether we were first is a question about dates, and we no longer believe our dating evidence was sound. Resolved 2026-08-11: we retired the claim permanently rather than reinstate it or rewrite it into a narrower version. We cannot verify a competitor's ship date and neither can you, so it is not a claim we should ever have rested on. What we claim now, and how to check each item yourself, is at storia.ph/moat.
What we are not doing. We are not quietly deleting the page, rewording the claim into something technically survivable, or waiting to see whether anyone noticed. Nobody challenged us. We found this ourselves while researching competitors, and we are publishing it because a claim that is only auditable when convenient was never auditable.
Correction note, 2026-08-08: why the dating evidence failed.
Our 2026-08-06 notice rested on a single artifact: a competitor blog post dated 2026-03-09 describing a shipped product. We treated that date as fact. It does not hold up.
That site's domain was registered on 2026-03-08. Twelve of its blog posts carry dates before the domain existed, running from 2026-01-25, and the phrase "6 AI assistants" appears in posts dated as early as 2026-01-25, roughly six weeks before the domain was created. Its sitemap dates one route to 2026-03-01, a week before registration. Post dates on that site are not evidence of when anything shipped.
We also failed to check our own records. An internal verification completed on 2026-06-07, three weeks after our cutoff, had assessed the same competitor's AI as single-shot text tools of the kind our criteria already exclude, and a hands-on test on 2026-06-09 found the feature paywalled and untestable. We did not consult either before publishing. We are stating this plainly because a claim framework that only gets audited when it is convenient was never a framework.
We are not accusing anyone of anything. We cannot establish when that competitor's AI features actually shipped, and it is entirely possible they predate our cutoff. Our point is narrower and is about us: we said "confirmed" when we had not confirmed, and we published that about a named third party. That was our error to fix.
The four criteria below are unchanged and still useful, so the rest of this post stands as written. Read it as a framework for judging any tool's AI claims, including ours.
This post originally argued that Storia was first. It is now the record of how that claim was tested and withdrawn. The four criteria we used are below, along with the exclusion list, our verification process, and the correction itself.
Why the claim is in writing
Under RA 11967 (the Internet Transactions Act of 2023), any "first," "only," or "best" claim made to a Filipino consumer is competitor-disputable. The protection a brand has against statutory liability under section 10 (unfair or deceptive practice) is a written definition that names the category precisely and lists what does not count.
We wrote that document on May 13, 2026, before any "first" claim was published on a marketing surface. This blog post is the public version of it. The internal source (with the panel-ratification record and quarterly verification cadence) lives in our governance ledger.
Same compliance pattern we used for the "Free" claim on the Wedding DNA quiz CTA in April 2026.
The four criteria
A platform qualifies as an "AI SaaS wedding-planning platform" only if it satisfies all four simultaneously. Three out of four does not count.
1. Wedding-specific
The primary user task is planning a wedding, not a general-purpose tool being repurposed for one. Wedding semantics (ceremony types, guest list mechanics, vendor classes, paperwork) are first-class objects in the product, not afterthoughts.
This excludes general AI chatbots that a couple uses for caption help or budget questions. It also excludes a website builder that happens to have wedding templates.
2. SaaS
Subscription or tier-based access with persistent state, multi-user collaboration, and a paid product surface. Not a one-time service. Not a directory of vendors. Not a free template gallery. Not a one-shot AI chatbot session.
This excludes wedding-coordinator agencies (which are full-service businesses, not SaaS products). It also excludes vendor marketplaces that take a commission on inquiries without offering a planning workspace.
3. AI-driven
AI is the load-bearing product engine, not a marketing add-on or a sub-feature shelf. The product must produce a personalized output (moodboard, website, timeline, vendor screening dialogue, copy) that the couple could not get from a static template. The output is generated by a foundation model at request time.
This is the criterion that most "AI wedding" claims fail. A speech writer or a hashtag generator is a writing helper, not a load-bearing planning engine. A budget calculator with a percentage formula is not AI. A vendor-matching feature inside a marketplace is a feature, not a platform.
4. Built for the Philippines
Cultural, regulatory, and economic context is in the product, not bolted on as a localization layer. This means Filipino ceremony types (Catholic, Civil, Christian, Muslim Nikah, INC, Tsinoy, interfaith and more), peso pricing in Tagalog and English (Cebuano-leaning register where it warms), and compliance posture against the Philippine consumer-protection statute stack (RA 11967, RA 10173, RA 7394, RA 8371, RA 11596).
This is also the criterion that lets us draw a line between Storia and the Western planners (Joy, Zola, The Knot, WeddingWire). Those tools can localize. None have. The economics of foreign-app localization do not close on a single-country market the size of the Philippines unless you are built here.
How Storia scores against the four criteria
Storia satisfies all four. On its current public surface, so does Vowly. What follows is a description of what Storia does, not a claim to priority.
Wedding-specific. The Wedding DNA quiz is built around 7 Filipino ceremony types and a cohort-aware style profile. The paperwork tracker covers Pre-Cana, NSO/PSA, CENOMAR, parish or NCMF, congregation registry, LCR, and marriage license. Guest lists model PH-specific relationships: ninong, ninang, principal sponsors, entourage by side, family hierarchy.
SaaS. Bronze (₱4,995), Silver (₱9,995), Gold (₱24,999), and Bespoke (quote-based, co-designed at booking) packages with persistent state across user sessions, partner alignment for two-couple workspaces, team-member invitations for coordinators, and vendor collaboration. Packages are one-time and active through your wedding, not a recurring subscription.
AI-driven. Production-grade foundation models for text and image generation are load-bearing across the product:
- Moodboard generation at request time, cohort-aware
- Hiraya AI, the planning assistant, context-aware on the couple's actual budget, timeline, and guest list
- Layon AI, the wedding-vendor screening conversation
Without the AI engine, the product is materially less valuable. We did not bolt AI on top of a checklist app. Specific AI sub-processors are disclosed in our Privacy Policy per RA 10173 transparency obligations.
Built for the Philippines. Documented architectural principles for Filipino-specific design. Cultural validation processes draw on local Filipino expertise across the ceremony types we support. Compliance posture continuously reviewed against the Philippine Internet Transactions Act, Data Privacy Act, and Consumer Act.