Slop*Detector

INCONCLUSIVE — slop score 39/100

The evidence points toward template assembly rather than outright fabrication, which is why this one lands at 45 out of 100 instead of higher. The three-step section with faint '01,' '02,' '03' numerals behind IMPORT/CONFIGURE/EMBED, followed by a 2x2 grid of single-letter R/A/C/L cards, is close to a textbook generated landing page skeleton. The closing 'Ready to ship your copilot?' banner just repeats the hero's Join Waitlist button and email field almost word for word, and the Before/After chat mockup uses gray placeholder bars standing in for a CRM interface, which suggests the screenshot was staged rather than pulled from a working product. None of that rules out a person building fast with a component library and a deadline, and the copy in places (reads data, creates records, and runs actions) is specific enough that it doesn't read as pure filler. Given the mix of layout tells with concrete, plausible product detail, inconclusive is the right call here; someone made real decisions about what this product does, even if they leaned hard on default UI patterns to ship it.

Findings

• Feature-tile grid — Equal-width card grids of 3–4 identical tiles (icon, subheader, blurb) are the signature layout block of generated landing pages.
• Gradient backgrounds / gradient text — Large gradient washes and gradient-clipped headline text (usually blue→purple) are the default decoration of generated UI.
• Numbered 1-2-3 step section — The 'From your API to a working copilot in three steps' section uses large decorative '01', '02', '03' numerals behind IMPORT/CONFIGURE/EMBED labels — the classic stamped-on numbered sequence used as filler decoration rather than genuine step visualization.
• Feature-tile grid — Below the three-step section is a 2x2 grid of near-identical cards, each with a single-letter badge icon, bold title, and two lines of blurb — the textbook AI feature-grid pattern (R/A/C/L acronym cards).
• Stock CTA pair — The hero uses the generic paired call-to-action pattern of a primary black button plus a lighter secondary button, mirroring the canonical 'Get Started / Learn More' template default.
• Template skeleton / redundant CTA banner — A near-duplicate 'Ready to ship your copilot?' dark banner with email capture and Join Waitlist button restates the hero's CTA almost verbatim, filling the standard closing-CTA template slot without adding new information.
• Warm amber/cream accent palette as safe default — The site leans on a warm amber/gold accent color for the headline highlight and a cream/blush background section — one of the emerging 'tasteful default' palettes called out as a low-effort safe choice replacing indigo gradients.
• Mocked fake product screenshot — The 'Before/After' chat widget mockup shows placeholder gray bars standing in for a CRM UI, with a scripted canned exchange, typical of a fabricated screenshot rather than a real product capture.
• 'From X to Y' sweeping construction — The guide flags this exact catch-all range construction as a filler pattern common in generated copy, and it appears verbatim here as a section header.
• Rule-of-three triads — Several feature lists use three-item parallel structures (reads data, creates records, and runs actions; create records, update fields, and trigger workflows), which is a mild machine-rhythm tell, though here the items are concrete and distinct rather than vague filler.
• Minor 'not just X' reframe echo — This is a softer variant of the banned appositive reframe ('X, not Y'), tacking a corrective clause onto the end of a sentence rather than stating the point directly.