Eprenz Partner Curation and Decision Guides
Purpose
Eprenz should not present partners as a random affiliate directory.
Partner curation should help founders make better business decisions.
The goal is to organize partner options around:
- founder problem
- knowledge context
- stage fit
- country fit
- comparison criteria
- Eprenz rationale
- next action
Comparison charts are useful, but they should not stand alone.
The full model should be:
flowchart LR
A[Founder Problem] --> B[Decision Guide]
B --> C[Comparison Criteria]
C --> D[Curated Partner Options]
D --> E[Eprenz Rationale]
E --> F[Next Action]Core Principle
Do not ask:
“What partner can we promote?”
Ask:
“What decision is the founder trying to make, and which partner options help them make progress?”
Why Curation Matters
Many partner directories sort by vendor category, ratings, or affiliate availability.
Eprenz should sort by founder problem and business context.
A founder does not usually think:
“I need a SaaS vendor.”
They think:
- I need a business bank account.
- I need to accept payments.
- I need a website.
- I need more customers.
- I need financial control.
- I need legal structure.
- I need funding.
- I need better systems.
Eprenz curation should translate that problem into a useful decision guide.
Benchmark Models
Eprenz should learn from existing marketplace and directory models without copying them directly.
| Benchmark | What They Do | What Eprenz Should Learn |
|---|---|---|
| HubSpot Solutions Directory | Filters partners by service, industry, country, and profile data | Use filters for problem, stage, country, partner type, and relevance |
| Shopify App Store | Uses categories, app cards, and quality signals such as Built for Shopify | Create Eprenz readiness labels such as OS Ready, Country Verified, Needs Review |
| AWS Marketplace | Helps users find, buy, deploy, and manage solutions | Connect partner discovery to implementation, not only listing |
| G2 | Uses software categories, reviews, ratings, and comparisons | Use comparison charts, but keep founder problem fit as the main lens |
| Affiliate review sites | Compare products and monetize through affiliate relationships | Avoid thin affiliate-style roundup pages and lead with education |
Eprenz Difference
Eprenz should not become a generic marketplace.
The Eprenz difference is:
Founder problem
→ knowledge guide
→ comparison criteria
→ curated partner options
→ action
Not:
Partner category
→ affiliate link
Research-Based Curation Rules
| Rule | Meaning |
|---|---|
| Start with the founder problem | The page should answer a real founder need |
| Teach before presenting options | Explain the decision before showing partners |
| Use clear comparison criteria | Compare what matters to the founder |
| Show why each partner is included | Add Eprenz rationale |
| Disclose relationships | Be clear when Eprenz has affiliate, sponsor, or referral relationships |
| Avoid unsupported claims | Do not call something best unless the reason is clear |
| Keep pricing current or avoid it | Pricing changes often, so mention only if verified |
| Mark unknowns internally | Unknown country support, tracking, or approval status should be reviewed before publication |
| Include alternatives when possible | Avoid showing only one option if founders need comparison |
| End with a next action | Guide, checklist, event, partner link, or advisor follow-up |
Disclosure and Trust Rule
If Eprenz has a material relationship with a partner, such as affiliate, referral, sponsor, or paid placement, the relationship should be disclosed clearly.
Use a simple disclosure near the partner comparison.
Example:
Disclosure: Some partner links may be affiliate or referral links. Eprenz may receive compensation if you use them. We include partners based on founder problem fit, stage fit, country availability, and usefulness.
Do not hide disclosure in the footer only.
Do not make partner content look like neutral education if it includes paid or affiliate relationships.
Decision Guide Format
Each curated partner page should follow this structure:
1. Founder problem
2. Short answer
3. Why the decision matters
4. What to compare
5. Curated partner options
6. Eprenz rationale
7. Disclosure
8. Next action
Example structure:
Problem: I need to choose a business bank.
Short answer:
Choose based on country availability, fees, payment needs, integrations, support, and future growth.
What to compare:
Country availability, account type, fees, minimum balance, card access, integrations, international transfers, support quality.
Partner options:
Show approved and relevant banking partners.
Next action:
Compare options, open an account, or attend a banking setup session.
Comparison Chart Criteria
Every comparison chart should include practical fields.
| Field | Purpose |
|---|---|
| Partner | partner name |
| Best For | use case where this partner is most useful |
| Founder Stage | Start, Grow, Profit, Exit, or multiple |
| Country Availability | where the partner works |
| Main Use Case | what the founder would use it for |
| Setup Complexity | simple, moderate, advanced |
| Key Strength | why this option may be useful |
| Limitations or Notes | what the founder should check |
| Tracking Available | yes, no, manual, unknown |
| Eprenz Relationship | affiliate, sponsor, solution partner, global partner, advisor, none |
| Eprenz Note | short reason this option is included |
| Last Reviewed | date of last review |
| Status | ready, needs review, paused, unknown |
Eprenz Recommendation Labels
Use practical labels instead of ranking every option as “best.”
| Label | Meaning |
|---|---|
| Best for first setup | good for early-stage founders |
| Best for simple use | low setup complexity |
| Best for growth | useful when the business has traction |
| Best for advanced needs | better for complex operations |
| Best for global use | broad country or currency support |
| Best for service businesses | useful for consultants, agencies, and service providers |
| Best for ecommerce | useful for online stores |
| Country-specific | availability depends on location |
| Needs review | not enough data yet |
| Advisor review recommended | human judgment should come before referral |
Example, Domain Name Decision Guide
Founder Problem
I need to choose and secure a domain name.
What to Compare
Founders should compare:
- domain availability
- renewal cost
- privacy protection
- DNS control
- transfer control
- email setup options
- support
- ownership and account access
- website or hosting integration
Example Comparison Chart
| Partner | Best For | Stage | Country Availability | Setup Complexity | Eprenz Note |
|---|---|---|---|---|---|
| Partner A | simple domain purchase | Start | verify | simple | useful for first domain setup |
| Partner B | domain plus hosting bundle | Start, Grow | verify | simple to moderate | useful when founder wants domain and hosting together |
| Partner C | advanced DNS and security | Grow, Profit | verify | advanced | useful for more technical setup |
Next Action
Start with a domain name guide, then compare approved domain partners.
Example, Business Banking Decision Guide
Founder Problem
I need a business bank account.
What to Compare
Founders should compare:
- country availability
- account type
- monthly fees
- minimum balance
- card access
- payment integrations
- accounting integrations
- international transfer support
- support quality
- compliance requirements
Example Comparison Chart
| Partner | Best For | Stage | Country Availability | Setup Complexity | Eprenz Note |
|---|---|---|---|---|---|
| Partner A | first business checking account | Start | USA or verify | simple | useful for founders opening their first account |
| Partner B | online banking and integrations | Start, Grow | country-specific | simple to moderate | useful when founder wants digital tools and integrations |
| Partner C | larger business banking needs | Grow, Profit | country-specific | moderate | useful for higher transaction volume or more complex needs |
Next Action
Read the business banking guide, compare available options, then choose based on country, fees, and operational needs.
Example, Payment Processor Decision Guide
Founder Problem
I need to accept payments.
What to Compare
Founders should compare:
- supported countries
- supported currencies
- transaction fees
- payout timing
- checkout experience
- invoicing support
- ecommerce integration
- refund and dispute handling
- accounting integration
Example Comparison Chart
| Partner | Best For | Stage | Country Availability | Setup Complexity | Eprenz Note |
|---|---|---|---|---|---|
| Partner A | online card payments | Start, Grow | country-specific | moderate | useful for accepting payments online |
| Partner B | invoices and service payments | Start, Grow | verify | simple | useful for consultants and service businesses |
| Partner C | ecommerce checkout | Grow | country-specific | moderate | useful for online stores |
Next Action
Start with the payment setup guide, then compare approved payment partners.
Example, CRM Decision Guide
Founder Problem
I need to manage leads and sales better.
What to Compare
Founders should compare:
- pipeline setup
- contact management
- email integration
- automation
- reporting
- pricing
- ease of use
- team access
- integration with website and forms
Example Comparison Chart
| Partner | Best For | Stage | Country Availability | Setup Complexity | Eprenz Note |
|---|---|---|---|---|---|
| Partner A | simple lead tracking | Start, Grow | global or verify | simple | useful for founders moving beyond spreadsheets |
| Partner B | sales automation | Grow | global or verify | moderate | useful for businesses with repeatable sales activity |
| Partner C | advanced reporting | Grow, Profit | global or verify | advanced | useful for teams needing visibility and process control |
Next Action
Use the CRM decision guide, then choose a CRM based on sales process maturity.
SEO and AEO Page Structure
Each decision guide should be structured so it can be found through search and answer engines.
Use this structure:
Title:
How to choose a business bank account for your business
Short answer:
2 to 4 sentence direct answer
Decision criteria:
What founders should compare
Comparison chart:
Curated options
FAQ:
Common founder questions
Next action:
Guide, checklist, event, partner option, or advisor follow-up
SEO and AEO Rules
| Rule | Meaning |
|---|---|
| Use question-based titles | Match founder search intent |
| Give a direct short answer near the top | Helps both humans and answer engines |
| Use tables for comparisons | Makes criteria clear |
| Use consistent headings | Improves readability and machine understanding |
| Avoid thin affiliate pages | Content should be useful even without partner links |
| Include last reviewed date | Keeps trust and freshness |
| Use visible disclosure | Required for trust |
| Keep claims verifiable | Avoid unsupported rankings |
| Add next action | Turns search traffic into founder progress |
Structured Data Notes
Structured data should only be used when it matches visible page content.
Possible future structured data types may include:
- FAQ content if visible on the page
- ItemList-style comparison lists if the page presents a real list
- Product or service markup only when appropriate and accurate
- Review markup only when Eprenz has real review content and meets search guidelines
Do not add structured data only to manipulate search.
Structured data should clarify content that already exists on the page.
Where Curated Decision Guides Should Appear
| Surface | Use |
|---|---|
| Mighty Knowledge Layer | practical founder education |
| OS | next action after Compass or journey step |
| Partner Page | searchable comparison and filtering |
| Email Follow-up | short guide after survey or Compass response |
| Events | topic guide before or after workshop |
| Network | discussion starter or expert thread |
| Advisor Follow-up | advisor uses guide to recommend next step |
| Social Media | educational post that points to full guide |
| GFIS | sponsor or partner activation tied to real founder problem |
Internal Publishing Checklist
Before a curated partner guide is published, confirm:
| Check | Required |
|---|---|
| Founder problem is clear | Yes |
| Top category and subcategory are mapped | Yes |
| Decision criteria are included | Yes |
| Partner options are active or clearly marked | Yes |
| Country availability is clear or marked for review | Yes |
| Eprenz rationale is written | Yes |
| Affiliate or sponsor disclosure is included | Yes |
| Tracking method is known | Yes, manual allowed |
| Claims are not exaggerated | Yes |
| Pricing is verified or avoided | Yes |
| Last reviewed date is included | Yes |
| Next action is clear | Yes |
Final Rule
Eprenz curation should help founders make a decision.
A curated partner page should be useful even if the founder does not click a partner link.
If the page only exists to promote a partner, it does not fit the Eprenz OS model.