Request a demo

See the real product. 30 minutes. No commitment.

No qualifying call and no forms to chase. We verify your license against the state registry, then a real operator emails you back — usually within one business day — with a time and a scope summary. The walkthrough is on the working product, run by an operator who uses it on their own floor. Only if it lands do we scope your cutover.

Prefer email? Email us directly — no form.

Demo request

Tell us about your shop.

~3 min

6-digit for WA · 9-digit for OR · alphanumeric for CA · pasted value preserved as-is. We use it to pull the right compliance frame for your state — WAC 314-55 for WA, OAR for OR, etc. — so the demo workspace mirrors your actual ruleset.

Don’t know yours? Look it up on lcb.wa.gov →
05 · Locations

Checkout lanes / POS terminals. Helps us size your hardware + license at quote time.

07 · Your current stack

Check all that apply — what you run in each lane today. Pick “Other” (or add a row below) for anything not listed.

POS / register

Rewards / loyaltyoptional

Online menuoptional

Purchasingoptional

Anything else in your stack?

The more specific the better.

Optional · helps us scope better▾

When you’d ideally cut over. We back-calculate the action items + reminders off this date. Push it later if you need to.

Optional. If someone sent you here, their code credits them — links lose it, the code doesn’t.

↳ Demo arrives by email in <60 sec·↳ One-click login link — no password to set·↳ No call required
What happens after you submit

Three steps. One human check.

01

You fill the form

A short form, a few minutes. The more specific you are about what's broken, the better the scope we send back.

02

We check your license, then email you a time and a scope

We match your license number against the state registry we already ingest, so you are not answering qualifying questions. Then a real operator emails you back with a time and a personalized scope summary — usually within one business day. There is no self-serve sandbox to log into right now; the walkthrough is live, on the working product, with an operator who runs it on their own floor.

03

30-minute walkthrough of the working product

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. One license check, then the demo — the real product on real sample data, the same build, not a slideshow or a sales deck.

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?
You keep your data exports and walk — and since setup and onboarding are free, there’s no fee sunk on the way in. 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.