Four upgrades to the Hey Jessica platform: Plaid-powered budgeting with an AI coach, an ad-supported free tier, a smarter feedback loop, and a roadmap for multiple chatbots, each scoped as a clear, milestone-based deliverable.
Following our discussion on August 3rd, here is the scope, timeline, and pricing for the new features you asked us to quote. Each is structured as a milestone-based deliverable, so you always know exactly what is being built and what it costs, no open-ended hourly work. These can run alongside the ongoing app build.
Connect users' real bank data and turn it into guardrails and a personal AI coach. Delivered in two parts so you can proceed in stages.
Connect users' bank accounts through Plaid, pull their transaction data securely, and surface it in a clean internal dashboard, with spending thresholds and budget guardrails that alert a user when they go outside the budget they have set.
Analyze the data to detect recurring spending behaviors and turn them into personalized notifications and AI coach nudges, for example flagging a recurring Tuesday spend before it happens, or suggesting an alternative when a user is trending over budget.
Timeline: approx. 6 to 7 weeks · Part 1 first, then Part 2, which builds on Part 1 and the use cases you define.
Run a free version of the app alongside the paid version, supported by in-app ads. We recommend starting with Google AdMob: it is the most reliable to integrate, has strong payouts, and its advertiser demand suits a finance app well. AppLovin and Unity can deliver higher revenue through mediation, but their demand skews toward gaming and they are more complex to set up, so the best path is to launch on AdMob and layer in AppLovin mediation later if we want to push ad revenue higher.
Timeline: approx. 2 to 3 days.
A thumbs up / down control on each Hey Jessica response that routes to a review dashboard, where a response can be adjusted and added to the knowledge base, so the AI continuously improves from real feedback.
Timeline: approx. 2.5 to 3 weeks.
We understand the vision: multiple chatbots, for example your new etiquette book, that share one underlying knowledge base while each has its own shell, intro, and rules per site.
Each request is billed as its own milestone, and Request 1 can proceed in two parts. Timelines can overlap and are contingent on finalizing the current app and your input on the Plaid and behavioral use cases.
Simple and staged, the same way we run every build.