FIN Product Tier Architecture

Date: 2026-05-15 Status: Draft v0.1 Related: docs/FIN_PLATFORM_DOC_INDEX.md, docs/projections/PROJECTION_CATALOG_2026-05-15.md, docs/engineering/FIN_AGENTIC_HARNESS_SPEC_2026-05-15.md

0. Purpose

This doc defines the five product tiers FIN sells against the same underlying platform. Engineering reads it to understand entitlements per tier. Sales reads it to understand what each tier costs and what it includes. Customer Success reads it to understand SLAs and migration paths. The Projection Catalog reads it to gate which projections are available per tier.

If tier definitions diverge across docs, this doc is the source of truth.

1. The Five Tiers At A Glance

Tier	Name	Audience	Anchor Price	GTM Role
0	Read-Only Intelligence MCP	Developers, universities, federal, researchers	Free → $999/mo enterprise quoted	Public credibility + open ecosystem + federal lever
1	Lightweight Tenant Agent	Single-warehouse small distributors	$499-$1,499/mo	Volume tier, broad market
2	Produce Agent Pro	Mid-size produce companies	$4,500-$15,000/mo per location	Economic anchor — Nathel sits here
3	Executive Agent	Multi-location operators, executive workflows	$25,000+/mo per seat	Premium relationship, Orgo-enabled
4	Platform / ERP	ERP replacement at scale	$100,000+/yr per location	Destination tier, post-funding

Tier 0 + Tier 2 is the focus through 2026. Tier 1 / 3 / 4 are framed but deferred until after the Nathel proof loop closes.

2. Architectural Foundation

All five tiers run on the same platform: four-table substrate, event store, projection layer, agentic harness, MCP layer. What differs across tiers is the configuration:

• which projections are available
• which MCP tools are exposed
• which agent skill bundles load
• which channels are enabled
• which data planes are readable/writable
• which onboarding path applies
• which support SLA is contracted
• which OpenClaw policies are enforced

No tier requires a fork of the platform. Tiering is configuration over code.

3. Tier 0 — Read-Only Intelligence MCP

3.1 Audience

External developers building agents that need produce intelligence. University researchers and extension services. Federal and state agencies. Foodservice / retail analysts. Other agtech companies. Hobbyist / consumer developers.

3.2 What They Get

• Read-only access to Harvest Directory entity profiles via public MCP
• Aggregate intelligence projections (commodity situation, regional outlook, season window)
• search_docs, get_doc, get_entity_profile, walk_provenance, list_recent_changes
• Versioned, citable, reproducible
• Open corpus releases (Wave 4+) for those who want to train their own models
• Self-service API key signup
• Public documentation site

3.3 What They Don’t Get

• No write capability of any kind
• No tenant-private data
• No real-time event stream from any specific operator
• No proposal / commit tools
• No A2A initiation toward other tenants
• No operator agent skills

3.4 Pricing

• Free tier: 1,000 calls/month, public attribution required
• Developer: $99/month, 100K calls
• Team: $999/month, 5M calls + priority SLA
• Enterprise: quoted, includes federal-safe routing where applicable

Heavy usage tiers gate by call count, not by tenant count.

3.5 Onboarding Path

Self-service: signup form → API key → docs site → “hello world” call → first integration. No human onboarding required for free/developer tiers. Team and Enterprise tiers get a brief call.

3.6 SLA

• Free: best-effort
• Developer: 99% monthly uptime, 24-hour support response
• Team: 99.5% monthly uptime, 8-hour business-hour response
• Enterprise: 99.9% monthly uptime, 2-hour response, named contact

3.7 Wave Assignment

Public Tier 0 ships Wave 3 at earliest (requires Harvest Directory + anonymization gate + public MCP infra). Pre-Wave-3, the same tool catalog can be used internally for partner demos.

4. Tier 1 — Lightweight Tenant Agent

4.1 Audience

Single-warehouse produce distributors, small farms with direct-sales business, foodservice distributors with simple SKU mix, operators who just want operational intelligence but not full multi-channel agent.

Typical firmographic: 5-25 employees, single location, $5-25M revenue.

4.2 What They Get

• Web-only Workspace access (no mobile-first PWA features)
• Read-only projections of their own tenant data
• Daily arrivals summary, lot status, basic event digests
• Tenant agent with single-channel chat (web only)
• Email / SMS alerts (one-way notifications, no reply-back agent)
• Reference Harvest Directory (Plane 3) for free
• 30-day event retention default

