All work

Avenox product · Avenox product · iOS · AI finance

In active development

A personal AI money operator built to make the next decision clearer.

AMO turns connected, read-only financial data into grounded answers about what is safe today, what needs protection, and what move should come next.

AMO is an Avenox-owned product in active development. An iOS and TestFlight foundation exists while the latest product work remains under release review.

The challenge

Most finance apps explain the past or expose another dashboard, then leave the user to make the hard decision alone. AMO needed to combine deterministic money logic, conversational AI, and clear proof without pretending to move funds or know more than the connected data supports.

The scope

Product strategy, native iOS experience, backend architecture, read-only financial-data integration, deterministic finance engine, AI conversation, privacy, safety, and release engineering.

Current product foundation

AMO

Expo / React NativeNode.js + PostgreSQLPlaidOpenAIApple TestFlight + Railway
  • A native iOS product experience centered on conversational money decisions
  • Read-only connected-account architecture with provider data handled behind the app
  • Deterministic logic for Available Today, bills, paycheck planning, purchase checks, debt, and savings
  • Persistent AI conversations grounded in financial evidence and guarded by deterministic validation
  • Privacy, authentication, safety, audit, and release foundations supported by broad automated testing
Current AMO native chat screen with review and money-question actions
AMO chat · Current native experienceConversation is the primary product surface: AMO refreshes the evidence first, then helps the user review their money or ask a direct question.

The outcome, honestly

AMO now has a locally release-verified native and backend foundation that can transform connected financial data into conservative, explainable next moves. It remains an active Avenox product—not a publicly launched banking service—and every action stays user-controlled.

Next phase · Next native release and field validation

The next phase is focused on shipping the newest verified product work carefully, validating it on real devices, and strengthening delivery for broader release.

  • Deploy the latest reviewed backend and matching database migrations
  • Publish the next TestFlight build and complete real-device scenario testing
  • Add remote push, background refresh, and long-history pagination before broader scale

Want a foundation like this one?