Your checkout breaks at 2:14 am.
You'll know by 2:16.
NightlyRun writes and runs Playwright test suites for Shopify Plus and SaaS teams protecting checkout, signup, login and payments on every deploy. A human verifies every alert before it reaches you.
Checkout discount broken on iOS Safari, carts > $150.
Trace + screenshot attached. Suggested fix in thread.
The bugs that cost you money look like this.
- Weekly digest08:04
- Order #4192 shipped07:31
- — reset your password —waiting 04:32
Not a red dashboard. A verified alert and a weekly receipt.
Checkout discount broken on iOS Safari, carts over $150. Trace + screenshot attached. Suggested fix in the thread.
Verified by a human · 02:31
- runs: 312
- failures caught: 2
- est. revenue protected: $18,400
Sample report · illustrative until we have a week of your data.
From first call to first verified alert in ten working days.
- Days 1–3
Map your risk flows
Interview + audit to rank the flows where a bug costs real money. Ship a written risk map.
- Days 4–10
Suite built in YOUR repo, wired to CI
Playwright suite committed as a PR into your repo. GitHub Actions on every deploy. Slack channel wired.
- Day 11+
Nightly + on-deploy runs, human-verified alerts
Runs on every push and every night. A human reviews every failure before you're paged. Weekly report.
Selected work
~/projectsE-commerce Playwright Suite
Full Playwright + TypeScript suite covering login, search, cart, checkout, and mobile flows on a demo Shopify-style store. Page Object Model, fixtures, mobile viewports.
GitHub Actions CI Pipeline
Matrix runs across browsers, HTML report published, screenshot + video artifacts on failure, Slack webhook on red builds.
Sample QA Audit Report
Anonymized bug report in the deliverable format: severity ranking, revenue impact estimates, reproduction steps, screenshots, recommended fixes.
Someone who's shipped QA at scale.
5+ years of QA automation across e-commerce and logistics. Built test infrastructure for a major commerce platform, a Fortune 500 logistics company, and a top home goods retailer.
Now applying that same playbook to teams that need it most — small SaaS and Shopify Plus companies who can't afford a full QA department, but can't afford to ship broken either.
Start free. Scale as you ship.
One free bug to prove it. Three ongoing tiers so a two-person startup and a $50M brand aren't paying the same price.
Free Bug Hunt
- 20 min manual QA
- Loom + written summary
- Mobile + desktop
- No call, no signup
Core
- ~15 Playwright tests
- Nightly runs
- GitHub Actions CI
- Slack alerts
- Monthly report
Growth
- ~50 Playwright tests
- On every deploy + nightly
- Human investigation < 2h
- Weekly revenue-protected report
- Maintenance included
Plus
- Unlimited flows
- Mobile device matrix
- On-call SLA
- Quarterly QA roadmap
- Direct line to your engineer
Month-to-month. Cancel anytime. You own every line of test code.
Questions people ask before they book.
Do you write the tests in my repo, or somewhere else?+
Your repo. Everything ships as a pull request against your codebase. You own every line of test code from day one — if you leave, nothing walks with me.
What happens when a test fails at 2am?+
I investigate and hand you a reproduction + suggested fix within 2 hours. I don't hot-fix your production app — the fix is your team's call. You get a verified alert, not a noisy pager.
Which stacks do you cover?+
Shopify (Liquid, Hydrogen, headless), Next.js, Remix, Rails, Django, custom SPAs. If it runs in a browser and you have a URL, I can test it. Native mobile is out of scope.
How long until I see the first test running?+
Ten working days from kickoff to first nightly run against production. First failing test on your calendar, first Slack alert in your channel.
Do I need a staging environment?+
Preferred but not required. Most flows can run against a production URL using seeded test accounts and payment sandboxes I set up as part of onboarding.
Can I cancel?+
Month-to-month after the first month. No annual lock-in unless you take the discount. If you cancel, you keep the entire test suite — it's in your repo.
Your next deploy shouldn't be a coin flip.
Send your URL. I'll find one real bug for free. Then you decide.