4.3 What They Don’t Get

• No voice
• No WhatsApp
• No customer portal
• No vendor portal
• No agent enrichment loop (propose_doc_edit not exposed)
• No executive agent
• No federal mode
• No Orgo

4.4 Pricing

• Starter: $499/month, 1 user, 1 location, 10K events/month
• Growth: $1,499/month, 5 users, 1 location, 100K events/month

4.5 Onboarding Path

3-step onboarding (subset of the 10-step PK v2 program): identity → data connect → first workflow. Self-service with optional 30-minute call.

4.6 SLA

99.5% monthly uptime, business-hour support, community forum primary.

4.7 Wave Assignment

Wave 4+. Resist the temptation to build Tier 1 until Tier 2 anchor (Nathel) is proven and Tier 0 public ships. Tier 1 is the easiest tier to build (it’s a feature-limited Tier 2) but the hardest to support at volume — solo-operator constraints apply.

5. Tier 2 — Produce Agent Pro (the economic anchor)

5.1 Audience

Mid-size produce companies. Wholesale distributors. Specialty importers. Regional foodservice chains. Multi-product brokers.

Typical firmographic: 25-200 employees, 1-5 locations, $25-250M revenue. Nathel sits here.

5.2 What They Get

• Full multi-channel agent: web + mobile PWA + voice + SMS + WhatsApp + email
• Read-write projections within tenant scope
• Operator agent + ops agent skill bundles
• All projections from the Projection Catalog except executive-only and federal-only
• Customer portal (customer audience: tenant’s customers)
• Vendor portal (vendor audience: tenant’s vendors)
• Customer-facing voice agent for inbound orders / inquiries
• Tenant intranet (GitHub vault + Workspace doc reader)
• Telnyx 2-3 phone numbers per tenant
• Agent enrichment loop (propose_doc_edit enabled)
• Proof package generation (assemble_recall_trace available with privileged role)
• Reference Harvest Directory
• 7-year event retention default (FSMA-compatible)

5.3 What They Don’t Get (yet — Tier 3/4 upgrades)

• Executive agent with calendar/email/Orgo
• Custom skill bundle development
• Federal mode
• Marketplace (deferred)
• ERP replacement (Tier 4)

5.4 Pricing

• Pro: $4,500/month per location, 25 users, 1M events/month
• Pro Plus: $9,000/month per location, 100 users, 5M events/month
• Pro Custom: $15,000+/month per location, unlimited users, negotiated events

Per-channel surcharge applies above included channels (extra phone numbers, additional WhatsApp business numbers, etc.).

5.5 Onboarding Path

Full 10-step PK v2 onboarding with a Nathel-cohort-style 3-act program (per project_agentic_onboarding_program memo). Solo-operator-paced for the first 3-5 tenants; productized after.

5.6 SLA

99.9% monthly uptime, 4-hour response (24/7 critical), named CSM at Pro Plus and above, quarterly business reviews.

5.7 Wave Assignment

Wave 1-3. This is the active build. Nathel is the first deployment. The full Tier 2 ships in stages:

• Wave 1: web Workspace + operator agent + 1 channel + tenant docs
• Wave 2: mobile PWA + voice + SMS + customer portal + entity profiles
• Wave 3: full multi-channel + vendor portal + proof package generation
  • enrichment loop

6. Tier 3 — Executive Agent

6.1 Audience

Produce-company executives (founder, CEO, COO) who want an agent that helps them with executive workflows: strategic decisions, customer relationship management, board prep, investor communication, multi-loc operational visibility, partnership sourcing.

6.2 What They Get

• Everything in Tier 2 plus
• Executive agent with calendar / email / scheduling integration
• Orgo cloud workstation (visible, auditable browser/desktop agent operations for tasks too complex for headless agents)
• Voice agent with executive context (briefings, daily catch-up, decision support)
• Custom skill bundle development (per-executive tuning)
• Decision record co-authoring (agent drafts, executive approves)
• Multi-location operational visibility (single pane across all Tier 2 locations)
• Quarterly proof package as polished executive briefing
• Dedicated executive CSM

6.3 What They Don’t Get

• Federal mode (separate add-on per Tier)
• Marketplace (Tier 4 add-on)
• ERP replacement (Tier 4)

6.4 Pricing

• Executive: $25,000/month per executive seat, requires existing Tier 2
• Executive Plus: $50,000+/month per seat, multi-location synthesis, Orgo included, custom skill development
• Family Office / PE / Strategic Buyer pricing quoted

