Professional Summary: Peptide Portal Strategy Sync

This call was a tactical planning session between Stan and Alton focused on reducing ambiguity, narrowing the MVP, and deciding what needs to happen before a Thursday investor/demo conversation with 359 Capital. The main conclusion was clear: do not overbuild the marketplace, distribution, or real-time data infrastructure yet. Launch first as an affiliate-driven peptide sourcing portal with a curated set of high-quality vendors.

The team aligned around three core workstreams:

Build the portal
Develop demand-side outreach
Develop supply-side vendor/affiliate relationships

The strongest strategic insight from the conversation is that the portal’s core purpose is not to become a research encyclopedia first. The core purpose is to help people find high-quality peptides and make purchasing decisions. Research, SEO, regulatory updates, and agent-driven content can become powerful supporting layers, but they should not distract from the buy-flow MVP.

1. Current State

Product direction

The team is building a peptide sourcing portal focused on helping buyers identify quality vendors, compare products, and eventually purchase through affiliate or distribution relationships.

The immediate monetization model is affiliate-first, not marketplace, dropshipping, or direct distribution. The team explicitly decided to table more complex “middleman” monetization models for now because they introduce sourcing, contracts, inventory, fulfillment, and distribution complexity too early.

MVP philosophy

The team repeatedly came back to the same principle: keep it simple.

The MVP should help users:

Search or browse peptides
See which vendors offer them
Compare basic quality and pricing signals
Click through using affiliate links
Trust that the listed vendors meet a quality threshold

Everything else is secondary.

That is the correct call. The biggest risk right now is not whether the team can build more features. The biggest risk is getting buried in complexity before validating that buyers care and vendors will participate.

2. Key Decisions Made

Decision 1: Affiliate is the first monetization play

The team agreed that affiliate links are the first practical revenue path. The work is straightforward: identify programs, sign up, collect links, structure vendor data, and route traffic through the portal.

Implication: No need yet for inventory, order handling, payment processing, fulfillment, or formal distribution agreements.

My read: Correct. Affiliate is the fastest way to test demand without operational drag. Distribution can come later once the team has proof of traffic, buyer intent, and vendor leverage.

Decision 2: Quality matters more than vendor quantity

The team aligned that having 20 to 30 high-quality vendors is more valuable than listing everyone. Alton suggested that roughly 30 quality providers would be enough to create meaningful signal, while Stan emphasized that the value comes from accurate, important data, not raw vendor count.

Implication: The portal should not look like an unfiltered directory. It should look like a curated intelligence layer.

My read: This is strategically important. A generic peptide directory has low trust. A curated portal with clear quality standards can become defensible.

Decision 3: Real-time pricing and inventory are not needed for MVP

The team discussed scraping, Python wrappers, cron jobs, and alternatives to expensive scraping services, but ultimately agreed that daily inventory and price updates are not necessary for the first version.

Implication: The MVP data model can start with manually enriched or periodically refreshed data.

My read: Correct. Real-time pricing sounds impressive but is not the bottleneck. Vendor coverage, affiliate setup, trust signals, and buyer acquisition matter more right now.

Decision 4: The portal should focus on buying decisions, not just information

Stan pushed the team back toward the core purpose: the site exists to help people buy peptides. Research pages, knowledge graphs, legal updates, and agent-generated content should support that purpose, not replace it.

Implication: Every feature should be judged by whether it increases trust, reduces buyer uncertainty, or improves conversion.

My read: This is the most important product discipline from the conversation. The team is prone to building interesting systems. The business needs a simple conversion engine first.

3. Product and UX Insights

The current UI has promising pieces, but should be stripped down

The team reviewed the portal and identified that some visual elements look good but may be wasting space. The “verified providers” card layout was questioned because it is aesthetically interesting but may not be the clearest way to compare vendors.

The stronger view appears to be the peptide-specific comparison/detail view, especially where users can see vendors, price normalization, and quality signals.

Recommended MVP page structure

The MVP should likely have three core page types:

1. Peptide detail page

Purpose: help users understand a peptide and find vendors.

Core sections:

Peptide overview
Primary use cases
Vendor comparison table
Quality signals
Price comparison, ideally normalized per mg where possible
Affiliate CTA buttons
Basic research links
Legal/regulatory note

2. Vendor profile page

Purpose: help users trust or compare a supplier.

Core sections:

Vendor name
Location
Peptides offered
COA/testing status
Third-party testing references
Affiliate program status
Shipping regions
Notes/flags
Link to vendor

3. Research page

Purpose: support SEO and trust, not distract from conversion.

Core sections:

