Plant champions
Founders, farmers, and operators trying to identify the plant(s) they can honestly serve, steward, explain, and stand behind.
Plant champions. Community service. Farm-rooted strategy.
Find the plant(s) your community needs. Champion them.
My path has been ashwagandha. Yours might be another plant or a small set of plants that serve your community directly. I help herbal founders, farms, and operators turn those relationships into devotional service work with a product, story, quality system, market path, technology stack, and operating model strong enough to last.
01
Portland Ashwagandha Farm founder/operator
02
Full-time farming since 2012
03
Supplement brand operator, 10+ years
04
Technologist since 1995; consultant 2000-2012
Right fit
Best for people ready to champion plant(s) in service to a community.
Ashwagandha is my lived example, not the only answer. The real work is finding the plant(s) or ingredient that belongs to your community, then building the practical structure around them.
Ashwagandha and botanical questions
People with sourcing, quality, cultivation, processing, story, market-access, or product questions that need perspective from someone who has lived a plant deeply.
Farms, brands, and partners
Teams evaluating a community-rooted herbal product, sourcing relationship, market fit, or operating plan and needing to know whether it is grounded in reality.
Not a fit
Generic wellness marketing, unsupported claims, trend chasing, extractive plant stories, miracle-product language, or pitch work that avoids operating truth.
Reality check
Start with a plant champion reality check.
A first engagement should save you from confusion, not create another project. The cleanest starting point is a focused read on the plant(s), the community they serve, the product idea, sourcing logic, operating system, or market-access decision before more time or money gets committed. The goal is to separate genuine service from noise while the plan is still flexible.
Good starting questions
- Which community should the plant(s) serve, and how do you know?
- Are the plant(s) right for that service?
- Are you overfocused on details that do not move the market while missing what does?
- Are you building from relationship, evidence, and usefulness, or just borrowing category language?
- Do sourcing, processing, potency expectations, records, and quality expectations support the brand?
- Can the story, channel, and operating system carry the service intent without getting vague?
What you get back
- A plain-language read on what matters, what does not, and where the real risk sits.
- A ranked list of community, plant, brand, quality, market, sourcing, and operating tradeoffs.
- A clear call on what to stop worrying about for now.
- A practical next-step plan for founders, farms, brands, investors, or partners.
- When useful, a channel map, operating model, spreadsheet, dashboard, database, or prototype.
Areas of work
Three ways I help plant champions turn devotion into structure.
The work is tailored to the decision: plant(s) selection and positioning, ashwagandha or botanical advisory, market access, or the technical systems and records needed to make the service promise real.
Plant Champion Strategy
Help clarifying which plant(s) can serve your community directly, what role you are qualified to play, and what the product or project can credibly promise.
Deliverable: a focused strategy memo separating genuine service from expensive distractions.
Ashwagandha and Botanical Advisory
A practical read on ashwagandha or other botanicals: sourcing, product form, cultivation context, processing, potency expectations, quality standards, and what the market story can support.
Deliverable: a positioning readout, brand-management plan, or channel map for reaching the right community and market.
Technology, Records, and Quality Systems
Spreadsheets, dashboards, databases, iOS and web tools, automation, records, ISO 9001-style quality thinking, AHPA context, and workflows designed around real staff and real timing.
Deliverable: a cleaned-up workflow, operating model, prototype, automation plan, or quality-system map people can actually use.
Engagement examples
Examples of bounded questions worth answering early.
Clarify which plant(s) directly serve the community you care about, and whether the source and proof support that relationship.
Figure out what is actually distinct about the plant(s), the community, and your role before you spend heavily on packaging, claims, or channels.
Map channels, buyers, pricing, brand management, inventory, fulfillment, community promises, compliance pressure, and cash timing.
Translate ISO 9001-style quality thinking, documentation discipline, AHPA context, and AHPA Botanical Congress themes into practical routines, dashboards, and records.
Prepare an operator-level memo for founders, boards, funders, lenders, or partners evaluating a community-rooted herbal plan.
Experience
I translate between plant devotion, operations, brand, and market reality.
Early roots
Grew up around community-cultivated land, with roughly 1.5 acres under cultivation across three adjoining backyards.
2000-2001
Earlier farm seasons that kept the field perspective alive during the beginning of a long technical career.
1995 onward
Technology work across software, infrastructure, databases, automation, and systems design, with a bias toward tools people actually adopt.
2000-2012
Full-time technical consulting, including work at Intel, an independent consulting practice, iOS and web-based systems, and Portland-area infrastructure and design projects.
Portland metro
Consulting with regional companies where success depended on adoption, communication, and good judgment under constraints.
2009 onward
Current farming chapter, including irrigation built from scratch, scrappy infrastructure, seasons, markets, weather, people, tools, and cash timing.
2012 onward
Full-time farm operation, with the daily accountability that comes from needing land, labor, water, products, records, and sales to work together.
2015 onward
Founder, owner, and operator of Portland Ashwagandha Farm, with years spent learning the crop, the farm systems, and the story behind the product.
Brand operator
More than 10 years owning and operating a dietary supplement brand, including products, customers, fulfillment, records, and practical constraints.
Financial services and technology
PMO and financial-services context, plus fluency with automation, software tools, technical infrastructure, reporting, and executive operating cadence.
Quality and botanicals
Conversant with ISO 9001-style quality systems, AHPA references, AHPA Botanical Congress context, and responsible herbal-products commerce.
Proof of range
Ashwagandha is the case study, not the cage.
Field execution
Knows the crop past the brochure.
My lived plant has been ashwagandha. The lesson is broader: plant relationships have to survive soil, water, harvest windows, processing pressure, labor, quality expectations, and real-world timing.
Systems fluency
Can build the system, not just describe it.
Decades in technology, including software systems, iOS and web-based tools, databases, reporting, and automation, mean the advice can turn into usable tools instead of another recommendation nobody adopts.
Brand and systems
Has operated the brand, not just the field.
More than 10 years owning and operating a dietary supplement brand means the advice includes product identity, category fit, customers, fulfillment, records, compliance pressure, and the friction of turning plant service into a viable offering.
Operating discipline
Understands executive cadence and operating pressure.
Financial services project work gives me a practical feel for accountability, reporting, priorities, deadlines, diligence, and the gap between a plan and execution.
Founder story
A plant champion, with systems discipline.
I am the founder, owner, and operator of Portland Ashwagandha Farm, in operation since 2015. My farming background started early: I grew up around roughly 1.5 cultivated acres across three adjoining backyards tended by our community, farmed again in 2000 and 2001, began this current farming chapter in 2009, and have farmed full time since 2012.
Alongside that field experience, I worked full time as a technical consultant from 2000 to 2012, including work at Intel, my own technical consulting firm, and consulting across Portland-area companies on software systems, technical infrastructure, databases, automation, iOS and web-based tools, and design.
I moved into farming to build a more grounded, balanced, outdoor life, then spent more than a decade operating a farm and dietary supplement brand in the real weather of production, sales, systems, cash flow, and community. Now I consult on ashwagandha and help people in the herbal supplement space find the plant(s) they can champion as practical devotional service.
Technical consultant, 2000-2012
Farm roots since childhood
Current farm chapter since 2009
Full-time farmer since 2012
Founder/operator since 2015
Supplement brand operator
Ashwagandha as lived case study
Technologist since 1995
iOS and web systems builder
Automation and database fluent
Approach
How I make the advice useful
1. Name the service question
We start with the community, plant, product, brand, channel, quality, or operating decision that needs a clearer answer.
2. Read the plant-to-community system
I review the farm reality, records, workflow, people, tools, data, margins, quality expectations, channel incentives, community need, and brand promise shaping what is actually possible.
3. Challenge the distracting assumptions
I help sort the details worth caring about now from the ones that can wait, so you do not build your plan around the wrong anxiety.
4. Leave behind usable structure
The outcome is a clear readout, prioritized next steps, and, when useful, a channel map, tool, model, automation path, quality routine, or operating plan that can survive contact with the season and the market.
Contact
Start with what you are trying to build.
Send a short note with the plant(s) you feel called to champion, the community you want to serve, the decision in front of you, why now, and what would make the engagement useful. The strongest first inquiries include a plant, source, product, channel, quality, or market-access question that is specific enough to wrestle with.
I am currently taking a small number of right-fit introductory consulting projects at practical rates for early clients who are a strong fit.
What happens next: I read for fit, urgency, and whether the problem is in range.
If I can help, we set up a focused first call. If I am not the right person, I will say so plainly.
Jeff@comfrey.net
Email Jeff about a first call