6.5 Onboarding Path

Full executive intake: weekly cadence calls during onboarding, custom skill bundle development, calendar/email/voice integration, OpenClaw policy review for executive-level actions.

6.6 SLA

99.95% monthly uptime, 1-hour response, named executive support, on-demand specialist access.

6.7 Wave Assignment

Wave 4. Strictly post-Nathel-Tier-2-proof. Don’t build executive agent capability for Nathel unless Sam/Stefanie explicitly request it.

7. Tier 4 — Platform / ERP

7.1 Audience

Produce companies replacing their existing ERP (Famous Software, Produce Pro, Silver Mountain) with FIN as the primary operating platform.

7.2 What They Get

• Everything in Tier 2 + Tier 3 plus
• Full order-to-cash flow (FIN as system of record, not extractor)
• Full procurement-to-pay flow
• Full inventory management (lot, pallet, location, age tracking)
• Full accounting integration (or replacement)
• Marketplace (when phased in per marketplace planning memo)
• Custom workflow development
• White-label tenant portal option

7.3 What They Don’t Get

• N/A — this is the destination tier

7.4 Pricing

Enterprise quoted only. Range: $100K-$1M+/year per location depending on volume and complexity. Implementation services separate.

7.5 Onboarding Path

6-12 month implementation. Parallel run against existing ERP. Cutover gates. Migration runbooks per legacy ERP. Dedicated implementation team (eventual — solo-operator until first hire).

7.6 SLA

99.99% monthly uptime contracted, 30-minute response 24/7, dedicated support engineering, named account team.

7.7 Wave Assignment

Wave 5+. No Tier 4 deployment before 2027 at the earliest. Nathel remains Tier 2 + Tier 0 + (optional Tier 3 executive add-on) — explicitly not Tier 4.

8. Tier × Capability Matrix

The canonical entitlement table. Cells use:

• ✅ included
• ➕ available add-on
• ❌ not available
• 🔒 federal/regulatory-gated

Capability	T0	T1	T2	T3	T4
Channels
Web Workspace	❌	✅	✅	✅	✅
Mobile PWA	❌	❌	✅	✅	✅
Voice (inbound)	❌	❌	✅	✅	✅
Voice (outbound)	❌	❌	➕	✅	✅
SMS	❌	➕	✅	✅	✅
WhatsApp	❌	❌	✅	✅	✅
Email agent	❌	❌	✅	✅	✅
MCP for tenant agents	❌	❌	✅	✅	✅
MCP public read	✅	✅	✅	✅	✅
Projections
Reference Harvest Directory	✅	✅	✅	✅	✅
Tenant entity profiles	❌	✅	✅	✅	✅
Daily/weekly digests	❌	✅	✅	✅	✅
Proof packages	❌	❌	✅	✅	✅
Recall traces	❌	❌	✅	✅	✅
Executive briefings	❌	❌	❌	✅	✅
Marketplace projections	❌	❌	❌	❌	➕
Portals
Customer portal	❌	❌	✅	✅	✅
Vendor portal	❌	❌	✅	✅	✅
White-label portal	❌	❌	❌	❌	➕
Agents & Skills
Operator agent	❌	✅	✅	✅	✅
Ops agent	❌	❌	✅	✅	✅
Executive agent	❌	❌	❌	✅	✅
Custom skill bundle	❌	❌	❌	✅	✅
Orgo cloud workstation	❌	❌	❌	✅	✅
Agent enrichment loop	❌	❌	✅	✅	✅
Platform
GitHub vault (tenant intranet)	❌	❌	✅	✅	✅
Workspace doc reader	❌	✅	✅	✅	✅
Event retention	n/a	30 day	7 year	7 year	7 year+
Federal mode	🔒	❌	🔒	🔒	🔒
ERP capability surface	❌	❌	❌	❌	✅
Marketplace	❌	❌	❌	❌	➕
Support
Community forum	✅	✅	✅	✅	✅
Email support	❌	✅	✅	✅	✅
Phone support	❌	❌	✅	✅	✅
Named CSM	❌	❌	✅ (PP+)	✅	✅
Dedicated implementation team	❌	❌	❌	❌	✅
QBR	❌	❌	✅ (PP+)	✅	✅

9. Tier Migration Paths

Migration is a first-class motion, not an exception. The platform supports each transition without data migration or re-onboarding.

