Developer Project Brief

Developer Project Brief
Claude AI Data Integration - Rodeo Cannabis Co
1625 Silas Deane Hwy, Rocky Hill, CT | [email protected]
Issued: March 2026

Project Overview
Rodeo Cannabis Co is a vertically integrated cannabis operator based in Connecticut. We
cultivate outdoor cannabis, manufacture and distribute wholesale products to dispensaries
statewide, and are opening our first two retail locations (Rocky Hill and Groton, CT).
We use seven core software platforms to manage our business. We are seeking a developer to
build a unified data integration layer that connects all seven platforms to Claude AI (Anthropic),
enabling our leadership team to query live business data, surface insights, and make faster
decisions without manually pulling reports.

Platforms to Integrate
The following seven platforms must be connected. The developer is responsible for researching
each platform's API documentation and obtaining developer access credentials with our
assistance.

Platform Purpose Integration Notes
Hoodie
Analytics

In-store retail sales data across the
Connecticut market

Cannabis-specific analytics; confirm
API or data export availability

LeafTrade Wholesale order management and B2B

sales dashboard

B2B cannabis marketplace; API
documentation available via partner
portal

Dutchie Point-of-sale system for retail stores Well-documented API; developer
portal at developer.dutchie.com

Edge Google review prompting and customer

reputation management

Confirm webhook or API export
options with Edge support

BioTrack State compliance tracking (CT DCP

required)

State-managed system; confirm API
access with CT DCP or BioTrack
support

Distru Cannabis manufacturing, inventory, and

production ERP

API documentation available; confirm
access via Distru account settings

QuickBooks Accounting, financials, payroll, and

expense tracking

Well-documented REST API via Intuit
Developer portal
(developer.intuit.com)

Rodeo Cannabis Co | Developer Project Brief

Technical Requirements
1. MCP Server (Primary Deliverable)
The core deliverable is a Model Context Protocol (MCP) server that Claude AI can connect to.
This is the open standard Anthropic uses to allow Claude to query external data sources. The
developer should be familiar with MCP or be willing to learn it quickly.
Build an MCP server that exposes structured tools for each platform (e.g.,
get_daily_sales, get_wholesale_orders, get_compliance_status)
The MCP server should be self-hostable on a small cloud instance (e.g., AWS,
DigitalOcean, or similar)
Claude connects to the MCP server to answer business questions using live or recently
cached data

2. Data Pipeline & Sync
Pull data from each platform's API on a scheduled basis (configurable - target daily or
hourly syncs per platform)
Store normalized data in a lightweight database (PostgreSQL or SQLite preferred)
Handle API rate limits, authentication token refresh, and error logging gracefully
Provide a simple admin log or dashboard so non-technical staff can confirm syncs are
running

3. Query Capabilities
Once connected, Claude should be able to answer questions such as:
What were our top-selling products at Rocky Hill last week?
How do our wholesale order volumes compare month over month?
What is our current compliance status in BioTrack?
Which wholesale accounts haven't placed an order in 30+ days?
What is our manufacturing output vs. sales velocity for each SKU?
How are our Google review scores trending across locations?

4. Security & Access
All API credentials must be stored securely (environment variables or a secrets manager
- never hardcoded)
MCP server should require authentication to prevent unauthorized access
Data must remain within our controlled infrastructure - no third-party data sharing

Rodeo Cannabis Co | Developer Project

Deliverables
1. Working MCP server with tools for all six platforms
2. Automated data sync pipeline with error handling and logging
3. Deployment to a cloud server with setup documentation
4. Simple admin log showing sync status per platform
5. Documentation covering setup, credentials management, and how to add future
integrations
6. 30-day post-launch support for bugs and issues

Timeline & Budget
Phase Scope Est. Duration
Phase 1 API research, credential setup, architecture

design

1 week
Phase 2 Build data pipeline connectors for all 6 platforms 2–3 weeks
Phase 3 Build and test MCP server, connect to Claude 1–2 weeks
Phase 4 Deployment, documentation, and 30-day

support

1 week + 30 days

Estimated Budget: TDB depending on experience and approach. We are open
to milestone-based payment. Please include a detailed breakdown in your proposal.

Ideal Candidate
Experience building API integrations and data pipelines (Python or Node.js preferred)
Familiarity with Model Context Protocol (MCP) or willingness to learn it quickly -
documentation at modelcontextprotocol.io
Experience with cloud deployment (AWS, DigitalOcean, Render, or similar)
Strong communication skills - you will work directly with our CEO
Experience in cannabis tech, retail, or compliance systems is a bonus but not required
Ability to provide references or examples of similar integration projects

How to Apply
Please submit a proposal that includes:

Rodeo Cannabis Co | Developer Project Brief

Your relevant experience with API integrations and similar projects
Your familiarity with MCP or your plan to get up to speed
A proposed technical approach (brief - a few paragraphs is fine)
A project timeline broken down by phase
Your fixed-price or milestone-based budget
Links to 1–2 relevant past projects or GitHub repositories