Request a demo

See it on your data. 30 minutes. No commitment.

We walk the same three surfaces a working day touches: a register transaction with a vertical-ID gate, a manager write-up against the WA labor rubric, and a quarterly Form 941 from your back office. If it lands, we scope your cutover. If it doesn’t, we tell you what would fit better.

Demo request

Tell us about your shop.

~3 min

The more specific the better.

Optional · helps us scope better▾
↳ Demo arrives by email in <60 sec·↳ Login credentials inline on the next page·↳ No call required
What happens after you submit

Three steps. Most of it’s automated.

01

You fill the form

Seven fields, three minutes. The more specific you are about what's broken, the better the scope we send back.

02

We email the demo + scope

Direct login URL, four persona shortcuts (Doug / Kat / Austin / Charity), shared password, and a personalized scope summary in under 60 seconds.

03

30-min call with Doug

If the demo lands, we walk your cutover plan and quote a fixed scope. If it doesn't, we tell you what would fit better.

No NDA. No qualifying call. No PDF brochure. The demo is the same code two stores ran a transaction on this morning.

Before you submit

Questions we hear first.

How long does migration from Dutchie take?
Two to four weeks for a single location, depending on how clean your Dutchie data is. The cutover itself happens overnight — last close on the old system Sunday evening, first open on CannAgent Monday morning. The ramp before that is data audit, hardware swap, and three days of on-floor support during the first week. Multi-location chains stage cutovers one store at a time; we don’t flip ten registers at once.
Do we lose any historical data when we migrate?
No. We pull transactions, customers, loyalty points, vendor records, and inventory snapshots out of your current system before the cutover and load them into your new Postgres database. You see your last twelve months of revenue, your loyalty members keep their points, and your vendor history carries over. Anything we can’t migrate cleanly we tell you about up front — we don’t silently drop rows.
Is there a per-staff or per-transaction fee?
No. Pricing is per location, billed monthly. Add a register, add a budtender, add a manager — same line on the bill. Cannabis cash-margin is tight enough without a vendor metering you on every staff add. Card-processing fees, if you turn them on, pass through at processor cost; we don’t take a per-swipe markup.
Who owns our customer and transaction data?
You do. Always. Each location runs on its own Postgres database, exportable any time in standard SQL. No vendor-database lock-in. On the Enterprise tier, source-code escrow is available so the platform itself keeps running on your terms if anything ever happens to us. Your customer list is not aggregated, not resold, and not used to train any model — it sits in your database.
What’s the AI model and is it making decisions for us?
Claude (Anthropic) is the primary model behind the assistive features — write-up drafting, scope generation, the reorder-queue explainer. The AI proposes, the manager gates the action — see /admin/manager-writeups for AI-suggested proportionate-response options against WA labor + WSLCB rules, then a human acknowledges and ships. We don’t auto-fire anyone, auto-purchase from a vendor, or auto-run payroll. The model is assistive, not autonomous.
What if we hate it after 90 days?
We refund the setup fee and you keep your data exports. We’d rather not work with someone unhappy. The full cross-tier guarantees — WSLCB compliance built in, no migration fees, named human support, free training, your data stays yours — live at /pricing.
See all questions