Service
Custom Software
Off-the-shelf software covers the easy 80%. The remaining 20% — the workflows that actually differentiate your operation — is where custom software pays off. In cannabis, that 20% is everything: a METRC integration that does not break when the API rate-limits you at end-of-month, a cultivation dashboard that correlates environmental sensor data with plant tags, or a wholesale ordering portal that knows the difference between California and Colorado product categories. We design, build, and maintain applications that fit your business instead of forcing your business to fit the software.
We have built delivery driver apps that handle real-time route optimization and compliance checks, cultivation dashboards that integrate environmental sensors with METRC plant tags, and wholesale ordering portals that connect brands with retailers across state lines. Every project starts with a detailed workflow analysis and ends with documented, tested code that your team can operate and extend. We do not hand over a black box — we hand over a system your engineers can read, debug, and improve.
When this service is right
Custom software is the right choice when your existing tools leave critical gaps. Common scenarios include operators managing multiple locations with inconsistent data, brands building direct-to-consumer or wholesale platforms, and cultivators tracking environmental and compliance data in spreadsheets. If your team spends more time wrangling software than using it, or if you have a workflow that no off-the-shelf product supports, we should talk.
When it is not right
If your problem can be solved with a $50-per-month SaaS tool, custom software is overkill. Teams without an internal champion to adopt and maintain a new system often struggle with adoption, no matter how well-built the tool is. And if what you need is fundamentally a marketing website or SEO content strategy, our Web & Search service is the better fit. We scope honestly and will tell you when custom development is not the right investment.
What you get
Our custom software engagements are comprehensive. We handle architecture, development, testing, deployment, and handoff documentation. Here is what is typically included.
- Internal dashboards and admin tools for cultivation batch tracking and compliance calendars
- Native and progressive web apps — driver apps with METRC manifest sync, customer pre-order apps
- Third-party API integrations — METRC REST API, BioTrack sync, Leaf Data Systems, payment processors
- Workflow automation and data pipelines — ETL from METRC to BI tools, automated state-reporting exports
- Legacy system modernization — migrating from spreadsheet-based compliance to API-driven systems
- White-label and B2B platform builds — brand-to-retailer ordering portals with state-aware inventory
How we work in your state
Cannabis operators face three major seed-to-sale platforms in the United States, each with its own API behavior, data model, and compliance rules. We have integrated with all of them and understand the abstraction layers multi-state operators need to stay sane.
METRC — CA, CO, MA, NV, and others
METRC provides a REST API for per-plant and per-package tracking. Rate limits are strict, webhook delivery is not guaranteed, and data schemas vary slightly by state. We build resilient sync pipelines with local queuing, exponential backoff, and full audit logging so your operation never loses data when METRC throttles or experiences downtime.
BioTrack — FL, AR, NM, and others
BioTrack uses a different data model from METRC, with bidirectional sync APIs that require careful mapping of product categories, strain names, and package conversions. We have built normalization layers that translate BioTrack entities into your internal schema without losing the granularity regulators require.
Leaf Data Systems — Washington
Washington State runs its own seed-to-sale system, Leaf Data, with a unique API schema and strict manifest and transportation rules. Integrations here require state-specific knowledge that generic cannabis software rarely provides. We handle the full integration so your Washington locations report accurately without manual data entry.
Multi-state operators face the hardest challenge: different schemas per state, different compliance calendars, and different product definitions. We build abstraction layers that let your corporate team see unified dashboards while each location writes data in the format its state regulator expects.
Representative tech stack
We choose technologies based on your existing infrastructure, team skills, and long-term maintenance requirements. Here are the tools we use most often.
Integration expertise
Cannabis operators rely on a patchwork of systems: METRC for state compliance, payment processors for cashless transactions, delivery platforms for logistics, and accounting software for bookkeeping. We have integrated with all of the above, and we understand the edge cases that break naive integrations — rate limits, API versioning, data format changes, and authentication refreshes.
We have delivered custom systems for operators at every scale — from single-location dispensaries needing a specialized inventory tool to multi-state platforms serving thousands of daily users. Every project follows our four-phase process with milestone demos, fixed-scope proposals, and staging environments where you test before anything goes live. Our clients stay with us because our systems work on day one and scale without rewriting.
Pricing posture
Fixed-price projects for well-scoped builds. Monthly retainers for ongoing development, maintenance, and feature iteration. We do not bill by the hour.
Unclear whether your current integrations are built to last? Get a free stack audit →
Related services
Custom software often connects to existing POS infrastructure or feeds data into analytics dashboards. If you are building something that touches retail transactions or compliance reporting, our POS and data expertise will accelerate the project.
Common questions
When is custom software the right choice versus an off-the-shelf tool?
Custom software pays off when your existing tools leave critical gaps — multi-location data inconsistency, compliance workflows that no standard product supports, or integrations that break every time an API changes. If your team spends more time wrangling software than using it, we should talk.
What types of integrations do you build?
We have integrated with METRC, payment processors, delivery platforms, accounting software, and ERP systems. We understand the edge cases that break naive integrations — rate limits, API versioning, data format changes, and authentication refreshes.
Do you build mobile apps?
Yes. We build native and progressive web apps for iOS and Android. Recent projects include delivery driver apps with real-time route optimization and compliance checks, and cultivation dashboards that integrate environmental sensors with METRC plant tags.
Will we own the code?
Yes. Unless otherwise agreed in a written statement of work, custom software developed for your business is owned by you upon final payment. We use open-source, portable infrastructure so you are never locked into a proprietary platform.
How are custom software projects scoped and billed?
Fixed-price for well-scoped builds, with milestones at kickoff (40%), midpoint demo (30%), and final delivery (30%). Monthly retainers are available for ongoing development, maintenance, and feature iteration. We do not bill by the hour.
How do you handle METRC API rate limits and downtime?
We implement request batching, exponential backoff, and local transaction queues so your operation keeps running even when METRC is slow or unavailable. Every sync event is logged with timestamps and retry status for audit purposes.
Can you integrate with our existing POS or do we have to replace it?
We integrate with existing systems whenever possible. Many of our engagements start with middleware that connects your current POS to METRC, accounting software, or delivery platforms. If your POS is the bottleneck, we will tell you directly and propose the least-disruptive path forward.
What compliance risks should we consider when building custom software?
The biggest risk is building something that works in development but fails under real state-audit scrutiny. We design every system with immutable audit logs, data lineage, and error handling that regulators expect to see. We also avoid claiming certifications we do not hold — no SOC 2, HIPAA, or PCI-DSS claims unless independently verified.