Public receipts

What we publish. What we don’t track.

The audience for muntin.digital has been told “trust us” by every SaaS in the restaurant space and been burned. This page is the structural counter: a public diary of a small studio. Updated weekly. Last updated 2026‑05‑01.

The library at a glance

  • 149glossary terms
  • 12free tools live
  • 43articles published
  • 3case studies
  • 2locales (EN, ES)
  • 7library topics

How we measure ourselves

Seven north-star KPIs, reviewed weekly. The list is short on purpose — if a number stops moving, that’s the conversation, not a dashboard with thirty more.

  1. Organic + AI-search sessions per week
  2. Tool engagement rate (first results ÷ tool pageviews)
  3. Workshop save rate
  4. Library depth ratio (article scrolls + checklist completions + audio listens)
  5. AI-search arrivals share (a watch metric, not a target)
  6. Window thread starts per week
  7. Lead-to-call rate (rolling 30 days)

What we track

A controlled vocabulary of about 60 events: page arrivals, AI-search landings, returning visits, article scroll depth, audio listens, glossary popovers, tool first-input, tool first-result, tool save intent, Workshop saves, newsletter signups, Window threads, form submissions, and 404s. Properties are bounded enums — no raw URLs, no path strings, no email addresses, no timestamps with second resolution.

The full event registry lives at /system/; the privacy-side disclosure lives at /privacy.html.

What we don’t track

  • No advertising cookies, no remarketing pixels, no cross-site identifiers.
  • No session replay, no heatmaps, no mouse-movement recording.
  • No keystroke logging on any tool input. Verifiable in DevTools → Network tab.
  • No email signups gated behind audit results.
  • No third-party JavaScript widgets that set cookies.
  • No fingerprinting libraries. (Plausible is cookieless and fingerprint-free.)

These are public commitments. If the policy ever changes, this page changes first — and the old version stays in git history.

Other receipts

Public commitments, in writing

The launch-plan refresh added a set of named commitments that are now part of the studio’s spec. Each one is a number or an absence operators can hold the studio to:

  • Two builds at a time, no exceptions. If the calendar can’t carry your project, you hear about it on day one with a date you’d be next, or a referral. /never/ #5.
  • Reply within 4 hours, Mon–Fri. Posted on every page, measured in Plausible.
  • Three site tiers, posted in writing. $2,500 Essentials · $5–9k Full Service · $8–15k+ Group. See pricing.
  • Three productized offers, bookable without a sales call. $499 audit · $1,500 menu drop-in · $99/mo Care Plan Light. Audit · drop-in · Care Plan.
  • Library content licensed CC BY-NC 4.0. Quote, summarize, translate, AI-cite freely. Tools / brand / codebase explicitly not licensed for redistribution. /terms.html §4.
  • Five things this studio will never do. No lock-in, no data resale, no hidden pricing, no remarketing pixel on the library, no work outside the quoted window. /never/.
  • Three functional cookies, no banner. md_locale, lang_hint_dismissed, md_session. Plausible is cookieless. /cookies.html.
  • Maryland courts, no mandatory arbitration. Disputes go to a real courtroom in Maryland. /terms.html §10.
  • WCAG 2.2 AA target, 0 critical violations. Audited with axe-core + pa11y-ci. /accessibility.html.
  • 72-hour breach notification, 45-day Maryland PIPA filing window. If your data is ever exposed in an incident, you hear within 72 hours. /privacy.html.

What shipped, in numbers

The May 2026 launch-plan refresh shipped across ten phases. The visible-side totals:

Found a number that looks wrong? Email Don. Numbers are recomputed from data/site-counts.json and Plausible aggregates — if any are stale, that’s a bug.