Early access
AI agents that sign up as new customers after every release.
Website audit signs up as a new customer after every release: a fresh AI test customer enters each code, opens every email and link and stops before payment. Every break reaches you with its screenshot and a drafted fix.
Release v2.15
Obsession agent for Your company- Sign up14 s
- Login code by SMS8 s
- Welcome email2 min
- First order codeRejectedLAUNCH20
Code not valid
Code LAUNCH20 rejected at checkout
Your 08:00 email promises this code.
Ship anywayHold the 08:00 sendHeld by you06:11Review fix - Stop before payment31 s
Fixes go live after your OK
Example
Pick it, and everything it needs is already set up.
Nothing to build or buy, and nothing to run yourself.
- A labelled AI test customer per run
- A fresh inbox and number
- Phone and desktop browsers
- Starts on every release
- A screenshot of every step
- Every step signed and dated
It runs on your schedule, and keeps the proof.
A pass or a break for every step of every release, with the screenshot and a drafted fix.
Example: release v2.15
Website audit
After every release, sign up as a new customer, enter the code, open every email and try our launch code. Stop before payment.
- Targets
- your-store.example, on phone and desktop
- Journey
- Sign up with a fresh inbox
- Enter the code from the text
- Open every email and link
- Stop before payment
- How often
- After every release
- Report
- Slack alert per release
- Set up
- Agent ID, declared as AI
- Fresh inbox
- Fresh UK number
- Starts on every release
Run log
- v2.15 ships. A fresh test customer starts on a phone, with its own inbox and UK number.Thu 06:02
- Sign up done in 14 seconds.Thu 06:04
- Login code by text in 8 seconds. It works.Thu 06:05
- Welcome email in 2 minutes. Every link opens.Thu 06:07
- LAUNCH20 rejected at checkout. Your 08:00 email promises it.Thu 06:09
Finding
The code your 08:00 launch email promises is turned away at checkout.
You held the 08:00 send at 06:11. The code fix is drafted, and a fresh test customer tries it once it’s live.
Example run. Every step timed, screenshotted and signed. Stopped before payment.
The agents do the legwork. You make the calls.
Connect your releases
A deploy hook, a schedule, or a button you press.
A stranger signs up
A fresh test customer that says it’s AI, with a new inbox and number every run, on phone and desktop.
Every step is timed
Sign up, login code, emails, links, forms and codes, stopping before payment.
Breaks reach you first
A Slack alert with the screenshot and a drafted fix, then a fresh run once the fix ships.
It covers the whole job, and stops where it should.
Sign up and login
Sign up
The form on phone and desktop, how long it takes, and every error it shows.
Login codes
By text or email: how long each takes to arrive, and whether it works.
Password reset
The email arrives and its link opens.
Emails, links and forms
Welcome email
It arrives, how fast, and every link opens the right page.
Every link
In your pages and emails, on phone and desktop. Any that error are flagged.
Forms
A labelled test enquiry through each form, and whether it reaches the inbox or CRM you connect.
Booking links
Each one opens to a live calendar, stopping before a slot is taken.
Basket and checkout
Codes
Every welcome and launch code, tried at checkout.
Checkout
Delivery, totals and every step up to payment, where it stops.
Each release ends in a pass or a break, with the screenshot behind it.
See a real store checkSlack alert
Minutes after a release, with the step, the screenshot and the time.
Ticket
Drafted for your tracker, with the steps to repeat the break.
Release history
Every release’s run, step by step, so you see what changed.
Webhook
A pass or a fail your pipeline reads, so it can hold the release.
Start from the recipe. Change anything.
- Runs
- After every deploy, on a schedule, or when you press run
- Journeys
- Sign up, login, onboarding, forms, basket and checkout
- Devices
- Phone, desktop or both
- Countries
- A number in each country you sell in
- Alerts
- Slack, email or a ticket
The same recipe, different jobs.
Only your own site, or a client’s with their OK. Always stopped before payment.
Obsession’s Website audit sends a fresh AI test customer through your site after every release: it signs up, enters each login code, opens every email and link and stops before payment, and every break reaches you with a screenshot.
Website audit gives you up to 2 hours a week back, if you spend 2 hours a week testing releases by hand.
Website audit checks what a new customer gets: the text that arrives, the email, the link and the code, on its own inbox and number. Your tests check the code.
No. Website audit uses your site like a customer. A deploy hook starts each run, or it runs on a schedule.
No. Website audit goes through checkout and stops before payment.
No. Every Website audit test customer is labelled, so you can filter them out of your lists and reports.
Website audit stops, and the run names the step it couldn’t test.
Yes, with each client’s OK: Website audit gives every client its own run, every morning or after each of their releases.
Catch the break before your 08:00 email goes.
Join the waitlist. Website audit comes ready to run on your next release.