Portfolio/Venture
WalletKing
Beta recruitment and validation
Help people understand their spending, develop financial accountability, and make better decisions with their money.
Accountability is the appeal. Budgeting clarity is the mechanism. People should come for accountability and find that the budgeting is genuinely useful.
The tree
.-. .-. FRUIT The outcome we want .-( '-' )-. An application people return to because it .' '. genuinely improves their understanding of ( ( ) ( ) ) their finances. '._ _.' '~---------~' | * * | * * LEAVES What the beta is testing . . | . . Watch real use. Do not advertise ahead of `. .' | `. .' it. `-..-' | `-..-' .--. | .--. BRANCHES Capabilities .-' `-. | .-' `-. The product surface the beta has to make ( )------|------( ) trustworthy. `-. .-' | `-. .-' `--' | `--' | TRUNK The product | WalletKing is a financial accountability | application. The promise is | accountability. The mechanism is a .----|----. ROOTS What the beta can stand on .-' | `-. The early product is already tied to real .' | `. financial data and a small group of people ____/__________|__________\____ willing to try it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SOIL The problem
SoilThe problem
No separate points on this layer.
RootsWhat the beta can stand on
- Financial and technical knowledge.
- Plaid integration.
- AI capabilities.
- Product design and user experience.
- Early adopters and beta testers.
- Customer feedback and behavioral insight.
TrunkThe product
No separate points on this layer.
BranchesCapabilities
- Financial data aggregation.
- Transaction categorization.
- AI-assisted spending insights.
- Budgeting.
- Expense tracking.
- Financial pattern recognition.
- User engagement and accountability.
LeavesWhat the beta is testing
- Plaid onboarding.
- Real-world transaction testing.
- Categorization accuracy.
- AI insight quality.
- User experience interviews.
- Retention and willingness to pay.
FruitThe outcome we want
No separate points on this layer.
The next year
Recruit and onboard the initial testers
Reach 20 real beta users
Collect feedback and evaluate the actual user experience
Begin focused deployments and improvements
Improve reliability, onboarding, retention, and product quality
Evaluate paid conversion and sustainable customer acquisition
November 2026 through October 2027. Bars are the November 1 timeframes, read onto this year. August through October are open on purpose. The blueprint does not schedule them. October 2026 is already behind this chart. A dim bar is not started. A full bar is in motion or done. Blocked work drops to a thin opacity so it stays visible.
Objectives
The year chart above is the same work, drawn from November 2026 through October 2027. Status stays in this browser.
WalletKing/First 30 days
Recruit and onboard the initial testers
Start near ten people. Watch the friction yourself.
WalletKing/By December 2026
Reach 20 real beta users
A validation milestone. Not product-market fit.
WalletKing/December 2026
Collect feedback and evaluate the actual user experience
Categorization, insight quality, onboarding friction, and whether people come back.
WalletKing/January 2027
Begin focused deployments and improvements
Changes earned by December's feedback, not a new feature list.
WalletKing/Q1 2027
Improve reliability, onboarding, retention, and product quality
WalletKing/Q2 2027
Evaluate paid conversion and sustainable customer acquisition
Only after the experience has earned it. The $5 figure remains a hypothesis until then.
Beta testers
The first ten teach you. Twenty is the December validation mark. Neither number is product-market fit, and neither is a reason to buy ads.
0 of 20 toward December
- Learn from actual transactions, not a demo account.
- Watch categorization, insight quality, and where onboarding stalls.
- Ask whether they would pay about $5 a month. Record the answer as evidence, not as a price.