ECP Digital Bank
Complete documentation of the 4 product lifecycle phases — from strategic context to operations.
Delivering on the computer — where they work, decide, and build their future — the most intelligent, clear, and integrated financial experience in the country.
Millions of young Brazilian professionals spend eight hours a day in front of a computer, yet are forced to manage their finances on mobile, on small screens, with fragmented data and no context. ECP Digital Bank exists to eliminate that contradiction.
Number of unique users per week who perform at least one interaction with intelligent financial features — smart statement, proactive insights, or financial planning.
Phase Timeline
Quick Access
Phase Summaries
Definition of strategic objective: "Win the first users who adopt ECP as their primary digital bank on the computer", with 5 measurable Key Results. Competitive analysis of 6 rivals revealed a universal gap — none offers a robust web-first experience.
10 opportunities prioritized across 3 pillars (Entry, Daily Use, Intelligence). 4 hypotheses selected for prototyping (H1–H4). Backlog with 3 epics, 14 features and 25 user stories with BDD/Gherkin acceptance criteria. 4 risks assessed, all approved.
DDD architecture with 5 bounded contexts. Stack: Fastify 5.0 + SQLite3 + React 18.3 + Vite 5.4 + Tailwind CSS 3.4. API with 9 modules and 27 endpoints. Frontend with 10 pages and 9 components. QA with 29 test cases and 10/10 quality gates passing.
GitHub Actions pipeline with 6 jobs (code-quality, unit-tests, build, change-gate, deploy-production, quality-gate). GMUD-001 approved for initial release. Deploy strategy: Node.js + PM2 for API, static hosting for SPA.