Grafeat does the work behind every feature.

• It collects challenge submissions, checks the rules, builds your carousel and keeps every credit in order. You choose the work worth featuring.

Great work deserves to be featured.

• Grafeat collects your challenge submissions, checks the rules, prepares your carousel and keeps every credit in order. You choose what makes the cut.

4. But I would remove one claim we haven’t established yet

Under Reels:

“Featured Reels can be republished without their original audio.” grafeat-lp.pdf

And step 9 says:

“Reel audio removed if you want.” grafeat-lp.pdf

That’s more implementation-specific than the rest of the LP and is still something the spike was supposed to validate. Unless we’ve already empirically proven the complete retrieve → process → republish Reel flow, I’d remove the promise for now.

It isn’t central to the value proposition anyway.

5. I’d reconsider “Ten steps, thirty-one times”

The section says:

“Ten steps, thirty-one times. Challenge Curator takes the bookkeeping…” grafeat-lp.pdf

Besides needing the Grafeat rename, “thirty-one times” makes the product unnecessarily October-specific. Not every challenge is monthly or 31 days.

I’d make it something like:

The same ritual, every day of the challenge. Grafeat takes the repetitive bookkeeping and leaves you the judgment: which work you love, and the order it’s shown in.

Then the numbered 10-step workflow communicates the rest.

7. One UX wording I still want changed in Settings

We discussed this previously: wherever the hashtag template configuration uses “Name”, I’d use “Hashtag base”. It prevents ambiguity with Challenge name.

And I still like Calendar over Days if that’s now what the UI uses—the screenshot already shows Calendar in the Settings navigation.

8. One LP concern: it’s long, but I would leave it long for now

Normally I’d challenge the amount of detail between the demo and CTA. But this is an early-access validation LP for a fairly unfamiliar workflow, not a mature high-volume signup page.

The sequence actually makes sense:

Promise → interactive proof → workflow → deeper differentiators → recurrence → FAQ → research CTA.

And the demo near the top means users don’t need to read the entire page to understand the product. The detailed material also becomes useful when Meta reviewers eventually inspect grafeat.com.