Northwind Capital

Identify the failure mode before the sprint begins.

Core argumentWeek 0 prevents the programme from wasting bank, mentor, and founder time.

Operational design

• Name the likely failure mode.
• Name the weakest score dimension.
• List missing evidence and data-risk exposure.
• Name buyer, UK, and pilot-scope risks.
• Weakest dimension: Integration Clarity at 22/100.
• Likely failure mode: First pilot ingests live customer data — high approval bar.

Actions

• Pre-mortem gap 1: First pilot ingests live customer data — high approval bar.
• Pre-mortem gap 2: Pilot scope is not bounded — customer/production exposure will slow approval.
• Pre-mortem gap 3: No exit / portability posture — UK operational-resilience gap.

Translate the pitch into a bank-owned workflow.

Core argumentA fintech is not bankable until it maps to a bank-owned workflow.

Operational design

• Chosen workflow: SMB working-capital origination via partner vertical SaaS.
• Name the workflow, bank owner, and control owner.
• Document current pain, workaround, and measurable value.
• Identify the operating risk category.

Actions

• Interview the target workflow owner (or their proxy) within 5 days.
• Draft one-page use-case memo with named buyer and measurable friction.

Prove the problem is real, budgeted, and painful.

Core argumentThe problem must be real, budgeted, and painful enough to justify diligence.

Operational design

• Confirm buyer owner and budget owner.
• Quantify friction cost and urgency.
• Map the procurement path and decision criteria.

Actions

• Log 3–5 buyer conversations in the Market Validation Log.
• Convert one objection into a required-evidence line item.

Map every point where the product touches bank systems and data.

Core argumentBank readiness depends on knowing where you touch bank systems and data.

Operational design

• Document APIs, webhooks, logs, and manual paths.
• Draw data inputs, outputs, auth, and hosting.
• State the exit / portability path.

Actions

• Produce an evidence-sidecar architecture diagram for the first pilot.
• State explicitly what the first pilot will NOT touch.
• Weak integration score — redesign first pilot as a strict sidecar with no core writes.
• Document exit / portability path in the architecture diagram.

Assemble the vendor-review evidence pack.

Core argumentThe post-demo bottleneck is vendor onboarding, not founder storytelling.

Operational design

• Publish SOC 2 / ISO posture (or credible roadmap).
• Publish pen-test, IR, DR/BCP, subprocessor, retention posture.
• Publish encryption architecture, IAM model, and audit log design.

Actions

• Draft evidence-verification specification.
• Post subprocessor register with owners.
• Weak diligence score — commission SOC 2 readiness assessment this month.
• Publish subprocessor register with data-flow annotations.

Translate US assumptions into UK regulatory and buyer terms.

Core argumentThe UK track is a regulatory and buyer-translation exercise, not a branding one.

Operational design

• Map bank partner → authorised institution / principal / partner.
• Map vendor diligence → operational resilience / outsourcing controls.
• Map AI tooling → accountability, oversight, explainability.

Actions

• Have UK counsel review the pathway memo before Week 8.
• Name the first UK buyer archetype and partner archetype.

Classify AI on autonomy and instrument the controls.

Core argumentAI products need governance by autonomy level, not generic 'AI safety' claims.

Operational design

• Classify each AI function on the Operator/Collaborator/Consultant/Approver/Observer spectrum.
• Document human boundary, override, drift, escalation, and kill switch.
• Name accountable owner per AI function.

Actions

• Freeze prompt/output logging policy.
• Draft kill-switch runbook.

Clarify who owns every material risk.

Core argumentBank-fintech partnerships fail when control ownership is ambiguous.

Operational design

• Draft pilot RACI across incidents, disputes, model changes, data access, releases, outages.
• Publish risk register with severity and control.
• Name termination process and exit plan owner.

Actions

• Have risk register reviewed by a third-party-risk advisor.
• Confirm every 'A' in RACI is a real, named person.

Design a controlled, approvable first pilot.

Core argumentThe first pilot must be narrow enough to approve and meaningful enough to matter.

Operational design

• Define objective, scope, out-of-scope, users, data set.
• Define success metric, kill criteria, duration, fallback.
• State evidence output.

Actions

• Confirm no live customer data and no production write access in first pilot.
• Confirm accountable owner on the bank side.

Assemble the buyer-ready decision packet.

Core argumentA bank will not adopt a tool because it is interesting — it needs a decision package.

Operational design

• Model ROI: cost reduction, risk reduction, oversight cost, integration cost.
• Publish evidence room index.
• Produce buyer-ready presentation and UK Beachhead Pack update.

Actions

• Validate ROI baseline with two bank-side reviewers.
• Freeze evidence room v1.0.

Present a bank-readiness decision, not a pitch.

Core argumentDecision Day is a bank-readiness decision, not a pitch event.

Operational design

• Present buyer problem, validated workflow, integration design, data-flow map.
• Present diligence status, risk controls, UK landing plan, pilot economics.
• Make an explicit ask.

Actions

• Circulate the Decision Day Packet to reviewers 5 business days before the session.
• Log the decision and named next step against every open objection.

Ask whether the sprint produced bank-reviewable artifacts.

Core argumentWeek 11 asks whether the report and sprint produced bank-reviewable artifacts.

Operational design

• Review missing evidence and unresolved objections.
• Record score movement across the 6 dimensions.
• Log mentor notes, buyer feedback, and counsel-review items.

Actions

• For every open objection, name owner + due date.
• Version-tag every artifact touched during the sprint.

Convert the sprint into a 30/60/90-day execution plan.

Core argumentWeek 12 converts the sprint into a 30/60/90-day execution plan.

Operational design

• Finalise pilot recommendation and unresolved blockers.
• Record legal, security, and UK review needs.
• State commercial next step.

Actions

• Produce the Cohort Readiness Memo with an explicit decision recommendation.
• Hand the 30/60/90 plan to the founder team with owners assigned.