About CannAgent

Built for cannabis retail. The whole shop, one system.

Built for the cannabis operator’s whole day — every register, the back office, the compliance gates, on one login. For operators who’d rather own the system than rent it.

Origin

Built because nothing else fit.

Cannabis retail is its own animal — cash-first, a state rulebook at every step, §280E hanging over the books. For years the tooling didn’t reflect that: a general-purpose register, then a stitch of that + a bolt-on POS + a third-party payroll vendor + a spreadsheet for vendor management. Each surface broke in a different specific place.

A cannabis-native build starts from the state’s ID and traceability rules and keeps them at the register, not three tickets deep in a help queue. The back office — payroll, hiring, write-ups, performance reviews — belongs on the same system the bookkeeper already works in, not a separate tool reconciled by hand. Vendor ordering runs off live velocity, not PDFs. Compliance is code at the register, not a poster on the wall.

The team building CannAgent runs licensed cannabis retail itself, and the features that ship are the ones that broke on a real register first. The numbers we publish are measured on our own floors — first-party, disclosed as ours, with the licenses and the figures laid out at /case-studies.

CannAgent is the replacement — register, inventory, compliance, payroll, vendor portal, all on one Postgres database instead of five vendors you reconcile by hand. It’s built ground-up for cannabis retail — state track-and-trace, §280E, cash discipline — not a general POS with cannabis bolted on. The platform is productized under Sureel Ventures LLC and offered to dispensary operators who’d rather own their system than file another support ticket.

The Team

The team behind CannAgent.

WE

The CannAgent team

Built for cannabis retail

CannAgent is built for cannabis retail from the ground up — WAC 314-55 in the cart, cash-first at the till, §280E in the books. Cannabis rules are the foundation, not a module added later. CannAgent is built ground-up for the floor: register, compliance, payroll, and vendor management on one Postgres database, not five you reconcile by hand.

Why we built it

Three things a cannabis-native build does that a bolted-on POS can’t.

Cash-first by design

Cannabis retail clears in cash, and most dispensary software was built around a credit-card workflow the industry spent years waiting on. CannAgent is cash-first: manager-PIN gates, a till-variance ladder that escalates at $5, $10 and $50, safe-drops and payouts as first-class workflows, and a closer who can finish a Friday night without texting the owner.

Native cannabis compliance

The state rulebook isn’t a config switch — it’s the rail the workflow runs on. Vertical-ID stops the cart at the register, not on a poster. Trade-sample units are counted against the per-employee quarterly cap in the cart, not on a clipboard. The waste log will not close without a second signature — that one is our workflow, not a PDF, and no section requires it. In Washington the age floor is WAC 314-55-079(1) and the trade-sample cap is -096(1)(j)(vi). Most systems tell 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 feature set
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.

Public changelog

Every ship, dated

What changed, when, in the open.

Trust posture

Sub-processors, retention

Named vendors, data ownership, security status.

Operator outcomes

Our own floors

Measured on licensed cannabis retail we operate ourselves — disclosed as ours, with the licenses and the figures laid out in full.

Common questions

What operators ask first.

How long does a migration take?
Two to four weeks for a single location, depending on how clean the data in your current system 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. We have run this off Dutchie on our own floors, and the shape is the same coming from POSaBIT, Treez, Flowhub, Cova, BLAZE, Greenbits or BioTrack — what changes is how much of your history the outgoing vendor lets you export, which is the first thing we check.
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 — 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
30 minutes on the working product. An operator replies.
Book it →