Hi, I'm Adam. I co-founded the beverage technology company, Sidework, and have spent the last 7 years turning it into a real product.
Let's TalkThree skills I bring to the team.
From first prototype to enterprise scale. I've taken a product from concept through four generations, iterating on every failure until it worked at scale.
I don't design from a desk. I install, troubleshoot, and watch people use the product firsthand, then rebuild what doesn't work.
I make product decisions with the P&L in mind. What it costs to build, ship, and support matters as much as what it does. I've managed that tradeoff across four product generations.
The metrics that matter most.
Release cycles, review gates, testing protocols — if it didn't exist, I built it. Now I design them AI-first, with agents compressing the cycle below from ten days to a few.
That's the overview. Here's the full story.
I get my hands dirty to make things people actually care about.
Four hardware generations at Sidework. Each one represents a different chapter of my development, from sole designer, to team lead, to Chief Product Officer.
With zero ME experience, I designed the entire mechanical system: every fluidics path, every mechanism, every assembly. 9 months at HAX in Shenzhen learning CAD, working with factories, and prototyping until it worked. It had reliability issues, but it proved the market was real and secured our initial funding.
Now managing 3 engineers, I leveraged the team to simplify the Deluxe architecture by removing the ice dispenser and making dozens of reliability upgrades. I established engineering review gates and DFM processes. More importantly, I learned that the best products don't try to do everything. They do fewer things and do them well.
When coffee shops came calling, I led a ground-up redesign: 9 direct reports across mechanical, software, and electrical, $1.5M budget, and a far more sophisticated product. I built the process from scratch and navigated NSF certification alongside active development — meeting strict commercial food safety requirements without slowing the release timeline. 134 units deployed. 1M+ drinks dispensed. 99.9% uptime.
Everything I learned across four generations lives in Gen 3, designed from the ground up for mass-market adoption. This time it's built with a new set of AI tools and frameworks that accelerate development at every step — and the result is the most focused product I've ever designed.
The building blocks I'd bring, and how they map to what product organizations actually need.
Led a 9-person cross-functional team spanning mechanical, software, and electrical engineering. I built the product development process that aligned engineering, accelerated releases, and dramatically reduced release-related bugs.
I can run the whole team. I've aligned engineers across disciplines, created processes that keep things moving without falling apart, and shipped coordinated releases where everything works together on day one.
Built the product that secured $15M in funding at a $40M valuation. Translated technical progress into investor narratives, ran product demos for enterprise buyers, and shaped the roadmap that led to pilots with Coke, Pepsi, Swig, AMC, Inspire Brands, and Dutch Bros.
Stakeholder communication. I know how to translate technical complexity into language that resonates, whether the audience is a customer, manager, or investor.
Pioneered an AI-powered order routing system that works with any point-of-sale system out of the box — eliminating formal POS provider integrations entirely and enabling a deployment model no one in the industry has replicated.
I use AI to solve problems that aren't supposed to be solvable. When the conventional path was too slow, I found a way around it. I'll bring that same instinct to your product — finding the places where AI can unlock capabilities the market doesn't expect yet.
Navigated an international supply chain driving BOM cost from $12K to $6.5K (46%) and assembly cost from $5K to $550 (89%) across 3,000+ parts from ~60 vendors in US, China, and Mexico.
Unit economics discipline. I think in terms of what it costs to build, ship, and support, not just what to build. Product decisions that ignore economics don't survive contact with reality.
Co-founded Pumpt while running Sidework. Concept to manufacturing in under 12 months. Designed the product, built the supply chain, landed Burger King Canada. Patent pending.
0-to-1 velocity. When there's a new opportunity, I have a bias for action. I scope it, build it, and ship it. Fast enough that the market validates before the budget runs out.
These aren't aspirational principles. They're how I've actually worked for 7 years.
I spent seven years running product the old way — a backlog triaged into a fixed release cycle. Here's how the same work gets originated, routed, and shipped today, AI-first.
Work started as a list. A 1,000-row requirements doc, a column of feature requests, a stack of bugs. My job was to triage the backlog and pack the winners into the next 10-day cycle. Nothing shipped until the calendar let it.
Work starts in a thread. I group what comes in into themed goals, prioritize, and decide what I drive myself versus what I route to an engineer. It ships in days, not whenever the next cycle opens.
Every fix waited for a handoff. A well-scoped bug walked through manual scoping, build, beta, and production gates — roughly six people and ten days from report to release.
I drive the well-scoped work myself. A relay of agents tickets, builds, QAs, and reviews it in one thread; I steer the approach and give the single approval that merges and ships — without pulling an engineer off architecture.
I was a triager of backlogs into a calendar. The process kept things moving, but the calendar was the speed limit.
I'm a builder again. I originate, decide, and ship across software, firmware, QA, and docs from a single thread — and engineering stays focused on the frameworks the rest builds on.