Plain-English summary
Study links
Human vs animal vs in vitro evidence
Timeline of new findings
Regulatory updates
“Find vendors offering this peptide” CTA

4. Data Strategy Insights

The team needs a stripped-down MVP schema

Stan correctly identified that the team is at risk of overcomplicating the data model. For the MVP, the data should support the pages and buying flow, not every possible future research or regulatory feature.

Minimum viable data objects

Peptides

Should answer:

What is this peptide?
What is it commonly used for?
Which category does it belong to?
Is it in scope for human optimization?
What vendors offer it?
What research or legal caveats matter?

Suggested MVP fields:

id
name
slug
category
short_description
primary_use_cases
status
research_summary
legal_summary
created_at
updated_at

Vendors

Should answer:

Who sells this?
Are they credible enough to list?
Where are they based?
Do they have affiliate or partnership options?

Suggested MVP fields:

id
name
slug
website_url
location_country
location_state
quality_status
coa_available
third_party_testing_available
affiliate_program_status
affiliate_signup_url
affiliate_tracking_url
notes
created_at
updated_at

Vendor peptide offerings

This is probably the most important table because it connects vendors to peptides.

Suggested MVP fields:

id
vendor_id
peptide_id
product_name
product_url
affiliate_url
price
currency
quantity_mg
price_per_mg
purity_claim
coa_url
testing_source
availability_status
last_checked_at
created_at
updated_at

Research studies

Should start simple.

Suggested MVP fields:

id
peptide_id
title
source_url
study_type
species
summary
published_year
created_at
updated_at

5. Strategic Insights

Insight 1: The real wedge is trust in a messy market

The peptide market is fragmented, opaque, and difficult to verify. Buyers need help understanding:

Which vendors are credible
Which products have COAs
Which products have third-party testing
Which peptides are legal or research-only
Which claims are backed by evidence
Which vendors have reasonable pricing

The portal should position itself as a trust and decision layer, not merely a directory.

Insight 2: The initial customer may be B2B, not only consumers

The team discussed practices and clinics looking to source peptides at scale. That changes the product logic.

For B2B buyers, the key buying criteria may be:

Reliability
Testing
COAs
Legal status
Bulk pricing
Distribution capability
Consistency of supply
Location/shipping
Vendor responsiveness

The team should not assume that consumer-facing criteria are the same as clinic/practice criteria.

Insight 3: SEO can become a major moat, but not on day one

The research-page idea is strong. Alton’s idea of continuously updating peptide research pages as new studies or regulatory changes emerge is strategically valuable. It creates both user trust and search freshness.

But this should come after the MVP buying flow works.

Best future version:

Each peptide has a canonical research page
New studies are monitored
AI summarizes new findings
Pages are updated with timestamps
Regulatory changes are tracked
Vendor pages are connected to research and legal context

That could become a serious SEO engine.

Insight 4: The team has enough information to execute

The call started with concern about unanswered implementation details. By the end, the answer was clear: yes, there are unanswered questions, but not enough to block execution.

The correct next step is not more planning. It is a one-week sprint around:

Finalizing MVP portal UX
Building the vendor database
Signing up for affiliate programs
Creating demand-side outreach
Preparing a Thursday demo

6. Action Items

Product / Portal

Owner: Alton

Finish final UX/layout changes today.
Simplify the portal around the main buying flow.
Replace or reduce visually interesting but low-utility sections.
Prioritize the peptide-specific vendor comparison experience.
Prepare a working demo for Thursday morning.
Hand off implementation/data model needs to Stan after final design pass.

Owner: Stan

Finalize the MVP data schema based on what the portal actually needs.
Strip schema down to peptides, vendors, offerings, affiliate links, and basic research.
Prepare data for the first set of peptides and vendors.
Normalize pricing where possible, especially price per mg.
Decide which quality fields are mandatory for listing.

Supply Side

Owner: Ed, with support from Stan/Alton

Build the master vendor list.
Identify the top 20 to 30 highest-quality vendors.
Confirm which vendors have affiliate programs.
Sign up for affiliate programs.
Collect affiliate links and tracking links.
Contact vendors that do not have public affiliate programs.
Investigate distribution or partnership potential, but do not make it an MVP dependency.
Capture due diligence notes for each vendor.

Demand Side

Owner: Alton, possibly Stan

Build a target list of clinics, practices, peptide buyers, and health optimization operators.
Create an outbound campaign.
Use direct outreach as the near-term traction engine while SEO compounds.
Position the portal as a tool for finding high-quality peptides and suppliers.
Drive early users to the Thursday demo/product.
Collect feedback on what buyers actually care about when evaluating vendors.

