About CannAgent

Built by operators. Run on our own registers.

Active in Washington cannabis retail since 2010. Daily ops, every register, the whole operator’s day. CannAgent is the system we run our own shops on — sold to operators who’d rather own the system than rent it.

Origin

Built because nothing else fit.

We run licensed Washington cannabis dispensaries — active in WA retail since 2010, pre–I-502 on one of our storefronts. Profitable, running CannAgent in production today. For years the shops ran on Dutchie, then on a stitch of Dutchie + bolt-on POS + a third-party payroll vendor + a spreadsheet for vendor management. Each surface broke in a different specific place.

Dutchie was a coupon site that bought a register. Treez and Flowhub treat cannabis as a vertical they bolted on. None of them know what WAC 314-55-079 means until you ask three tickets deep. The back office — payroll, hiring, write-ups, performance reviews — lived in a separate tool the bookkeeper reconciled by hand. Vendor ordering ran off PDFs. Compliance was a poster on the wall, not code at the register.

In 2025 we started building the replacement ourselves — register, inventory, compliance, payroll, vendor portal, all on the same Postgres each store already runs. We ran our own stores on it before letting another operator touch it. The platform was productized under Sureel Ventures LLC and is now offered to other dispensary operators who’d rather run their own system than file another support ticket. CannAgent is what came out the other side.

The Team

We run the shops. We build the software.

WE

Operator team

Active WA cannabis operator since 2010

We run licensed Washington cannabis dispensaries and built CannAgent on the system that runs our own registers daily. Dutchie, Treez, and Flowhub each broke in a different specific place; stitching three vendors together stopped being a strategy. The platform you’re looking at is the one we run our shops on — same code, same compliance gates, same morning glance.

Why we built it

Three things Dutchie structurally can’t do.

Operator-tested cash management

Cannabis retail clears in cash, and Dutchie was built around the credit-card workflow it spent years pretending it could deliver. CannAgent is cash-first: manager-PIN gates, till-variance SMS over $5, safe-drops and payouts as first-class workflows, and a closer who can finish a Friday night without texting the owner.

Native WSLCB compliance

WAC 314-55 isn’t a config switch — it’s the rail the workflow runs on. Vertical-ID stops the cart at the register (314-55-079 enforcement, not a poster). Industry discount has a 90-day re-verify in code (314-55-095). Waste log carries second-witness sign-off as a workflow, not a PDF. Dutchie tells you the rules; we run them.

Self-learning ordering

Reorder isn’t a vendor PDF you re-key. CannAgent drafts purchase orders against velocity, vendor reliability, and observed fill-rate — the math runs nightly off your actual transaction history, not a static days-of-supply formula. Override with one click. The vendor portal closes the loop on the other side.

See the full comparison

Verify our story

Every claim above is checkable on a public surface. Don’t take our word for it.

Live status

5-min probes

Per-target uptime visible.

Case studies

2 operator-run

our own stores.

Common questions

What operators ask 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.
Ready when you are

See if it fits your shop.

30-minute demo. 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 the back office.

Request a demo
Schedule a demo
30 minutes · register, write-up, Form 941
Request a demo →