Phase 01 — Strategic Context

OKRs, OST (Opportunity Solution Tree), North Star Metric and product principles defined by the Product Manager Agent.

Product Vision

3–5 Year Vision

For Brazilian micro-entrepreneurs who lose time and money with banks that ignore their business needs, ECP Emps is the web-first digital bank that automates business financial management with intelligence, unlike existing PJ digital banks because it is the only one that integrates personal (PF) and business (PJ) accounts in one place with AI-powered automatic categorization and a native desktop experience.

Opportunity window: 12–18 months of first-mover advantage in the web-first PJ segment before competitors react.

Beachhead segment: Digital Freelancer MEI (ages 22–35, digital services, natural desktop affinity, lowest CAC, highest product-market fit for MVP).

North Star Metric

North Star

EFAS — Financially Active Companies per Week

Number of companies with 3+ financial operations in the last 7 days. Captures the moment when the company uses ECP Emps as its primary bank.

COUNT(DISTINCT company_id FROM pj_transactions WHERE created_at >= 7d ago GROUP BY company_id HAVING COUNT >= 3)

Activation Rate

35%+

3+ ops in 7 days after opening

Invoices/company

2+/month

Usage as a billing tool

Toggle PF↔PJ

2+/session

PF-PJ integration value

ARPAC

R$ 70/month

Average revenue per company

D30 Retention

45%+

OKRs — Q2 2026 (April–June)

Objective

Make ECP Emps the digital bank that freelancer MEIs trust to separate, organize, and bill — replacing spreadsheets, bad banks, and the PF/PJ financial mess.

Key Results

KR-01

Reach an activation rate of 35% (companies with 3+ operations in 7 days after opening)

Baseline: 0% Target: 35%

Activation Rate = companies_3tx_7d / companies_created * 100

Measurable

KR-02

Achieve an average of 2+ invoices issued per active company per month

Baseline: 0 Target: 2+

invoices(status!=cancelled, parent=null) / active_companies

Measurable (with refinement)

KR-03

Achieve an average of 2+ PF↔PJ toggles per session

Baseline: 0 Target: 2+

toggle_events / sessions_with_toggle

Requires analytics_events

KR-04

Achieve D30 retention of 45% (login 30 days after opening)

Baseline: 0% Target: 45%

companies_login_d28_32 / companies_created_30d_ago * 100

Measurable

Opportunity Solution Tree (OST)

12 mapped opportunities (pains, needs, and desires) — no solutions, following Teresa Torres.

KR-01 Activation Rate 35%

OPP-01 Pain

MEIs cannot open a PJ account quickly because banks require excessive documentation and slow bureaucratic processes

Personas: Ana Beatriz, Lucas · 73% of MEIs have no formal financial control

OPP-02 Need

Entrepreneurs need to immediately understand the value of the PJ account in the first session to justify switching banks

Ana: “Inter PJ account does not work well on desktop” — if value is not seen quickly, they abandon

OPP-03 Desire

MEIs want the PJ account to come pre-configured with the tools they need, without manual setup

Product principle: “Automation beats configuration”

KR-02 2+ invoices/company/month

OPP-04 Pain

Issuing a billing invoice is bureaucratic and expensive in current banks, making MEIs give up on formal billing

Ana pays R$ 2/invoice at Inter · Lucas finds B2B invoices complicated

OPP-05 Need

Freelancers need to charge clients professionally (with company details) without losing time configuring each billing

Ana: 8–12 active clients per month · Agency with multiple clients

OPP-06 Pain

MEIs don’t know when a client paid or stopped paying because reconciliation between billing and statement is manual

Lucas: “reconciliation of iFood with the statement is manual”

KR-03 2+ PF↔PJ toggles/session

OPP-07 Pain

MEIs mix personal and business expenses because having two accounts in separate apps is too inconvenient

42% do not separate PF/PJ · Ana mixes expenses on PF card

OPP-08 Need

Entrepreneurs need to see the complete financial picture (personal + business) for decisions like owner’s draw withdrawals

Market gap: no competitor offers a consolidated PF+PJ dashboard

OPP-09 Desire

MEIs want to instantly transfer money between personal and business accounts without bureaucracy

BR-13: instant PF-PJ transfer same ownership

KR-04 D30 Retention 45%

OPP-10 Pain

MEIs don’t know how much the business actually earns per month because they have no accessible cash flow tool

Ana doesn’t know how much she profits · Lucas feels he’s losing money · 58% use spreadsheets

OPP-11 Need

Entrepreneurs who work on computer need a bank that fully works on desktop

No PJ competitor offers a complete desktop experience · Ana works 100% on computer

OPP-12 Pain

Companies with more than one person cannot give partial account access without sharing passwords

Mariana and Thiago: “Cora doesn’t allow giving partial access to the assistant”

Product Principles

Desktop first, mobile always

The primary experience is designed for desktop (1280px+), with mobile as a companion.

In practice: Every feature is designed first for large screen; mobile receives a simplified version.

Trade-off: We give up mobile-only market share to gain productivity with the audience that works on computer.

Automation beats configuration

The system makes the right choice automatically instead of asking the user to configure.

In practice: Automatic categorization; CNPJ Pix key registered at opening; invoice with intelligent defaults.

