ASTERANOVA
Prepared for  Digital Bank
Program Estimate · Digital Bank Build

From Idea to a Live Digital Bank

A four-phase delivery program — Phase 0 discovery, Pilot, Launch, and Expansion — engineered end-to-end by Astera Nova: architecture, integrations, product, compliance, and operations, built for an online-only bank from day one.

10,138
Total Hours
$942,790
Total Investment
16
Months, M1–M16
4
Phases
Program at a Glance

Four Phases, One Continuous Build

Headline scope and investment per phase. Full objective, prerequisites, assumptions, deliverables, and team breakdown for each phase are detailed further down the page.

0

Discovery & Foundation

M1–3
1,952
Hours
$195,100
Cost
19.1% of program
1

Pilot

M4–8
3,432
Hours
$314,140
Cost
33.9% of program
2

Launch

M9–13
3,274
Hours
$299,510
Cost
32.3% of program
3

Expansion

M14–16
1,496
Hours
$135,080
Cost
14.8% of program
Timeline & Critical Path

50 Work Packages, One 16-Month Critical Path

Every bar below is a real work package with its own start and end month — nothing runs full-width. 19 of the 50 bars form the critical chain that actually sets the 16-month duration; the other 31 run alongside with real slack. The 21 arrows shown are only genuine hard blockers (X literally can't start until Y is done) — 12 documented relationships, some fanning out to more than one successor; dashed gates pin the 7 sync points to the exact month they gate.

Swipe to see the full 16-month timeline
Critical-path bar (19 of 50 — sets the 16-month end date)
Supporting bar (real slack, doesn't extend the timeline)
Milestone (Go-Live, M13)
Dependency (predecessor → successor)
Sync-point / blocker gate, pinned to its month
Phase 0
Pilot
Launch
Expansion
M1
M2
M3
M4
M5
M6
M7
M8
M9
M10
M11
M12
M13
M14
M15
M16
G2
G1·G3·G7
G4
G5·G6
BEBackend Engineer
BABusiness Analyst
SASolution Architect
QAQA / Test
DevOpsDevOps
DEData Engineer
FEFrontend
PMProgram Mgmt
SECSecurity
COMPCompliance
MLEML Engineer
SA1
SA2
AUDIT
REG
VENDOR
ENV
PM1
FEAS
QA1
SEC1
CLOSE
SA1
ENV
CONNECT
PRODUCT
SCORE
OPS
UI
DATA
COMP
SEC
PLAN
E2E
PM
DOCS
DR
PROD-ENV
HARDEN
CATALOG
EXTEND
ANALYTICS
UI
E2E
SEC-TEST
PENTEST
DR/BACKUP
SIGNOFF
PM
DOCS
PLAN
BUREAU-2
PRODUCTS
A/B
DATA
SCALE
SEC
AUDIT
REGRESS
PM

Critical path (highlighted): SA architecture (P0-SA1/SA2) → Pilot connector & product build (PL-INT1/PROD1) → Pilot UAT (PL-QA2, Gate 4) → Launch hardening & catalog (LA-INT1/PROD1) → Launch E2E (LA-QA1/QA2) → pentest/compliance/DR converge (LA-SEC1, LA-COMP1, LA-DEVOPS2, Gates 5&6) → Cutover (M13) → Expansion build & test (EX-SA1/PROD1/QA1). 19 bars, 8 phase-to-phase serial links — this is what the 16 months actually depends on; the other 31 bars run in parallel with slack.

1

Legacy-Core API confirmation. SA resolves REST-vs-batch reality for GL/wallet APIs and secures sandbox access.Gate 1 · M3 → blocks Pilot connector (PL-INT1) at M4

2

Bureau/score-provider selection. Vendor (CIC/FinScore/other) chosen, sandbox access confirmed for Pilot integration.Gate 2 · M2 → blocks Pilot bureau connector & scorecard (PL-INT1, PL-CRED1) at M5

3

Bank KYC/AML ownership confirmation. Bank confirms it owns KYC/AML sign-off and the API shape it exposes.Gate 3 · M3 → blocks Pilot compliance controls (PL-COMP1) at M5

4

Pilot UAT sign-off. Bank-coordinated UAT complete, retrospective run, formal go/no-go recorded.Gate 4 · M8 → blocks Launch hardening/build (LA-INT1, LA-PROD1, LA-DEVOPS1) at M9

5

Compliance sign-off + pentest remediation. Production sign-off documented; pentest findings closed and verified.Gate 5 · M13 → blocks Production Cutover (LA-CUTOVER) at M13

6

DR/production-readiness verification. DR/backup infrastructure tested; failover/DR architecture verified against RTO/RPO.Gate 6 · M12 → blocks Production Cutover (LA-CUTOVER) at M13

7

Historical-data/ML scope decision. ~1,000-loan portfolio confirmed insufficient for production ML.Gate 7 · M3 → locks Launch scoring rules-based & Expansion ML exploratory-only

Phase Detail · 1 of 4

Phase 0 — Discovery & Foundation

0

Discovery & Foundation

M1–3
$194,060
1,936 hours

Establish the architectural, regulatory, and delivery foundation before any product code is built. Phase 0 answers the questions that determine Pilot's design: what the bank's legacy core/GL/wallet can actually expose via API, what BSP/CIC/AMLA/Data-Privacy rules constrain product and data design, and what the reference architecture, tech stack, and environments look like for all 9 components. No build — design, audit, and planning only.

Prerequisites

  • Signed engagement / Phase 0 statement of work.
  • Bank grants read access to product policies, process documentation, and org/role structure.
  • Bank grants (or commits to grant) technical access for a legacy-core/GL/wallet API review.
  • Bank identifies its compliance/legal counterpart for BSP/AMLA/Data-Privacy scoping.
  • Initial candidate list of bureau/score providers (CIC, FinScore, or alternatives) available.
  • Program sponsor and steering-committee contacts named on the bank side.

Assumptions

  • Legacy core's API maturity (REST vs. batch-only) is unconfirmed — carried as an explicit integration-layer risk.
  • Bank provides access to current processes/systems for the audits.
  • ~1,000 historical loans assumed insufficient for production ML — informs a rules-first scoring architecture.
  • BSP AI/ML guidance applicability is confirmed later, not finalized in Phase 0.
  • No physical-branch design work — online-only bank, no branch/teller workflows.

Deliverables & Result

  • Reference + integration architecture for all 9 components; tech-stack decision, environments/DR, ADR set.
  • Legacy-core API capability assessment — the single highest-risk input to Pilot planning.
  • Regulatory pack: BSP, AMLA, CIC, Data Privacy Act (NPC), mapped to product/process impact.
  • Detailed design + pilot backlog for each of the 9 components.
  • Program charter, roadmap, risk/issue tracking; discovery DevOps environment; top-level threat model.
  • Result: validated architecture, a scoped Pilot backlog, and documented regulatory constraints — ready to commit to a fixed-scope Pilot.
RoleWhat they do in Phase 0HoursCost
SALegacy-core API assessment (REST vs. batch) — program risk #1, gates Pilot's connector build. Scoring architecture that has to work rules-first, no ML at launch. RBAC/maker-checker model for the confirmed 10-role + 4-API-actor surface.724$94,120
BABureau/score-provider vendor audit (CIC vs. FinScore vs. other) — kicks off sandbox access, program risk #2. Compliance traceability matrix that draws the exact line between what we own and what the bank exposes via API.500$37,500
COMPAMLA/KYC analysis scoped to the bank's API contract, not an AML build — the "bank owns compliance operations" boundary the whole estimate depends on. AI/ML-in-scoring read stays light since launch scoring is rules-based.280$22,400
DevOpsDiscovery environment, IaC and CI skeleton — routine scaffolding, low risk this phase; sets the baseline Pilot's real environments build on.112$10,640
DELegacy-core/GL/wallet inventory with hands-on API probing, not just document review — direct input to SA's #1-risk API assessment.96$8,640
PMProgram charter and Phase 0 roadmap — sets the cadence for a 16-month, four-phase program with a lean team.88$7,920
SECThreat modeling raises the remote-identity-proofing / account-takeover bar from day one — online-only bank, no branch fallback to catch a bad actor.64$7,040
QATest-strategy and automation-tooling draft, scoped to a thin UI surface — the decision Pilot's QA either reuses or has to redo.40$2,600
MLEHistorical-data/scoring feasibility on ~1,000 loans — the finding that locks Launch scoring rules-based rather than ML.32$3,200
Phase 0 Subtotal1,952 h$195,100
Phase Detail · 2 of 4

Pilot — One Deposit + One Loan Product, End-to-End

1

Pilot

M4–8
$314,140
3,432 hours

Build one thin, fully end-to-end slice — one term-deposit product and one unsecured-loan product — through every one of the 9 components: origination, scoring (rules-based), servicing, collections, operations/RBAC, compliance controls, and the core/GL/bureau/KYC/wallet integrations. Prove the architecture against a real bank sandbox before committing to full-scale Launch build.

Prerequisites

  • Phase 0 architecture, component designs, and pilot backlogs signed off.
  • Bank confirms and provisions sandbox/API access for core banking, GL, e-wallet, and KYC provider.
  • Bureau/score provider sandbox or API access available for pilot integration.
  • One deposit and one loan product's parameters confirmed by the bank for pilot configuration.
  • Dev/test/staging environments provisioned, carried from Phase 0 scaffold.
  • Bank names the UAT participants and pilot go/no-go decision-maker.

Assumptions

  • Core banking exposes a usable API, not only batch files — explicit risk if untrue.
  • GL API exists on the legacy core for posting deposit/loan entries.
  • Bureau API access is confirmed available for pilot scope, not batch-only.
  • Pilot builds consume the bank's KYC/AML result rather than building controls in-house.
  • Scoring is a rules-based champion model with minimal champion-challenger scaffolding — no ML build.
  • RBAC scoped for the full 10-role actor model even at pilot scale.

Deliverables & Result

  • Working core-banking, GL, e-wallet, KYC, and bureau connectors with reconciliation-aware design.
  • One live deposit product and one live loan product running end-to-end.
  • Rules-based scorecard wired to a decision-engine service; minimal champion-challenger infra.
  • Servicing & collections: payment schedule/application, arrears calc, bucket 1–3 segmentation.
  • Ops Admin: RBAC, maker-checker, audit-trail logging; basic compliance controls + draft CIC reporting.
  • Result: a bank-validated, live pilot proving the full application-to-collections lifecycle — the evidence base for Launch.
RoleWhat they do in PilotHoursCost
BECore-banking/GL/bureau connector build against an API shape only confirmed at the Gate 1/2 handoff — the single biggest execution risk in the phase. RBAC + maker-checker across the full 10-role model, not a simplified pilot stand-in. Reconciliation-aware GL posting, not just "post a transaction."1,568$141,120
DevOpsFull dev/test/staging + CI/CD stood up before bank sandbox access is guaranteed — a sequencing risk if that access slips.352$33,440
FEMaker-checker approval queue UI — the one screen tightly coupled to backend RBAC semantics, not a generic CRUD form.340$28,900
QABuilds the one test-automation framework the program reuses through Launch and Expansion, not a pilot-only throwaway — targeted at the few real interfaces and the core connector/contract flows, not broad manual UI passes.120$7,800
PMCoordinates the bank stakeholders and runs the pilot retrospective that directly feeds the Launch plan.200$18,000
DETest-data prep for interest day-count logic has to mirror the legacy core's actual accrual convention — unconfirmed until Gate 1 closes.180$16,200
SAAPI contracts between components — the artifact that turns Phase 0's architecture assumptions into commitments Pilot code is actually built against.176$22,880
BADocuments scoring business rules — the record of exactly which decisions are rules-based today, in case the ML add-on gets greenlit later.168$12,600
MLERules-based champion scorecard, deliberately not an ML model. The real work is building drift/PSI monitoring for a system with no live production data yet.144$14,400
SECFirst threat model against live connectors and real secrets — still shaped by the no-branch, remote-only posture.136$14,960
COMPBasic KYC/AML controls scoped strictly as bank-API consumption — the calibration boundary made concrete for the first time, not a parallel control build.48$3,840
Pilot Subtotal3,432 h$314,140
Phase Detail · 3 of 4

Launch — Harden, Scale, Go-Live

2

Launch

M9–13
$299,510
3,274 hours

Take the validated pilot to full production coverage across all 9 components: harden every connector and calculation path, extend the product catalog and rules to the full initial launch scope, complete regulatory reporting and compliance sign-off, and prove production readiness through full end-to-end testing, load testing, and a pre-launch pentest.

Prerequisites

  • Pilot UAT sign-off from the bank and a formal go/no-go decision to proceed.
  • Full launch-scope product parameters confirmed by the bank.
  • Production-grade environment and DR requirements agreed (uptime, RTO/RPO).
  • Compliance sign-off process and criteria agreed with the bank's compliance/legal function.
  • Bank commits resources for launch UAT coordination and training participation.
  • CIC/BSP production reporting formats and submission channels confirmed.

Assumptions

  • CIC API/format for production submission remains stable and available as scoped earlier.
  • Bank continues to own AML monitoring and sign-off; Launch consumes/alerts on AML output, doesn't build a monitoring engine.
  • Full 9-component testing reuses the Pilot-built automation framework rather than authoring it from scratch, and stays weighted toward automated critical-flow/contract checks over manual UI passes — the bank's app has few interfaces, so QA doesn't scale 1:1 with catalog size.
  • Pentest scoped as internal coordination + remediation; external execution cost is a separate line item.
  • Production environment must support blue-green/canary deployment and rollback from day one.

Deliverables & Result

  • Hardened connectors (retry, idempotency, reconciliation) across core, GL, bureau, KYC, e-wallet.
  • Full launch-scope product catalog: extended accrual methods, eligibility/fraud rules, servicing/restructuring.
  • Production-ready BSP/CIC reporting, compliance sign-off docs, SoD-matrix sign-off.
  • Production-grade environments (DR, autoscaling, observability), full E2E + load testing, pre-launch pentest remediated.
  • Full documentation, production runbooks, bank team training, handover plan.
  • Result: a production-hardened system covering the full initial catalog, signed off by compliance and security, ready for go-live.
RoleWhat they do in LaunchHoursCost
BEHardens connectors for retry/idempotency/reconciliation — the gap between a pilot integration and a production one. Extends eligibility/affordability/fraud rules to the full catalog without re-architecting Pilot's single-product logic.888$79,920
QAAutomated E2E across the 9 components' contracts/critical flows, not exhaustive manual UI regression — the thin interface surface is exactly why this stays lean. Load/performance testing holds (non-negotiable for a live-money system). Security testing runs jointly with SEC, not sequentially after.150$9,750
DevOpsDR/backup build & test is a hard release gate (Gate 6) — parallel to the pentest and compliance sign-off, all three have to close together before cutover.416$39,520
BAFull documentation and bank-team training — the handover artifact that determines how much the bank can self-serve after go-live.328$24,600
SECPre-launch pentest + remediation is a hard release gate (Gate 5) — findings block cutover, this isn't a checklist review.304$33,440
PMRuns cross-component dependency management across all 9 components converging on one cutover date.288$25,920
DEReconciliation reports against connectors still being hardened in parallel — the pipeline can't fully stabilize until connector hardening lands.244$21,960
FEExtends the admin UI to the full parameter set — mostly scale, not new risk.224$19,040
SAFailover/DR strategy design — the architecture half of the Gate 6 DR-readiness gate.168$21,840
COMPProduction compliance sign-off converges with pentest remediation and DR verification at the same two-week cutover window — three independent tracks landing together.144$11,520
MLEChallenger-model stability monitoring — first time the scorecard runs unattended at production volume.120$12,000
Launch Subtotal3,274 h$299,510
Phase Detail · 4 of 4

Expansion — First Scale-Out Increment

3

Expansion

M14–16
$135,080
1,496 hours

Deliver the first post-launch increment: 2–3 additional deposit variants, 1–2 additional unsecured-loan products, expanded eligibility/affordability data sources, promo mechanics, and the first collections risk-scoring pilot — while validating the platform scales cleanly beyond the initial launch catalog. Explicitly scoped as the first increment, not an open-ended roadmap.

Prerequisites

  • Launch go-live completed and stable in production.
  • Bank confirms the specific product set for the first expansion wave (assumed 2–3 deposits, 1–2 loans).
  • Decision on a second credit-bureau provider, if pursued — currently unconfirmed.
  • Decision on corporate SSO/AD integration for the admin panel — currently unconfirmed.
  • Any additional payment-rail integrations finalized in scope — currently unconfirmed.

Assumptions

  • Scope is bounded to a first increment (2–3 products); further waves are out of scope for this estimate.
  • Optional ML-based scoring uplift is not in this phase's hours — a separately-ballparked, opt-in add-on.
  • Historical/production data volume is still assumed limited — ML-adjacent work here is exploratory groundwork only.
  • Second bureau, SSO/AD integration, and additional payment rails are each unconfirmed-scope items.

Deliverables & Result

  • Additional deposit and loan products live, with expanded affordability models and rate-tier flexibility.
  • Promo/discount mechanics with configuration UI, expanded rate simulation tooling.
  • Collections support for new products, expanded restructuring scenarios, first risk-score collections pilot.
  • Optional second bureau connector and payment-rail integration (pending bank confirmation).
  • Expanded RBAC/delegation, expanded regulatory reporting (BSP FSF/perimeter), first periodic control audit.
  • Result: a validated pattern for adding new products to the live platform, plus groundwork for an optional future ML scoring add-on.
RoleWhat they do in ExpansionHoursCost
BEOptional second bureau connector and SSO/AD integration — both explicitly unconfirmed-scope items, not committed builds; scope depends on bank decisions still open.612$55,080
BANew eligibility rules and promo-campaign design for the confirmed 2–3 deposit / 1–2 loan first wave.168$12,600
DEFeature-engineering pipeline groundwork for the eventual ML add-on — not the model itself, just the plumbing.144$12,960
MLEChampion-vs-ML-challenger A/B groundwork — exploratory only. This is the seed of the separately-priced ML add-on, not a production model.144$14,400
FEPromo-configuration UI — routine extension of the existing admin UI pattern.96$8,160
QARegression pass reuses Launch's full suite rather than rebuilding — the same reuse pattern behind the QA-hours recalculation above.40$2,600
DevOpsScales infrastructure for the first wave — routine, no new architecture.80$7,600
SAArchitecture for the first wave of additional products, reviewed against the production baseline set at Launch.64$8,320
COMPFirst periodic control audit — the compliance cadence shifts from one-off sign-off to ongoing review.60$4,800
PMManages expansion-wave dependencies — smallest PM line in the program, reflecting one confirmed wave, not an open-ended roadmap.56$5,040
SECSecurity review scoped to the new components only — not a full re-pentest.32$3,520
Expansion Subtotal1,496 h$135,080

Optional ML scoring add-on (not in the above hours): a dedicated, production-grade ML credit-scoring uplift — model build, MLOps, governance, bias/fair-lending testing — is available as a separate opt-in track, top-of-market ballparked at 500–700h, additive to the exploratory groundwork above.

Role Glossary & Program Roll-Up

Eleven Roles, One Program

Every role's program-wide mandate, and its total hours/cost summed across all four phases — the same 10,138 h / $942,790 reconciled from a different angle: by role instead of by phase.

Program Roll-Up
10,138 h · $942,790

Blended rate $92.99/h. Rates: SA $130 · BA $75 · BE $90 · FE $85 · DE $90 · MLE $100 · QA $65 · DevOps $95 · PM $90 · COMP $80 · SEC $110.

RoleProgram-Wide MandateTotal HoursTotal Cost
BEBackend EngineerThe largest role on the program. Owns every server-side build: product/origination/servicing logic, all core-banking/GL/bureau/KYC/wallet connectors, the scoring decision engine, RBAC/maker-checker, and regulatory report generation — from Pilot's single-product slice through Launch's full catalog and Expansion's new products.3,068 h$276,120
BABusiness AnalystThe process and requirements backbone: audits current processes, designs traceability matrices and product-policy models, writes documentation/runbooks/training, configures product parameters — active every phase from discovery through expansion design.1,164 h$87,300
SASolution ArchitectOwns the reference and integration architecture end to end — heaviest in Phase 0 (foundational design) and Launch (production hardening/DR), lighter touch in Pilot (API contracts) and Expansion (scaling for new products).1,132 h$147,160
QAQuality AssuranceOwns all testing beyond unit tests, scoped tightly for a thin-interface product: one automation framework built once and reused every phase, critical-flow/contract checks over broad manual UI regression, load/performance and security testing held firm as hard release gates.350 h$22,750
DevOpsDevOps EngineerBuilds and hardens platform infrastructure: environments, IaC, CI/CD, observability, DR — scaling from a discovery sandbox in Phase 0 to production-grade blue-green infrastructure at Launch.960 h$91,200
DEData EngineerBuilds the data pipeline and analytics layer: integration/data-source audits in Phase 0, transactional/analytics pipelines in Pilot, portfolio analytics and reconciliation at Launch, ML-adjacent feature-pipeline groundwork in Expansion.664 h$59,760
FEFrontend EngineerBuilds every admin and operator-facing UI: product/role administration, application processing, collections dashboards, business dashboards — extended in Launch and Expansion for the full product set.660 h$56,100
PMProgram ManagerRuns program governance end to end: mobilization/charter in Phase 0, pilot management in Pilot, full launch-program and cross-component dependency management at Launch, expansion-wave planning.632 h$56,880
SECSecurity EngineerOwns the security posture: top-level threat modeling/SDLC standards in Phase 0, pilot secure-coding review, pre-launch pentest and remediation plus infra hardening at Launch, expansion component security review.536 h$58,960
COMPComplianceOwns regulatory analysis and sign-off support: BSP/AMLA/CIC/Data-Privacy analysis in Phase 0, basic product controls in Pilot, production compliance sign-off and disclosure validation at Launch, periodic control audits in Expansion.532 h$42,560
MLEML EngineerScoped light and rules-first per program decision: data/feasibility assessment in Phase 0, rules-based champion scorecard in Pilot, scorecard extension/monitoring at Launch, exploratory ML/A-B groundwork in Expansion — a production ML uplift remains a separate opt-in track.440 h$44,000
Program Total10,138 h$942,790
Assumptions & Scope Notes

Program-Wide Notes

Rates used throughout: SA $130/h · BA $75/h · BE $90/h · FE $85/h · DE $90/h · MLE $100/h · QA $65/h · DevOps $95/h · PM $90/h · COMP $80/h · SEC $110/h.