Earlybean — family finance across parents, children, schools and merchants
Earlybean began as a financial-literacy product for children and evolved into a family-finance and school-payments ecosystem. I co-founded the company and led product direction and hands-on design across the parent, child, school and merchant experiences.
A financial-literacy app was not enough
Earlybean started with lessons, savings goals and a child-centred experience. It taught the mechanics of saving, but gave families limited ways to apply them with real money.
What parents and schools actually needed
Across at least five school conversations and repeated parent feedback, the same tensions kept surfacing. Parents did not want another standalone banking relationship: they wanted to fund children from accounts they already used, retain control, and understand how money was being used. Schools wanted oversight inside their own environments. Children needed safe, practical places to save, spend and transfer real money.
Reframing the product around relationships
The product stopped being only a child-facing app. It became a system connecting a parent’s authority, a child’s bounded financial identity, a school’s oversight and operating role, and a merchant’s ability to receive and manage money. Trust, permissions and money movement became the architecture; the interfaces followed from that model.
Giving parents authority without another banking app
Parents needed distinct controls for funding, approvals, limits, visibility and blocking. The product treated the parent as the authority over a child account rather than a customer expected to adopt a new bank, so parents could fund children from accounts they already used while retaining control over what happened next.
Making money behave differently by purpose
Money in a savings goal was locked and not spendable. Money loaded onto a card or wristband could be spent with approved merchants inside school environments or curated events. Transfers ran on a separate rail through Earlybean IDs or validated bank accounts. The product had to make those states and rails legible because each carried different risks, permissions and expectations.
Turning schools into safe financial environments
Schools needed more than a fee-payment endpoint. The product direction covered onboarding, monitoring, school payments, ancillary payments and oversight across school-owned and third-party merchants. Direct spending stayed restricted to approved school environments, giving schools control over merchant acceptance and reducing the risk around children carrying spendable money.
What shipped, what remained directional
Shipped: parent-controlled child accounts, savings goals, card and wristband spending, Earlybean ID and bank transfers, school onboarding and monitoring, and the merchant application. Directional, and not presented as shipped: advanced school messaging, the complete school money OS, deeper school-owned and third-party merchant management, revenue-share or rental tracking, and the broader ancillary-payment operating model.
Evidence and critique
Figures from the Earlybean backend snapshot, July 2026. The same backend snapshot listed 895 parents and 2,635 children. These categories are presented as recorded and are not added to or reconciled against the active-user figure.
The snapshot proves production use, active accounts and real money movement. It does not tell us how often families returned, how activity changed over time, or how deeply individual schools adopted the platform. The broader school operating model also remained only partly implemented.
