Powered by StealthAgents
Founder Operations
Cannabis dispensary founders often reach a point where they are executing tasks that should belong to someone else. They are approving every vendor invoice, running their own METRC reconciliation, handling HR paperwork, and fielding compliance questions that a trained staff member could answer independently.
This is not a discipline problem. It is a structural problem: the work has outgrown the systems, and the systems have not been rebuilt to account for the growth.
A delegation framework solves this by defining which work the founder must own, which work should be delegated with visibility, and which work should be fully owned by someone else with only exception reporting going up.
The most practical delegation framework for cannabis operators divides tasks into three tiers based on reversibility and consequence.
Tier 1: Founder-only decisions. These are decisions with irreversible consequences or strategic implications that the founder must personally own. New license applications, equity transactions, major vendor relationships, and legal responses to regulatory actions belong here. These cannot be delegated because the authority and accountability cannot be separated.
Tier 2: Delegated with visibility. These are recurring decisions that a trained staff member or manager can own, with the founder receiving summary information rather than being involved in every instance. Hiring decisions for non-senior roles, operational spend within an approved budget, and scheduling and capacity planning belong here. The founder sees the outcomes on a cadence without being in the decision loop.
Tier 3: Fully delegated with exception reporting. These are operational tasks that run on a defined procedure, can be executed without judgment from the founder, and should only surface to the founder when something falls outside the expected range. METRC daily reconciliation, POS reporting, COA management, vendor invoice processing, and license renewal tracking belong here. The founder sees exceptions, not updates.
The most reliable method is a time audit. For two weeks, log every task you complete with an estimated time in minutes. At the end of two weeks, go through the log and mark each task with the tier it belongs to.
Most founders find that 30 to 50 percent of their logged time is Tier 3 work, executed personally because no one else owns it. This is the delegation opportunity.
For each Tier 3 task you are currently doing, ask: what does "done correctly" look like? What information would I need to verify it was done without seeing every step? Those two questions define the procedure and the exception criteria that let someone else own the task with you receiving only the signal that matters.
Delegation without visibility is abdication. The goal is not to stop being informed; it is to receive the right information at the right cadence without being in the execution chain.
For Tier 2 decisions, build a weekly summary report. One page, delivered every Monday morning, that shows the key decisions made last week, the outcomes, and anything that requires your input in the coming week. You review it, reply with any input, and move on.
For Tier 3 tasks, define the exception criteria and build a brief daily or weekly exception report. For METRC reconciliation, the exception is a discrepancy that could not be resolved through the standard correction process. For license tracking, the exception is a renewal date entering the 30-day window with a documentation gap. You receive nothing when operations are normal and a brief flag when they are not.
Start with tasks that have clear procedures and can be documented in a way that allows someone else to execute them correctly. METRC daily reconciliation, POS end-of-day reporting, COA management, and vendor invoice processing are all procedural tasks with well-defined correct execution. These are the easiest to hand off and the ones that will return the most founder time.
Avoid delegating first to the tasks that require judgment or relationship history. Vendor negotiations, employee performance conversations, and strategic planning discussions are not the right starting point. Get the procedural delegation working first, build trust in the reporting layer, and then expand the delegation scope as your confidence in the system grows.
Delegation fails when the founder takes tasks back at the first sign of friction. A staff member or VA who makes an error on their first week of owning METRC reconciliation is not a reason to retake the task. It is a reason to improve the procedure documentation and training.
Define what a delegation failure actually looks like: repeated errors after the procedure is fully understood, or an exception that was not escalated when it should have been. Single errors during a ramp-up period are not failures. They are the expected output of someone learning a new procedure.
Build a 30-day and 90-day review into every delegation handoff. At 30 days, assess whether the procedure documentation is complete and whether the person owning the task has the resources they need. At 90 days, assess whether the delegation is producing the outcomes you intended and whether the exception reporting is calibrated correctly.
For founders looking to build the operations layer that makes delegation sustainable, our founder admin and EA service covers the specific administrative coordination, calendar management, and reporting infrastructure that supports the CEO's focus on Tier 1 decisions. The National Cannabis Industry Association publishes operator resources including management frameworks used by established cannabis businesses. For a view of what cannabis VAs can take on across the full operations picture, the cannabis VA duties guide covers the specific task categories in detail.
Q: How do I maintain compliance visibility when I am not doing the compliance work myself?
A: Define the compliance metrics that matter to you and build a weekly compliance dashboard that puts those numbers in front of you without requiring you to pull them. METRC error count for the week, open discrepancies by age, days until the next license renewal deadline, and COA expiration alerts are all reportable numbers that can be delivered on a schedule. You see the compliance health of your operation without being in the daily workflow.
Q: What if my dispensary is too small to justify hiring staff for these tasks?
A: The threshold for delegation is not headcount, it is time cost. If you are spending six hours per week on METRC reconciliation and that work could be owned by a part-time remote staff member for less than the value of six hours of your attention, the economics of delegation are positive regardless of your dispensary's size.
Q: How do I know if a task has been delegated successfully?
A: A task has been delegated successfully when the exception reporting is the only contact you have with it, and the exception reports reflect a well-running process rather than chronic problems. If you are receiving exception reports every week for the same issue, the delegation is not working: either the procedure needs improvement or the person executing it needs additional training.
Q: Is it safe to delegate compliance tasks to a remote employee?
A: Compliance-adjacent tasks that are procedural, such as METRC reconciliation, COA management, and license calendar tracking, are well-suited to remote execution with appropriate access controls. Tasks that require judgment calls about compliance incidents or regulatory communications should escalate to you or a senior compliance lead. Build the escalation criteria into the procedure documentation rather than leaving it to the person executing to decide when to surface an issue.
Q: What is the most common reason delegation fails for dispensary operators?
A: The most common reason is that the founder takes tasks back informally without acknowledging it. A question from a staff member that gets answered with a decision rather than a referral to the procedure is the founder doing the task again. Build the habit of responding to task questions with the procedure, not with the answer, even when giving the answer is faster in the moment.