Tier 0 → Tier 1/2: Public MCP user signs up for tenant. Existing API key carries usage history into tenant analytics. No data migration; the tenant starts fresh.

Tier 1 → Tier 2: Channel and projection entitlements expand. Existing tenant data stays. New skill bundles load. Onboarding adds the 7 steps not done in Tier 1’s 3-step path.

Tier 2 → Tier 3: Tier 2 base remains. Executive agent adds. Custom skill development begins. No re-onboarding for existing users.

Tier 2/3 → Tier 4: Implementation engagement opens. Parallel run against existing ERP. Tier 4 capabilities unlock per migration runbook. This is a months-long process; Tier 2/3 stays active throughout.

Downward migration: Customers may downgrade. Data retention follows the new tier’s policy with 90-day grace. Skill bundles unload but doc projections remain.

10. Federal Mode Add-On

Federal mode is an orthogonal add-on, not a tier. Tier 0, 2, 3, or 4 tenants may add federal mode, which enables:

• federal-safe model routing (Anthropic Bedrock FedRAMP, sovereign endpoint)
• audit export to federal-grade format
• data residency commitments
• recall trace tools with regulator-audience flag
• SBOM / provenance reporting
• federal contract vehicle support

Pricing: 30% premium on base tier, $50K minimum annual.

Wave assignment: Wave 4 for shipping; Wave 1-3 for readiness work.

11. Nathel Tier Mapping

Per project_nathel_deployment + project_nathel_endpoint_architecture:

• Primary tier: Tier 2 Produce Agent Pro
• Included by default: Tier 0 public Harvest Directory (Nathel can link customers to it)
• Optional add-on (executive request only): Tier 3 Executive Agent for Joshua Gatcke (VP) or Jacob Gatcke (GM); not anticipated in initial deployment
• Explicitly excluded: Tier 4 ERP (Nathel keeps Produce Pro running)
• Federal mode: Not in initial deployment, evaluated for Wave 4

This mapping is the scope guardrail. Anything that doesn’t serve Tier 2 deployment for Nathel is deferred.

12. Catalog Cross-Reference

Every Projection Catalog entry should be tagged with which tiers it serves. The Catalog v0.2 update should add a tiers: [T0, T1, T2, T3, T4] field to every projection entry.

Example:

projection: commodity_profile.watermelon
tiers: [T0 (anonymized via Harvest Directory), T2, T3, T4]

projection: recall_trace.LX2026-1142
tiers: [T2, T3, T4 (federal mode required for regulator audience)]

projection: executive_briefing.weekly
tiers: [T3, T4]

Until this tagging lands, default assumptions:

• entity profiles → T0 public + T2/3/4 tenant
• event digests → T2/3/4 tenant
• proof packages → T2/3/4 tenant + federal flag for federal audience
• aggregate intelligence → T0 public only

13. Sales Motion By Tier

• Tier 0: Self-service developer signup, content marketing, GitHub presence, Hugging Face model release.
• Tier 1: Inside sales, low-touch, demo-to-close in 1-2 calls.
• Tier 2: Founder-led until first hire. Anchor reference selling. 3-6 week sales cycle.
• Tier 3: Executive sponsor + founder. 2-4 month sales cycle.
• Tier 4: Enterprise sales motion (post-funding). 6-12 month sales cycle. RFP-driven.

14. Stop Conditions

Add a tier or change definitions only if:

• the new tier is materially distinct (not just a price point)
• engineering effort is bounded (configuration, not platform fork)
• support model is solvable (solo-operator can sustain or hire trigger is hit)
• catalog tier-tagging stays consistent

Do NOT add intermediate tiers (Tier 2.5) — split via add-ons (federal, extra channels, custom skill) instead.

15. Open Questions

ID	Question	Default
TQ-1	Should Tier 1 ship before Tier 0 public MCP?	No. Tier 0 ships Wave 3; Tier 1 ships Wave 4+.
TQ-2	Is marketplace Tier 4 only or available as T2/T3 add-on?	Tier 4 only initially; revisit post-launch.
TQ-3	What’s the executive-agent fair-use cap on Orgo time?	Quoted per contract.
TQ-4	When do consumer-facing Tier 0 features (recipes, seasonal guides) split into a separate offering?	Wave 4.
TQ-5	Federal mode availability on Tier 0 — public/Tier-0-federal-friendly?	Yes, distinct route + FedRAMP infra, post-Wave-3.