Key Takeaways
- Review the commitment length, payment schedule and renewal terms separately. A monthly invoice does not establish a month-to-month agreement.
- Record the deadline and method for giving notice if you plan to let the agreement end when the current term expires. Separately check whether you can end the agreement early and what would still be payable.
- Confirm deliverables, support responsibilities and usable data exports before choosing a provider.
- Choose terms that fit your supported workflow, full cost and ability to change systems. No contract length guarantees delivery, growth or a straightforward exit.
Compare the Commitment with Your Operating Needs
An annual agreement can suit a store with an established workflow and a budget for the full commitment. A shorter term may be useful while requirements remain uncertain. Compare the actual price, obligations, renewal and exit terms rather than treating either label as proof of a good deal.
Put the signed order, service agreement and amendments together. Confirm which terms apply to your locations and services and resolve conflicting promises before signing. Have qualified counsel review rights, liabilities and unclear provisions for your specific agreement.
Six Contract Terms to Review
- Renewal and notice: the renewal date, length of the next term, deadline, required delivery method and recipient for notice.
- Deliverables: the included software, managed work, locations, staff responsibilities and expected handoffs.
- Implementation: the required source data, supported connection, milestones, acceptance criteria and charges if setup is delayed. Record when recurring fees start and when the first store is expected to go live. Ask what happens to those fees if launch slips.
- Data access: which contacts, consent evidence, withdrawals, segments and message records can be exported, in what format, at what cost and by when. Ask for a sample with fictional or redacted records and check that it distinguishes a recorded opt-out from an unknown consent status.
- Support and remedies: coverage hours, response and escalation process, service commitments, exclusions and any agreed remedy. A response commitment is different from a resolution or delivery guarantee.
- Complete costs: subscription, usage, registration, carrier charges, integrations, locations, managed work and any agreed change or exit fees. Identify which amounts can change and how notice works.
Separate Payment Frequency from Contract Length
Write the total commitment beside the invoice schedule. An annual price, monthly payment, annual prepayment and cancellable monthly service describe different arrangements. Ask what remains payable after cancellation and whether unused amounts are refundable under the applicable terms.
The annual versus monthly Texting budget worksheet shows how to compare the first-month budget, the monthly equivalent and the full 12-month cost.
For example, AIQ’s public service agreement describes a one-year initial term when the Service Order does not specify one, annual renewals with at least 30 days’ written non-renewal notice, and monthly subscription-fee due dates unless the Service Order states otherwise. Those are separate provisions, not a description of every customer’s order or Blackleaf’s terms. Review the applicable documents.
- Commitment: record the start, end and renewal dates for the actual order.
- Payment: record what is due upfront and on each billing date.
- Changes: ask when a downgrade, location change or service removal takes effect.
- Exit: obtain the notice process and a written explanation of any remaining charges.
- Portability: Confirm how far in advance to request the export, how it will arrive and the last day you can download it. Leave time to open the file and verify that it contains the agreed fields and opt-out records before account access ends. Use the migration field-mapping worksheet to record where each agreed field appears.
- Evaluation: agree scope, costs and decision criteria before any separately authorized trial. Use the Texting pilot framework to prepare that discussion.
Review Messaging Eligibility Alongside the Agreement
A contract, registration approval or carefully worded message does not establish that a provider supports your business and use case. Confirm the actual route, restrictions, responsibilities and process for holding affected traffic when eligibility or delivery is uncertain.
Blackleaf requires explicit recipient consent and age confirmation before any text, including service and support messages. The intended recipient must verify themselves by selecting the birthday on file in the message flow; never disclose the saved birthday. These company requirements are separate from legal and provider review. Check the age and recipient verification guide when reviewing the proposed workflow.
Review the cannabis SMS compliance guide and TCPA review guide for planning questions. Use carrier-filtering guidance and the deliverability guide to distinguish provider restrictions, message outcomes and troubleshooting responsibilities. None replaces review of the actual agreement or promises successful delivery.
A Contract Review Checklist for Owners
Before signing, attach a written answer and responsible person to each question. Hold the decision when a material answer is missing.
- What is the full commitment, payment schedule and cost for the scope we need?
- What renews, when must notice arrive and how do we document its receipt?
- Which work and connections are included, and who approves setup and campaign activity?
- Can we obtain usable customer records, consent evidence and withdrawals before access ends?
- What happens to fees, data access and service if setup is delayed or we need to leave?
- Who handles restrictions or failures, what must be held, and what remedy is actually agreed?
Download the blank Texting vendor evaluation worksheet (CSV) to record evidence, owners, open questions and proposed costs across six demo scenarios. Make a copy for each candidate and identify your required workflows before comparing proposals.
Use the six vendor demo prompts for the full exercise. This is an uncompleted planning template, not a vendor scorecard or contract approval. Keep customer data and private account details out of shared copies.
What If You Already Signed an Annual Contract
Start with the agreement that governs your account. A current website price or a general contract checklist does not amend an existing order.
- Collect the signed order, amendments, invoices, renewal date and notice requirements.
- Confirm the available export process, fields, timing and access deadline before planning a migration.
- Keep factual records of setup delays, support requests, restrictions and service outcomes.
- Discuss proposed changes in writing and have qualified counsel review uncertain obligations or disputes. Do not assume that stopping use or payment ends the commitment.
FAQ
Should dispensaries sign annual contracts for marketing tech?
An annual agreement may fit an established need and budget. Compare the full commitment, payment timing, renewal, support, data access and exit terms with the actual supported workflow. A shorter term does not automatically offer better value, and annual pricing does not establish cancellation rights.
What contract length is safest for dispensary marketing software?
There is no universally safest length. Consider how certain the requirements are, what the store can commit to, the complete cost and the ability to change or leave under the actual agreement. Review specific rights and liabilities with qualified counsel.
What clauses matter most?
Review the term and renewal, notice method and deadline, fees and changes, implementation responsibilities, support commitments and remedies, data access and export, and obligations after termination. Resolve material gaps in writing before signing.
Next Step
When evaluating Blackleaf’s dispensary texting tools, bring your current systems, required workflow, expected usage and existing commitments. Supported existing-POS Texting can be evaluated without a POS switch. Review current Texting plans and the applicable written quote and terms; confirm payment timing, commitment and cancellation separately.
Review the messaging prerequisites and assign owners for recipient checks, approvals, customer replies and reporting before activation. A purchase or signed software agreement does not replace recipient permission.
Contract-source example reviewed October 29, 2026. Recheck the current source and your applicable documents before making a decision.