# Evaluation Guide

Use this guide before adopting OpenHuman Online for a team, client, directory listing, or comparison page.

## Fit Check

OpenHuman Online is most relevant for teams adopting private AI memory, source planning, meeting briefs, and connector rollout.

Strong fit signals:

- You need inspectable memory tree planning.
- You need connector rollout map.
- You need meeting prep and follow-up drafts.
- You need obsidian-style note preview.
- You need hosted team annual checkout.

Weak fit signals:

- The team only needs a one-off answer rather than a repeatable workflow.
- No one owns the rollout, review, billing, or support path.
- The work would require private data before the team has a policy.

## First Review Questions

1. What exact problem will this product solve in the first week?
2. Which user or team owns the workflow?
3. What data, repo, transcript, or connector scope is allowed?
4. Which output should be reviewed before trusting the system?
5. What success signal justifies moving from preview to payment?

## SaaS Links To Use

| Need | Tracked link |
| --- | --- |
| Product evaluation | [home](https://openhuman.online/?utm_source=github&utm_medium=documentation&utm_campaign=openhuman_online_docs&utm_content=evaluation_home) |
| Plan comparison | [pricing](https://openhuman.online/pricing/?utm_source=github&utm_medium=documentation&utm_campaign=openhuman_online_docs&utm_content=evaluation_pricing) |
| Paid start | [checkout](https://openhuman.online/checkout/?utm_source=github&utm_medium=documentation&utm_campaign=openhuman_online_docs&utm_content=evaluation_checkout) |

## Decision Record

Copy this into your own notes:

```text
Decision:
Owner:
Allowed scope:
Blocked scope:
Default plan:
Review date:
Reason to continue:
Reason to stop:
```