Trade-off: We give up flexibility for power users in favor of simplicity for the majority.

Financial clarity above all

The entrepreneur must know exactly how much they have, how much comes in and how much goes out — without mental calculation.

In practice: Dashboard shows real profit; clear business categories; cash flow charts always visible.

Trade-off: We prioritize transparency even if it reveals the business is doing poorly.

PF and PJ are one entrepreneur

The person and the business coexist; the bank must reflect this reality.

In practice: PF/PJ toggle in the same app; instant PF-PJ transfer; consolidated view.

Trade-off: We give up total independence between PF and PJ in favor of an integrated experience.

Free at core, premium for extras

Essential operations (Pix, invoices, account) are free; advanced features may be premium.

In practice: Unlimited Pix for free, free invoices, no monthly account fee.

Trade-off: We give up immediate per-operation revenue in favor of adoption and volume.

Entrepreneur’s data belongs to the entrepreneur

Full access and export of financial data, without lock-in.

In practice: Statement export in CSV/PDF, downloadable reports, open API (future).

Trade-off: We make client departure easy, betting that superior experience ensures retention.

Security without unnecessary friction

Protect the entrepreneur without them feeling like they’re fighting against their own bank.

In practice: Additional confirmation only above R$ 5K; automatic nighttime limit; RBAC by profile.

Trade-off: We accept that smaller limits pass without extra confirmation in favor of fluidity.

Outcome Roadmap

Now — Apr/May 2026

The entrepreneur opens the account, operates and feels the bank understands their business

MEIs open PJ account in < 3 min and make first operation the same day
Entrepreneurs charge clients with invoice+Pix without another system
Entrepreneur perceives the PF-PJ connection in the same environment

KR-01 KR-02 KR-03

Next — Jun/Jul 2026

The entrepreneur understands where the money goes and makes better decisions

MEIs know how much they profited without a spreadsheet
AI automatic categorization eliminates manual work
Entrepreneurs with partners delegate access with confidence

KR-01 KR-02 KR-04

Later — Aug/Oct 2026

ECP Emps becomes indispensable for the business’s financial health

Entrepreneurs trust ECP Emps to anticipate cash flow problems
ARPAC reaches R$ 70/month via premium services
Accountants recommend it as the best PJ account for MEIs

KR-02 KR-04

Competitive Analysis

Player	PJ Clients	Web Desktop	Free Pix	Free Invoice	E-Invoice (NF-e)	AI Management	PF-PJ Integration
Nubank PJ	15M+	Partial	✓	✓	✗	✗	Basic
Cora	1.4M+	CoraWeb	✓	✓	Paid	✗	✗
Inter PJ	5M+	Partial	✓	✓	✗	✗	✗
C6 Bank PJ	3M+	✗	✓	Paid	✗	✗	✗
PagBank PJ	8M+	Partial	✓	✓	✗	✗	✗
Conta Simples	200K+	✓ Web	✓	✓	✗	✗	✗
ECP Emps	MVP	✓ Web-first	✓	✓	✓	✓ AI	✓ Native

Critical Assumptions

The 4 highest-risk assumptions are all about desirability. If invalidated, the product loses its reason to exist.

ID	Assumption	Opportunity	Risk	Validation Method	Success Criterion
A-01	MEIs truly want to separate PF/PJ expenses (not just say they do)	OPP-07	High	Interview 10 freelancer MEIs	7/10 demonstrate active separation behavior
A-03	MEIs prefer to charge via invoice if it is simple and free	OPP-04	High	Survey 30 MEIs	60%+ would use for 2+ clients/month
A-05	MEIs would make different decisions with cash flow visibility	OPP-10	High	Interview 8 MEIs + mock dashboard	6/8 identify a concrete decision they would change
A-08	MEIs with a PF account at ECP would open a PJ account in the same ecosystem	OPP-01	High	Interest banner in the ecp-digital-bank PF	5%+ click; 30%+ fill out pre-registration

Issues & Open Items

BLOCKING — KR-03 (Toggle PF↔PJ) There is no analytics_events table in the tech_spec to track PF/PJ toggles on the frontend. There is also no definition of “session” in the schema. Cross-app tracking (PJ→PF on port 5173) adds complexity.
Remediation: Add analytics_events table to tech_spec or extend pj_audit_logs with action='profile_switch'.

LOW — KR-02 (Invoices) Installment invoices (type='installment') may inflate the count. Formula must filter parent_invoice_id IS NULL.

LOW — KR-04 (D30 Retention) No explicit PJ login tracking. Using pj_audit_logs as proxy requires passive actions (GET /pj/dashboard) to generate log.

Open Questions

KR-03 requires an analytics_events table not planned in the tech_spec. Include in Phase 03?
Desirability assumptions (A-01, A-03, A-05, A-08) should be validated before development, or do we assume the risk?
The target of 2+ PF/PJ toggles per session may be too aggressive — revisit after first data?

HITL #1 — Approval Decision

Are the OKRs correct? Does the OST contain only opportunities (no solutions)? Do the principles reflect the desired strategy?

✅ Approved — Strategic context validated. Advance to Phase 02 (Product Discovery).
⚠️ Approved with reservations — Context ok, but with specific adjustments before advancing.
❌ Rejected — Return to Product Manager with specific feedback.