New tools die in onboarding fog. A crisp first-scan ritual creates the habit.
People looking for how to run first glint scan with client usually already feel revenue soft without a clean story. This guide is written for Teams rolling Glint into delivery — not for generic “ecom tips” blogs.
New tools die in onboarding fog. A crisp first-scan ritual creates the habit. If that matches a client conversation you are having this month, keep reading; if not, use the full guide index.
Teams rolling Glint into delivery
If you own the retainer narrative and the client still asks “why is cash flat when ads look fine?”, you are the buyer for this workflow — not a pure creative shop that never touches Stripe.
Do this week: open Stripe (or your client’s authorized connection), inventory the bullets above, and rank by dollars — not by which ticket yelled loudest.
Client understands top risks and whether they want monitoring only or approve-first fixes next.
Glint surfaces symptoms the data supports — not invented causes. For this topic, the closest detectors are:
Full detector set (when relevant): failed retries · ghosts · expired promos · duplicates · legacy prices · margin bleed. A finding only appears when objects match.
How long should the first review be?
30 minutes is enough if findings are pre-ranked. Do not doom-scroll the entire invoice history live.
Free Scan covers 3 client stores on read-only keys. Pro ($299/mo, 10 stores) and Scale ($499/mo, 30) add approve-first fixes and client reports when you need them — full pricing.
Run a free 3-store scan focused on: Agency playbook: your first Glint scan with a client. Read-only keys. Approve before any fix.
Start free Scan See plans All guidesInformational operator guide. Not legal, tax, or accounting advice. We do not invent client case studies. Industry ranges are attributed to named sources; $274/mo is our instrumented test-store result only.