Neophyte icon

Neophyte

Neophyte uses an AI browser to test website onboarding, uncover signup friction and activation blockers, and assess agent readiness with recorded reports and replays.

Neophyte

AI-assisted onboarding testing

Neophyte is an onboarding and first-run testing service for websites and web products. It uses an AI-controlled browser to act as a brand-new user: it signs up with a run-specific email identity, completes available verification, and works toward a task or first meaningful action without a prewritten script.

The service records the journey and reports what worked, where a person or AI agent might encounter friction, and whether the requested goal was reached. It is intended for product teams and site owners evaluating signup, verification, setup, early activation, and agent accessibility from an outside-user perspective.

Features

Unscripted first-run exploration

The agent starts without a supplied script or prior product context, infers what the site is for, and determines the next step from the page it sees.

New-user signup and verification

Neophyte creates a run-specific email identity, reads verification messages or codes in its own mailbox, and works through signup and setup without using the customer's inbox.

Custom onboarding goals

You define the task and stopping point. The agent navigates toward that goal and records whether it arrived or where the journey broke down.

Recorded reports and replays

Reports include a human-and-agent rank, a friction report, replay of the run, and a product-flow view. Public reports can be shared by link unless privacy settings apply.

Agent-readiness checks

In addition to the browser journey, runs perform agent-readiness checks for resources such as robots.txt, sitemap.xml, llms.txt, OpenAPI and related well-known endpoints, plus a missing-page check and an MCP initialize request.

Bot identification and owner controls

Runs use the Neophyte-NUXBot user agent, stop at supported bot checks, and can be recognized by a domain-specific Neophyte-Site-Key when a verified owner configures one.

Use cases

  • Audit a new-user activation path

    Set a target such as reaching the first useful screen and observe whether a new visitor can move from landing page through signup, verification, and setup without unexplained stalls.

  • Review onboarding changes

    Run the same type of task after changing forms, navigation, verification, or first-run screens, then use the recorded journey and friction report to inspect the resulting experience.

  • Assess agent readiness

    Use the report's human-and-agent perspective and the separate resource checks to identify pages or machine-readable endpoints that may make a product harder for AI agents to understand or operate.

  • Share findings with a team

    Share a public run when soliciting feedback, or use private-run and domain-level privacy controls when onboarding results contain work-in-progress product information.

  • Manage testing on an owned domain

    A product owner can verify a domain, restrict who may start runs, and provide a site key so approved Neophyte runs can be distinguished from ordinary automated traffic.

Pros and Cons

Pros

  • Tests onboarding from a genuinely new-user context without requiring a detailed script.
  • Captures both the path taken and concrete friction points, with replay and product-flow views.
  • Handles email verification through a dedicated mailbox, keeping the customer's inbox out of the signup flow.
  • Supports shareable public reports, private runs on paid packs, and domain-owner controls for access and report visibility.
  • Includes checks for common agent-facing site resources alongside the interactive onboarding journey.

Cons

  • Runs can stop at CAPTCHA, Cloudflare challenges, phone verification, payment screens, or paywalls; the agent does not bypass these barriers.
  • The agent can create accounts and make-up profile details remain on the target site, while other side effects such as posts, invitations, or bookings cannot be ruled out.
  • The browser has a 40-minute run limit and uses one shared phone number, so a phone check may prevent a run when that number is already in use.

FAQ

What does a Neophyte run do?

A run signs up as a new user with a dedicated Neophyte email address, reads its own verification email or code, and works toward the task you specify, often the first useful screen. The run and the resulting report are recorded.

How do I use Neophyte?

You name the product and state what the agent should reach and when it should stop. The agent chooses its path from what each page shows rather than following a fixed script, then reports what worked and where it became stuck.

What happens if a bot check blocks a run?

Runs stop at Cloudflare challenges, Turnstile, reCAPTCHA, or hCaptcha rather than attempting to bypass them. The first bot-check block for an account is refunded; later blocked runs use their credit. A verified product owner can configure a site key and access settings to let Neophyte in, although bot-check widgets still need to be left out for keyed requests.

Who can see a run report?

Runs are public by default. Starter or Value credits allow a run to be marked private, and a verified site owner can keep reports for the domain private. Shared reports exclude the account email, password, and made-up profile details.

How are Neophyte plans and credits structured?

Paid plans are one-time credit packs and do not renew automatically. The site lists Free, Starter, Value, and Enterprise options; Enterprise is described as volume pricing with white-glove onboarding, automation setup, invoice payment, and dedicated support.

Quick Facts

Category
Product onboarding testing
Platform
Websites and web products
Primary users
Product teams and site owners
Workflow
AI browser signup, verification, onboarding, and goal completion
Report outputs
Rank, friction report, replay, and product-flow view
Pricing model
Free access plus one-time credit packs; Enterprise volume pricing is available