Investor / Demo Prep

Owner: Alton

Prepare a Thursday morning demo for the 359 Capital conversation.
Show the product as working, not theoretical.
Tell a clear story:
- Peptide sourcing is fragmented and low-trust.
- Buyers need quality, price, COA, testing, and legal clarity.
- The portal solves discovery and trust first.
- Affiliate is the first monetization layer.
- Distribution and deeper vendor partnerships come later.
- Capital accelerates vendor coverage, demand-side acquisition, SEO content, and data automation.

Owner: Stan

Help shape the capital-use narrative.
Define what funding would accelerate:
- More vendor coverage
- Better data collection
- Automated research/content system
- Outreach infrastructure
- Regulatory/quality verification
- SEO scale

7. Pending Questions

Product Questions

Who is the primary MVP user: consumers, clinics, health optimization practices, or all of the above?
What is the first conversion event: affiliate click, email capture, vendor inquiry, or booked consultation?
Should the homepage lead with peptide search, vendor discovery, or trust/research?
Should each peptide page be more educational or more transactional?
What exact trust badges should be shown?
Is “COA verified” a vendor-level signal or peptide/product-level signal?
What data must be visible above the fold on peptide pages?

Vendor Questions

What is the minimum quality standard required to list a vendor?
Does every listed product need a COA?
Does every vendor need third-party testing?
How should vendors be ranked?
Should vendors without affiliate programs still be listed?
Should poor-quality vendors be excluded entirely or shown with warnings?
How often does vendor/product data need to be refreshed?

Data Questions

What are the exact MVP fields for peptides?
What are the exact MVP fields for vendors?
What are the exact MVP fields for product offerings?
Should pricing be stored raw, normalized, or both?
How should “purity” be represented when vendors report it differently?
How should unavailable or unknown data be displayed?
What fields are required before a peptide/vendor can go live?

Legal / Regulatory Questions

What legal status should be tracked for each peptide?
Should legal status be tracked by country, state, or both?
How should “research use only” be explained?
What disclaimers are required?
Can the site make product recommendations without creating legal risk?
How should the site handle peptides with prescription, compounding, or gray-market issues?
Should the site avoid dosage guidance entirely?

Research / SEO Questions

Which peptides deserve research pages at launch?
How many studies should be attached per peptide for MVP?
Should research pages distinguish human, animal, and in vitro evidence?
Should the site include an “evidence strength” score?
How often should research pages be updated?
What sources should be trusted?
Should an AI agent eventually monitor new studies and update pages?

Business Model Questions

What affiliate programs are available for the target vendors?
What are the expected commission rates?
Which vendors are open to custom partnership or distribution agreements?
Is the long-term model affiliate, paid placement, subscription, lead-gen, distribution, or marketplace?
Should vendors be allowed to pay for visibility?
How will the portal preserve trust if vendors pay?
What is the first revenue target?

8. Recommended Next 7-Day Sprint

Day 1: Lock MVP scope

Finalize portal layout.
Finalize schema.
Define listing criteria.
Create the shared vendor research tracker.

Day 2: Build vendor database

Add 20 to 30 candidate vendors.
Capture peptide coverage, COA/testing status, location, affiliate status, and product links.
Normalize prices where possible.

Day 3: Affiliate setup

Create one shared business email for affiliate accounts.
Sign up for all available affiliate programs.
Store affiliate links in the database.
Contact vendors without self-serve affiliate programs.

Day 4: Demo polish

Load real vendor data into the portal.
Make the peptide detail pages feel credible.
Prepare demo narrative for 359 Capital.

Day 5: Demand-side outreach

Build lead list of clinics/practices/operators.
Draft outreach copy.
Start small outbound test.
Ask for feedback, not just sales.

Day 6: Feedback loop

Review buyer responses.
Identify what fields buyers ask for.
Adjust vendor comparison UI and schema accordingly.

Day 7: Revenue test

Push traffic to live pages.
Track affiliate clicks.
Track search behavior.
Track which peptides get the most interest.
Decide whether to expand data, content, or vendor relationships next.

9. Bottom-Line Assessment

The team is directionally right, but the risk is obvious: overbuilding the intelligence layer before validating the transaction layer.

The correct MVP is not an AI research engine, a full marketplace, or a regulatory knowledge graph.

The correct MVP is:

A trusted, curated peptide sourcing portal that helps buyers compare quality vendors and click through to purchase.

After that works, the research engine, legal-status tracker, automated content updates, and vendor partnership layer can become the moat. But right now, the team should sprint toward a simple, functional demo with real vendors, real affiliate links, and a clear buying path.