Real regulated-delivery scope
This is a live product operating in a category where customer flow and compliance logic have to coexist.
Regulated delivery flagship
Green Run
Licensed cannabis courier platform for Boston-area delivery, built around compliant ordering, partner-menu sync, and real dispatch follow-through.
Green Run is a strong flagship proof surface because it sits in a regulated environment where the customer journey and the operator workflow cannot drift apart. The public site, ordering logic, menu sync, dispatch layer, and driver handoff all have to work as one system.
Role
Flagship delivery and compliance proof
System proof
Ordering, dispatch, driver handoff, and partner-menu sync
Stack
Next.js, Prisma, Dutchie, Stripe
Live scope
Customer ordering plus courier-side operational workflows
Business problem
Combine customer ordering and courier operations in a space where sloppiness is not acceptable
Regulated delivery cannot stop at a clean storefront. The system has to coordinate menus, eligibility gates, order routing, delivery logic, and partner workflows without making the customer experience feel broken.
Green Run was built around that tension: preserve a clear ordering path for the buyer while keeping the operator side grounded in compliant, auditable delivery flows.
System constraints
Design for compliance and operations first, then make the user journey feel simple
The hardest part of Green Run is not visual design. It is keeping regulated delivery steps coherent while multiple actors interact with the system: customer, partner dispensary, internal dispatch, and the driver in the field.
That drove the architecture toward connected workflows instead of isolated screens. Dutchie sync, order state, payment handling, and dispatch had to reinforce each other rather than compete.
Operating proof
Why this matters on the public site
Dispatch and driver work are part of the product
The proof is broader than checkout. It includes the operational handoff required to complete delivery cleanly.
Partner workflows were designed in, not bolted on
Menu sync and operational coordination matter because the business is only credible when those dependencies stay aligned.
What I learned
Regulated delivery software succeeds when product clarity and operator rigor are treated as the same job
Green Run reinforced a recurring studio lesson: the best customer-facing experience in a regulated business still fails if dispatch, partner data, and execution details are handled like an afterthought. The stronger build is the one that makes all of those layers legible at once.
Need a system that carries operational load?
JalenBuilds is strongest when the product has to do more than look good: regulated delivery, commerce, dispatch, quoting, or any workflow where real execution matters after the click.