How it works

From demo to live in about four weeks, typically.

From signed scope to live on a Sunday open. Whether you’re switching from another POS or opening your first store, every step is named, every duration is honest, and every workload is split.

Pick your path

Switching from another POS

Whatever register you run today

Active

Opening a new dispensary

First POS · pre-grand-opening setup

Switching timeline

Step 01 / 06

Self-serve

Your own demo workspace

We check your license against the state registry, then email a one-click login to a workspace set up as a sample store. Walk it on your own: no deck, no slides, the same surfaces a budtender sees on shift.

What you do

Tell us your current POS, how many locations, and who files your CCRS. Walk the workspace on your own time.

What we do

Verify your license, send the login, and quote your cutover on a 30-minute call when you want one.

What happens in this step +
  • Live register transaction with vertical-ID gate
  • Inventory dashboard and a reorder draft
  • Manager write-up flow drafted against WA labor rubric
  • Month-close trial balance from the same data that took the cash
  • A 30-minute call at the end, only if it lands, with a fixed-scope quote — no hourly games

Step 02 / 06

1 week

Discovery

We map your current operation: vendor list, schedule, register hardware, loyalty rules, custom report cadence. The output is a Cutover Doc you sign before we lift a finger on your DB.

What you do

Give us read-only access to your current system or send full exports. Walk a closer through their day.

What we do

Map every field. Document every workflow. Surface every edge case in writing.

What happens in this step +
  • Product + vendor master + customer + loyalty CSV exports
  • Hardware audit — printers, scanners, customer displays, tablets
  • Compliance posture review against WAC 314-55 family
  • Cutover Doc: per-table mapping, every edge case named
  • Decision: do we keep your existing METRC link or re-link

Step 03 / 06

2 weeks

Pre-flight

We provision your store on its own Postgres, port the Cutover-Doc data in stages, and run mirrored transactions against your current register so we catch field drift before customers do.

What you do

Run dry-runs with three of your closers. Flag anything that doesn’t match how your floor actually moves.

What we do

Port every row. Reconcile every field. Stand up your hardware so cutover night is a swap, not a project.

What happens in this step +
  • Per-store Neon Postgres provisioned, your DB on day one
  • Customers + loyalty tiers + vendors imported with reconciliation report
  • Hardware test: printer, scanner, customer display, kiosk
  • Mirrored test transactions against your live register for 1 week
  • Three on-shift staff dry-runs in the demo deploy before cutover

Step 04 / 06

1 weekend

Cutover weekend

Your last close on the old system is Saturday night. We switch overnight. Sunday morning the registers boot to CannAgent. The register, customer display, scanner, and printer are physically the same; the brain underneath changed.

What you do

Run Saturday close as normal. Trust the playbook on swap night. Open Sunday, same opener you always have.

What we do

Run the swap, the smoke test, and the remote support. If anything breaks Sunday morning, we’re on the line within the hour.

What happens in this step +
  • Saturday close on old system — your last till count there
  • Saturday night after close: final delta sync + freeze
  • Overnight into Sunday: hardware swap, terminal reboot, smoke test
  • Sunday open: CannAgent live. Our team on call — phone, Slack, screen-share within the hour
  • Three days of remote standing-by during opening week

Step 05 / 06

2 weeks

White-glove first two weeks

Our team on standby every day. Daily check-ins, same-day fixes for surprises, training your manager into the in-app help so the system supports itself by week three.

What you do

Use the system. Tell us what feels off. Send your manager through the training tracks before they get asked.

What we do

Stay close. Fix what surfaces. Train your team into ownership instead of dependence.

What happens in this step +
  • Daily standup call (15 min) for the first 5 business days
  • Slack / SMS / email access to our team, same-day responses
  • Manager training: 50+ modules across 8 role tracks
  • Weekly review of the audit log + variance reports
  • Hand-over to the in-app help once your manager owns it

Step 06 / 06

Week 3+

Steady state

You own the system. We’re on call as needed — same-day for outages, same-week for feature requests, monthly for the operator-feedback session that drives the roadmap.

What you do

Run your shop. Show up to the monthly operator call. Tell us when something’s off.

What we do

Keep the system green. Ship the requests that show up twice. Stay the operator-built tool you signed up for.

What happens in this step +
  • Monthly operator-feedback call — your requests shape the next ship
  • On-call SLA: same-business-day for register-down, 24h for everything else
  • In-app help (150+ panels) covers most manager questions
  • Quarterly compliance review against WAC 314-55 updates

Common questions

Specific to the switch. The full FAQ is at /faq.

Will the register be down during cutover?

No. Saturday close runs on your old system. We switch overnight. Sunday opens on CannAgent. Same hardware, new brain. The cutover playbook keeps the register down for under an hour, overnight, when the store is closed.

Do we lose our customer + loyalty data?

No. Your customer list, loyalty tiers, visit history, and basket size all port over during Pre-flight. We send a reconciliation report — every row that came across, every row that didn’t (with the reason). You sign off before cutover.

What about hardware? Do we have to buy new printers and scanners?

Almost never. CannAgent runs on iPad-class tablets, USB or Bluetooth scanners, ESC/POS printers, and 1-2 customer displays per register. We audit during Discovery and tell you in writing what works as-is and what (if anything) needs replacing.

What happens to our existing METRC / state-tracking link?

We can either keep your existing license under your account or re-link to ours during cutover. The choice depends on your state and your current contract. We document the path in the Cutover Doc before we touch the link.

Who owns our data?

You do. Per-location Postgres, exportable any time in standard SQL. No hidden fees on data export, no migration penalty if you ever leave.

Who’s on the other end if something breaks?

A named person on our team. Not a ticket queue. Same-day for register-down, 24h for everything else. Your manager will have a phone number, not just an email address.

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.

Trust posture

Sub-processors, retention

Named vendors, data ownership, security status.

See it in 30 minutes.

End the call with a fixed-scope quote and a cutover date that fits your store, not ours.

Request a demo →See the full feature set