Project Charter
Project Charter: {{PROJECT_NAME}}Drop — Fintech Payment App
Project: {{PROJECT_NAME}}Drop — Remittance + QR Payments
Version: {{VERSION}}1.1
Date: {{DATE}}2026-02-08 (updated 2026-02-23)
Author: {{AUTHOR}}John (AI Director)
Status: Draft | In Review | Approved
Reviewers: {{REVIEWERS}}Alem Bašić (CEO)
Document History
| Version |
Date |
Author |
Changes |
| 0.1 |
{{DATE}}2026-02-08 |
{{AUTHOR}}John |
Initial draft |
| 1.0 |
2026-02-13 |
John |
Updated after Phase 0.5 security sprint |
| 1.1 |
2026-02-23 |
John |
Aligned with ROADMAP.md and current pipeline state |
1. Vision & Mission
Vision: {{VISION_STATEMENT}}
Drop becomes Whatthe doesdefault successpayment look like 12 months after launch? What has changedtool for theall businessresidents in Norway who need to send money abroad or users?pay at local businesses — capturing the remittance + QR payments market that no single app currently serves together.
Mission: {{MISSION_STATEMENT}}Build a PSD2 pass-through fintech app (never holding customer money) that offers remittance at 0.5% and QR merchant payments at 1%, powered by Open Banking — cheaper and simpler than every existing alternative.
How does this project deliver the vision? What approach, principles, or methods define delivery?
Strategic Alignment:
Drop Howis doesALAI thisHolding projectAS's alignflagship product, demonstrating AI-native product development from zero to market. It aligns with ALAI's ormission theto client's"build broaderdigital" businessand strategy?generates Referencerecurring therevenue relevantthrough OKRtransaction orfees. businessInnovasjon goal.Norge Oppstartstilskudd (150K NOK) provides initial runway.
2. Scope
2.1 In Scope — Deliverables
| # |
Deliverable |
Description |
Acceptance Criteria Summary |
| D-01 |
{{DELIVERABLE}}Web App (Next.js) |
{{DESCRIPTION}}Full-featured payment app with 10 screens |
{{ACCEPTANCE_CRITERIA}}All pages functional, deployed to staging at drop-staging.fly.dev |
| D-02 |
Remittance Flow |
Send money to 30+ countries at 0.5% fee via PISP |
User can initiate transfer; 6 corridors working (RS, BA, PK, TR, PL, EUR) |
| D-03 |
QR Payment Flow |
Pay merchants by scanning QR code at 1% fee |
Merchant QR generated; customer scan + payment flow functional |
| D-04 |
Open Banking Integration |
AISP (read balance) + PISP (initiate payments) via BaaS partner |
Real bank connection via BankID + selected BaaS provider |
| D-05 |
KYC + BankID Onboarding |
Identity verification, age 18+, Norwegian residency |
Users verified via BankID; KYC status tracked per user |
| D-06 |
Landing Page |
Marketing site at getdrop.no with waitlist |
Live on Vercel; waitlist collecting emails |
| D-07 |
CI/CD + Monitoring |
GitHub Actions pipeline + Fly.io deployment |
All tests green in CI; staging auto-deploys on merge |
2.2 Out of Scope
{{OUT_OF_SCOPE_ITEM_1}}Physical card issuance (feature-flagged, requires card partner){{OUT_OF_SCOPE_ITEM_2}}Wallet / balance holding (Drop is pass-through — no float){{OUT_OF_SCOPE_ITEM_3}}Crypto payments or asset trading- Lending or credit products
- Under-18 user support (requires separate legal review)
- White-label product for other companies (Phase 4 roadmap item)
- Real money movement in MVP demo (mock Open Banking until licence obtained)
- Content creation, translations beyond Norwegian/English
2.3 Assumptions
| # |
Assumption |
Risk if False |
Owner to Validate |
| A-01 |
{{ASSUMPTION}}BaaS partner (Swan or SpareBank1) confirms by Phase 2 |
{{RISK}}Phase 2 blocked indefinitely |
{{OWNER}}Alem |
| A-02 |
Finanstilsynet PISP/AISP registration process takes ~3 months |
Launch delayed |
Alem + Legal advisor |
| A-03 |
Users have Norwegian BankID and +47 phone |
Onboarding conversion low |
Alem (user research) |
| A-04 |
Open Banking APIs from BaaS provider are stable |
Integration rework required |
John |
| A-05 |
Innovasjon Norge grant (150K NOK) is approved |
Cash flow gap before revenue |
Alem |
2.4 Constraints
| # |
Constraint |
Category |
Impact |
| C-01 |
{{CONSTRAINT}}Drop NEVER holds customer money (PSD2 pass-through model) |
Technical / Legal / Budget / TimeRegulatory |
{{IMPACT}}Architecture must use AISP/PISP only |
| C-02 |
Minimum user age: 18 (BankID DOB validation) |
Legal |
Onboarding must validate DOB |
| C-03 |
NEVER use word "banking" without licence disclaimer |
Legal |
All copy must be reviewed |
| C-04 |
Norwegian BankID required for onboarding |
Technical |
Locks market to Norway initially |
| C-05 |
Budget: ~250K NOK total (150K Innovasjon Norge + bootstrap) |
Financial |
AI-first development to minimise costs |
| C-06 |
PCI-DSS: NEVER store or expose full card numbers/CVV |
Security |
Cards feature requires tokenisation partner |
3. Stakeholder Register
| ID |
Name |
Organization |
Role |
Interest |
Influence |
Engagement Strategy |
Contact |
| S-01 |
{{NAME}}Alem Bašić |
{{ORG}}ALAI Holding AS |
CEO / Sponsor |
{{INTEREST}}Strategic success, revenue, brand |
High |
SteeringDirect committeesessions, monthlyall major decisions |
{{EMAIL}}[email protected] |
| S-02 |
John |
ALAI Holding AS |
AI Director / Product Owner |
Technical delivery, product quality |
High |
SprintDaily reviews,async, dailyall sprint reviews |
— |
| S-03 |
SpareBank1 contact |
SpareBank1 |
EndBanking UserPartner RepCandidate |
Partnership revenue, market expansion |
MediumHigh |
UATQuarterly sessionsmeetings, pitch materials |
Via Alem |
| S-04 |
Swan (BaaS) |
Swan.io |
BaaS Provider Candidate |
API adoption, merchant fees |
Medium |
Technical Leadintegration discussions |
| Via High |
Daily standup |
John |
| S-05 |
Finanstilsynet |
Norwegian FSA |
Finance/LegalRegulator |
PSD2 compliance, consumer protection |
High |
Formal registration process |
Via legal advisor |
| S-06 |
Early users (waitlist) |
— |
End Users |
Cheap remittance, easy QR payments |
Low |
Waitlist comms, beta invitations |
[email protected] |
| S-07 |
Local merchants |
Oslo area |
Merchant Users |
Lower fees than Vipps, easy setup |
Medium |
MonthlyDoor-to-door reportsonboarding |
Alem |
Key Decision Makers:
- Final scope decisions:
{{DECISION_MAKER}}Alem Bašić (CEO)
- Technical architecture approval:
{{TECH_APPROVER}}John (AI Director)
- Budget approval:
{{BUDGET_APPROVER}}Alem Bašić
- Contract/legal:
{{LEGAL_APPROVER}}Alem Bašić + external legal advisor
4. Budget Summary
| Line Item |
Amount (NOK) |
% of Total |
Notes |
| Development (AI-first) |
{{AMOUNT}}10,000 |
4% |
Claude Code + tooling costs |
DesignOpen Banking integration (PSD2) |
{{AMOUNT}}15,000 |
6% |
BaaS setup + API costs |
InfrastructureLegal /+ Hostingcompliance setup |
{{AMOUNT}}50,000 |
20% |
Finanstilsynet registration, legal review |
Third-partyMarketing licenses / APIslaunch |
{{AMOUNT}}100,000 |
40% |
Social media, local merchant onboarding |
TestingQR /stickers QA+ merchant kits |
{{AMOUNT}}20,000 |
8% |
Physical materials |
ProjectBuffer Management/ contingency |
{{AMOUNT}}55,000 |
22% |
| Unexpected
Subtotal |
{{SUBTOTAL}} |
100% |
|
Contingency Reserve (15%) |
{{CONTINGENCY}} |
|
For approved change requestscosts |
| Total Budget |
{{TOTAL}}250,000 |
100% |
|
Payment Schedule: Internal project — Innovasjon Norge Oppstartstilskudd (~150K NOK) + bootstrapped by ALAI.
| Milestone |
% |
Amount (NOK) |
Due DateSource |
ContractPhase signing0.5 completion (security hardening) |
50%0 (AI cost only) |
{{AMOUNT}} | ALAI {{DATE}}bootstrap |
MVPPhase delivery1 (demo app) |
25%~25,000 |
{{AMOUNT}} | Innovasjon {{DATE}}Norge |
FinalPhase delivery2 (bank integration) |
~125,000 |
Innovasjon Norge |
| Phase 3 (launch) |
~100,000 |
Revenue + UAT sign-off |
25% |
{{AMOUNT}} |
{{DATE}}grant |
5. Timeline & Milestones
| # |
Milestone |
Target Date |
Gate Condition |
Owner |
| M-01 |
ProjectPhase Kick-off0 — Foundation |
{{DATE}}2026-02-08 |
CharterLanding approved,page teamlive, onboardedbrand done, pipeline test passed |
PMJohn |
| M-02 |
RequirementsPhase Complete0.5 — MVP Hardening |
{{DATE}}2026-02-20 |
BRD/FRSSecurity approvedaudit bypassed, PO217 +tests clientgreen, staging live |
BAJohn |
| M-03 |
DesignPhase Approved1 — Demo App |
{{DATE}}2026-03-15 |
AllFull mockups10-screen signedapp offfunctional, investor-ready demo |
DesignerJohn |
| M-04 |
MVPBaaS /Partner Alpha ReleaseDecision |
{{DATE}}2026-03-01 |
CoreSpareBank1 featuresanswer functional,or deployedSwan to stagingsigned |
Tech LeadAlem |
| M-05 |
BetaPhase Release2 — Banking Integration |
{{DATE}}2026-04-30 |
AllReal featuresBankID, complete,AISP, regressionPISP testsworking passwith 10 beta users |
QAJohn |
| M-06 |
UATFinanstilsynet CompleteRegistration |
{{DATE}}2026-05-15 |
UATPISP/AISP sign-offlicence document signedsubmitted |
PMAlem + Legal |
| M-07 |
Phase 3 — Production Launch |
{{DATE}}2026-06-15 |
Go-liveApp checklistStore passed,+ monitoringPlay activeStore live, 200 merchants onboarded |
DevOpsJohn + Alem |
| M-08 |
Post-launch HandoverReview |
{{DATE}}2026-07-15 |
Documentation1,000 delivered,users, supportmonitoring transitionactive, external pentest done |
PMJohn |
Gantt Diagram (placeholder):Diagram:
gantt
title {{PROJECT_NAME}}Drop — Project Timeline
dateFormat YYYY-MM-DD
section PlanningFoundation
ProjectPhase Kick-off0 Foundation :done, m1,p0, {{START_DATE}},2026-02-08, 3d7d
RequirementsPhase Gathering0.5 Hardening :active,done, req,p05, after m1,p0, 14d
section DesignDemo
UI/UXPhase Design1 Demo App :des,active, afterp1, req,2026-02-20, 14d28d
Designsection ReviewIntegration
BaaS Partner Decision :milestone, baas, 2026-03-01, 1d
Phase 2 Banking :p2, after des,p1, 56d
Finanstilsynet Filing :milestone, reg, 2026-05-15, 1d
section DevelopmentLaunch
Sprint 1 :s1, after des, 14d
Sprint 2 :s2, after s1, 14d
SprintPhase 3 :s3, after s2, 14d
section Testing & Launch
UATProduction :uat,p3, after2026-05-15, s3,30d
7dGo Production LaunchLive :milestone, afterlive, uat,2026-06-15, 1d
6. Success Criteria & KPIs
| # |
Success Criterion |
KPI / Metric |
Target |
Measurement Method |
Evaluation Point |
| SC-01 |
{{CRITERION}}Revenue generation |
{{KPI}}Monthly Recurring Revenue |
{{TARGET}}130,000 NOK/month |
{{METHOD}}Transaction logs |
{{WHEN}}Month 12 post-launch |
| SC-02 |
User acquisition |
Registered users |
3,000 |
App analytics |
Month 12 post-launch |
| SC-03 |
Merchant adoption |
Onboarded merchants |
200 |
Merchant dashboard |
Month 12 post-launch |
| SC-04 |
System performance |
PageAPI loadresponse time p95 |
< 2 seconds (p95)500ms |
Lighthouse / monitoringMonitoring |
Launch + 30 days |
SC-0305 |
UserSecurity adoptionposture |
ActiveSecurity usersscore |
{{TARGET}}≥ in 90 days80/100 |
AnalyticsSecurity dashboardaudit |
90Pre-launch |
days
| SC-06 |
Transaction reliability |
Payment success rate |
≥ 99% |
Transaction logs |
Ongoing post-launch |
SC-0407 |
QualityFee competitiveness |
BugRemittance ratefee vs Wise |
<0.5% 5vs critical bugs post-launch0.7-1.5% |
IssueCompetitor trackermonitoring |
30 days post-launch |
SC-05 |
Client satisfaction |
NPS score |
≥ 8/10 |
Post-launch survey |
60 days post-launchOngoing |
7. Dependencies
| # |
Dependency |
Type |
Impact if Delayed |
Owner |
Target Date |
Status |
| DEP-01 |
{{DEPENDENCY}}BaaS provider (Swan or SpareBank1) |
Internal / External / Client |
{{IMPACT}}Phase 2+ blocked |
{{OWNER}}Alem |
{{DATE}}2026-03-01 |
PendingSpareBank1 pitched; awaiting |
| DEP-02 |
Finanstilsynet PISP/AISP registration |
External / Regulatory |
Real payments blocked |
Alem + Legal |
2026-05-15 |
Not started |
| DEP-03 |
BankID integration via BaaS |
External |
SCA/onboarding blocked |
John |
After BaaS selected |
Pending BaaS |
| DEP-04 |
KYC provider (Sumsub or partner KYC) |
External |
AML compliance blocked |
John |
After BaaS selected |
Mock in place |
| DEP-05 |
Phase 0.5 security hardening |
Internal |
Phase 1 blocked |
John |
2026-02-20 |
In progress |
8. Governance Model
8.1 Decision-Making Authority
| Decision Category |
Authority |
Must Consult |
Must Inform |
| Scope changes |
POAlem +(CEO) |
John |
TechAll Lead, PM |
Client, Alemstakeholders |
| Architecture decisions |
John (AI Director) |
Tech Lead agents |
Developer team |
PM, JohnAlem |
| Budget changes > 10% |
Alem |
John, PMJohn |
Client— |
| Release go/no-go |
Tech Lead + PM |
QA, DevOps |
John, Client |
Team changes |
John |
PMQA agents |
Alem |
ContractPartner/legal amendmentsdecisions |
Alem |
John + Legal advisor |
Client— |
| Team / agent changes |
John |
— |
Alem |
8.2 Change Control Process Summary
- Request: Any stakeholder
submitsraises achange Changerequest Request (CR) using thevia change-request.md template
- Impact Analysis:
PMJohn + Tech Lead assessassesses scope, timeline, budget, and risk impactbudget within 3 business days
- Decision:
POAlem + John approve/rejectapproves/rejects within 2 business days of impact analysis
- Budget changes > 10%: Require Alem explicit approval via session
- Implementation: Approved
CRschanges are logged, prioritizedlogged in backlog, andcomms/decisions/, scheduled in roadmap
- Communication: All stakeholders notified
of approved/rejected CRs within 24 hours
8.3 Escalation Hierarchy
L1: Team Member → Tech Lead (response: 4 hours)
L2: Tech Lead → PM (response: 8 hours)
L3: PMAgent → John (response: 4 hours)
L4:L2: John → Alem (response: 24 hours — strategic/financial only)
L3: Alem → External advisor (legal/regulatory only)
9. Team & Roles
| Role |
Agent / Person |
Responsibilities |
Availability |
| Project Sponsor / CEO |
{{NAME}}Alem Bašić |
Strategic direction, finalpartnerships, budget approvals, budgetregulatory |
AsPart-time needed(decisions + partnerships) |
| AI Director |
John (Claude Opus) |
Delivery accountability, architecture, agent coordination |
Full-time |
ProjectDeveloper Manager/ Builder |
{{AGENT}} | Builder Coordination,(Claude reporting, risk, stakeholder comms |
Full-time |
Business Analyst |
{{AGENT}} |
Requirements, acceptance criteria, documentation |
Full-time |
Tech Lead |
{{AGENT}} |
Architecture, code review, technical decisions |
Full-time |
Developer(s) |
{{AGENT}}Sonnet) |
Feature implementationimplementation, API routes, frontend pages |
Full-time |
Designer |
{{AGENT}} |
UI/UX, design system, assets |
Part-timePer-task |
QA Engineer/ Validator |
{{AGENT}}Validator (Claude Sonnet) |
TestTesting, planning,validation, execution,code sign-offreview |
Full-timePer-task |
DevOpsSecurity |
{{AGENT}}Security agent (Claude) |
Infrastructure,Threat CI/CD,modelling, deploymentaudit, compliance |
Part-timePer-sprint |
| Legal |
Legal agent (Claude) |
Regulatory review, document drafting |
As needed |
| Finance |
Finance agent (Claude) |
Budget analysis, projections |
As needed |
10. Risk Summary
| # |
Risk |
Probability |
Impact |
Mitigation |
| R-01 |
{{RISK}}Banking partner / BaaS not secured in time |
H/M/LHigh |
H/M/LHigh |
{{MITIGATION}}Multi-provider approach; Swan as backup to SpareBank1 |
| R-02 |
Finanstilsynet registration delayed |
Medium |
High |
Start process early; operate under bank partner licence initially |
| R-03 |
Security breach before production hardening |
Low |
Critical |
Security audit completed; 8 critical fixes tracked; no real money in MVP |
| R-04 |
Vipps launches remittance product |
Medium |
High |
Already ahead in market; community trust and lower fees are moat |
| R-05 |
Slow merchant adoption |
Medium |
Medium |
Door-to-door in local communities; 0% fee for first 3 months |
Full risk register: [risk-register.md](risk-register.md)
Approval
| Role |
Name |
Date |
Signature |
| Author |
John (AI Director) |
2026-02-08 |
Approved (AI) |
| Reviewer |
John (AI Director) |
2026-02-23 |
Reviewed (AI) |
| AI Director (John) |
John |
2026-02-08 |
Approved |
| Project Sponsor |
Alem Bašić |
2026-02-08 |
Approved |
CEO (Alem) |
Alem Bašić |
2026-02-08 |
|
Client Representative |
|
|
Approved |
