The Financial Engine (Sprouts & Payouts)

Seedling’s financial engine is built around Sprouts. Sprouts are the platform’s value unit. They are not generic “points”. They are treated like tracked capital.

Any account can use Sprouts to fund (“seed”) collaborations. That includes organizations and regular users. This supports B2B, B2C, C2C, C2B, and hybrid models.

Earners receive Sprouts for outcomes. They can convert Sprouts to currency through payouts.

Key concepts

• Sprouts (human rewards): used to pay contributors and fund milestones.

• Growth Tool Credits (AI costs): reserved for Seeder AI features.

• Hard separation: purchased Sprouts must stay distinct from AI utility credits.

• Wallet = treasury: each account wallet behaves like a controlled budget.

Seeding workflow (funding work)

Seeders manage balances and transactions from wallet and settings surfaces.

What this enables:

• Allocate Sprouts to collaborations and milestone rewards.

• See real-time balances for the active account (personal or organization).

• Build a visible history of reliable payments.

• Attract high-credibility contributors faster.

Significance:

Seeding turns intent into execution for any collaboration. It removes doubt about whether work will be funded. It lets you signal seriousness before anyone commits time. It creates a clear trail of who rewards outcomes. It helps you attract stronger partners with less negotiation. Over time, it builds a reputation for reliable follow-through.

Earning workflow (earning → payout)

The UI focuses on earning and receiving Sprouts. The underlying system enforces payout guardrails.

Expected behavior:

• Earners accrue Sprouts from successful milestones.

• Payout eligibility follows platform rules (for example: minimum thresholds).

• Conversions happen fast once eligibility is met.

Significance:

Earning makes contribution measurable across every type of relationship. It rewards delivered outcomes instead of promises or popularity. It gives earners a clear reason to finish milestones. It creates portable proof of work through payout history. It turns trust into something you can build step-by-step. Over time, it aligns reputation with real results.

Payout mechanics (platform ledger ↔ Stripe Connect)

Payouts use a secure handshake between:

• the platform’s secure transaction ledger

• and the Stripe Connect API

This gives you:

• auditable state transitions

• threshold enforcement

• payouts that match traditional financial security expectations

UX example: payout flow (what a user experiences)

1

1) Connect a payout account (first time only)

From your wallet, choose Set up payouts. You complete the Stripe Connect onboarding. You see a confirmation that payouts are enabled.

2

2) Earn Sprouts

You complete a milestone or deliver an agreed outcome. Sprouts appear in your wallet as Pending or Earned. If the platform uses a review window, the Sprouts move to Available after it clears.

3

3) Check eligibility

In the wallet, you see your Available balance and your Minimum payout requirement. If you are below the minimum, the payout button stays disabled. If you are above the minimum, you can proceed.

4

4) Request payout

Tap Withdraw (or Payout). Choose a destination if multiple options exist. Confirm the amount. The wallet shows the payout as Processing.

5

5) Processing and completion

While Stripe processes the transfer, the payout remains Processing. Once completed, it switches to Paid. Your wallet balance updates immediately. A receipt-style record remains in your transaction history.

6

6) Common UX blockers (and what users see)

If Stripe onboarding is incomplete, you see a prompt to finish verification. If a payout fails, you see a Failed status with a retry option. If a compliance check delays processing, you see Pending review until it clears.

How this scales to teams

The payout flow stays the same for each person. What changes is how funds are seeded and tracked across multiple earners. A team is basically many individual payout flows running in parallel against a shared budget.

In a team setup, a seeder (an org or a person) typically funds a project or set of milestones. Multiple contributors can earn Sprouts from that same scope. Each contributor still withdraws to their own payout account. This keeps payouts clean and avoids “one person cashes out for everyone” problems.

This scales because the platform can:

• Split rewards across many people: each milestone can pay one or many earners.

• Keep a shared budget transparent: seeders see remaining balance and reward history.

• Preserve individual accountability: each payout is tied to a specific earner and outcome.

• Support approvals and controls (if enabled): teams can require confirmation before large payouts.

• Maintain an audit trail: everyone can trace what was funded, what was earned, and what was paid.

Why this matters

• Strategic seeding scales without manual bookkeeping.

• Real-time balance visibility improves trust on both sides.

• Rewarding outcomes creates a compounding talent flywheel.

• Every “Handshake of Value” is backed by real assets and traceable state.