How it works

From demo to live in 4-6 weeks.

From signed scope to live on a Monday 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

Dutchie · Treez · Flowhub · Cova · BLAZE

Active

Opening a new dispensary

First POS · pre-grand-opening setup

Switching timeline

Step 01 / 06

30 min

Demo on your data

We walk a real workday on a sandbox seeded with the shape of your inventory and customer list. No deck, no slides — the same surfaces a budtender sees on shift.

  • Live register transaction with vertical-ID gate
  • Inventory dashboard with your category structure
  • Manager write-up flow drafted against WA labor rubric
  • Form 941 generated from the same data that took the cash
  • 30 minutes, end with a fixed-scope quote — no hourly games

What you do

Send us a CSV export of products + customers. Show up to a 30-minute call.

What we do

Pre-load the demo with your data shape. Walk three real surfaces. Quote your cutover before we hang up.

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.

  • 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

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.

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.

  • 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

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 Sunday is a swap, not a project.

Step 04 / 06

1 weekend

Cutover weekend

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

  • Saturday close on old system — your last till count there
  • Sunday: final delta sync (transactions Sat → Sun) + freeze
  • Sunday night: hardware swap, terminal reboot, smoke test
  • Monday open: CannAgent live. Doug on call — phone, Slack, screen-share within the hour
  • Three days of remote standing-by during opening week

What you do

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

What we do

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

Step 05 / 06

2 weeks

White-glove first two weeks

Doug 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.

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

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.

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.

  • 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
  • 90-day satisfaction window: refund the setup fee, keep your data

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.

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. Sunday is the swap. Monday 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.

What if it doesn’t work out?

90-day satisfaction window. If you’re not running better than you were on the old system after 90 days, we refund the setup fee and you keep your data exports. We’d rather not work with someone unhappy.

Who’s on the other end if something breaks?

Doug, named human. 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.

Case studies

2 operator-run

our own stores.

See it on your data. 30 minutes.

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

Request a demo →Compare against every POS