Worked examples · design partners wanted
What Stride is built to enable.
Three buyer shapes Stride is built for. All examples below are illustrative — modelled on publicly visible patterns, not on any specific firm we've worked with. We're in early pilot phase and looking for design partners.
Design partners wanted — 5 slots open · for the buyer shapes below
Stride is in early pilot phase. The first 5 design partners get founder pricing locked in (20% off any annual tier, in perpetuity), direct WhatsApp / Slack to the build team, and first dibs on the named case-study slot that replaces the worked example for your buyer shape. After 5, public pricing stands. The examples below are modelled on publicly visible patterns — not on any specific firm we've worked with.
1Worked example · B2B stablecoin payment rail
Today · daily recon at most stablecoin rails
3hrs / day
Two ops people every morning matching on-chain receipts to bank deposits to merchant settlement obligations across 4 spreadsheets, 3 banks, and 4 chains.
With Stride · target outcome
20min / day
One screen shows what's matched, what's pending, what's stuck. Per-counterparty obligations reconcile to on-chain receipts first time. Settlements clear before lunch.
COO · target
Exception queue replaces the morning Slack thread.
CFO · target
Daily evidence the auditor accepts first pass.
Treasurer · target
Float position + counterparty obligations in one view.
“The morning recon is the first thing my ops team opens and the last thing they close. We chase exceptions in Slack threads. By the time it's done, half the day is gone.”
Composite of public LinkedIn posts and conference talks by ops leaders at stablecoin payment companies. Not a Stride customer.
Buyer profile we built for: ~25 person team · B2B stablecoin payment rail moving funds between importers, exporters, and logistics counterparties · 7 float positions across 3 banks (US + SG) and 4 on-chain wallets (Ethereum, Tron, Base, Solana) · ~140 inbound transactions per day · COO + CFO + Treasurer trio in the loop.
Today · the morning grind
Pull yesterday's on-chain receipts from 3 explorers; pull bank deposits from 3 portals; match each receipt to a sender on a merchant's customer list; chase exceptions in Slack; build per-merchant obligations; authorise settlements. Repeat next day. Repeat next day.
What a 30-day pilot would do
Connect 7 float positions (banks added as off-chain entries; wallets read-only via address). Configure counterparty grouping for 6 active merchants. Set up daily snapshots + settlement event tracking. Generate one daily close bundle. Success metric defined upfront: ops-team minutes per morning recon.
What the daily ritual would look like
08:00 SGT: ops lead opens
/close. 5 readiness checks ticked overnight. 15 min reviewing 3 pending + 1 unresolved. One click → daily evidence ZIP. Forwards to CFO; Treasurer authorises from same screen. Done by 08:20.2Worked example · Mid-market crypto fund / OTC desk
Today · monthly close + intraday risk
5days / month
Controller + analyst manually pulling balances across 18 wallets, cross-checking fund-admin NAV, categorising transactions in Excel, building audit packs by hand. NAV mismatches eat half the cycle.
With Stride · target outcome
1.5days / month
Daily snapshots reconcile to fund-admin NAV first time. Per-disposal P&L (FIFO/LIFO/HIFO) auto-tracked. One-click month-end ZIP: PDF + ERP CSVs + audit log.
CFO · target
Audit pack defensible, no week of follow-ups.
Controller · target
Per-entity, per-disposal P&L without spreadsheets.
Head of Trading · target
Intraday position visibility for risk calls.
“We spend more time explaining the mismatches than fixing them. The auditor comes back with five questions every month-end and we lose a week chasing things that should have been logged daily.”
Composite of public statements by crypto fund CFOs and controllers. Not a Stride customer.
Buyer profile we built for: ~50 person team · 3 legal entities (SG Pte Ltd + 2 BVI sub-funds) · ~18 wallets across Ethereum, Solana, Arbitrum, Bitcoin · custody split between BitGo and on-chain · CFO + Controller + Head of Trading in the loop.
Today · the month-end scramble
Pull balances from Etherscan / Solscan / mempool.space / BitGo portal. Cross-check fund admin's NAV against on-chain totals. Categorise transactions in Excel by entity. Build audit pack PDF manually. Chase the auditor for clarifications. Repeat for the next entity.
What a 30-day pilot would do
Connect all 18 wallets read-only. Set up entity grouping (SG Pte Ltd + 2 BVI sub-funds). Configure cost basis method (FIFO / LIFO / HIFO). Run one full month-end close cycle and generate evidence bundle. Success metric: controller hours saved on first close.
What month-end would look like
1st of month, 02:00 UTC: monthly report email auto-sent. Controller opens
/close, checks 5 readiness boxes, generates bundle ZIP. Forwards to auditor + uploads to fund admin. Auditor accepts first pass. Done by lunch.3Worked example · Enterprise CFO · crypto on balance sheet
Today · quarterly disclosure prep
2weeks / quarter
Controller and treasury analyst pull custodian statements, on-chain wallet positions, then build a board-ready disclosure pack manually. External auditor returns 5+ questions per cycle. ERP postings done by hand.
With Stride · target outcome
2days / quarter
Quarterly evidence pack auto-generated from continuous snapshots. ERP-ready CSVs (NetSuite / Oracle / SAP). External auditor accepts first pass. Board disclosure pulls clean numbers.
CFO · target
Quarterly disclosure defensible to board + regulator.
Controller · target
Crypto positions book to ERP without manual entry.
Internal Audit · target
Continuous evidence trail, not a quarter-end scramble.
“We hold stablecoin reserves for treasury yield and occasionally pay vendors in USDC. Every quarter our auditor wants evidence we cannot produce in one pass. We spend the first two weeks of every quarter just preparing the disclosure pack.”
Composite of public CFO commentary on enterprise crypto adoption (Block, MicroStrategy, Reddit-style firms). Not a Stride customer.
Buyer profile we built for: Mid-large enterprise (~200-2000 person team) holding $10M-$100M in stablecoin reserves for treasury yield + occasional vendor / contractor payments · 3-5 wallets, 1-2 institutional custodians (BitGo / Anchorage / Fireblocks) · CFO + Controller + Internal Audit + External Auditor in the loop.
Today · the quarterly disclosure prep
Pull custodian statements via PDF / portal export. Pull on-chain wallet balances at period boundary. Reconcile against ERP general ledger. Build board disclosure pack from scratch. Field auditor questions for two weeks. Re-do for the next quarter.
What a 30-day pilot would do
Connect all wallets + custodian accounts (read-only entry). Configure cost basis method for tax (typically FIFO for US GAAP). Set up quarterly close cadence + ERP-format CSV exports for your accounting stack. Generate one quarterly evidence pack. Success metric: auditor follow-up questions per cycle.
What quarterly close would look like
End-of-quarter snapshot frozen automatically. Controller opens
/close, generates evidence pack ZIP (PDF + ERP CSV + audit log + JSON). Forwards to external auditor. Auditor accepts first pass. Board disclosure compiles from same numbers.See your shape above? Be the first reference customer.
Five design-partner slots. Founder pricing locked in, direct line to the build team, named case-study slot replacing the worked example for your buyer shape.