The first ninety days of the technical build, on a page: assess, plan and prioritize, then execute. Annotated with what is already complete as of June 2026 and what is gated on the pre-seed close.
This is management's plan of record for the first ninety days of the technical build: ninety days, three gates, and a definition of done for every action. It was built the way the rest of this room was built, sequenced against funding, scoped against the regulated architecture, and tracked honestly.
Two things to know before reading. First, the clock starts at the first close of the $3M Pre-Seed (the round opens July 1, 2026); the build is deliberately sequenced behind funding, which is a control, not a delay. Second, a meaningful share of the Day 1-30 discovery work has already been completed ahead of the clock, because the founder ran the discovery phase during the raise rather than after it. Each action below carries an honest status: COMPLETE, IN PROGRESS, or GATED ON CLOSE.
This document covers days 1 to 90. The full 0-to-12-month program it feeds, including the MVP build, the regulator-aligned sandbox pilot, and production hardening, is document 03.6, the Structured Roadmap Matrix. The first three phases of that matrix mirror this plan.
Objective: discovery and scope. Focus: the six HoldCo capability pillars, high-level architecture, product market options, buy-versus-build evaluation, and a preliminary budget.
| KEY ACTION | EVIDENCE | STATUS |
|---|---|---|
| Conduct founder and stakeholder interviews to validate vision, priorities, and decision criteria | Completed during the raise; decision criteria documented | COMPLETE |
| Break down the six HoldCo capability pillars into business capabilities, workflows, and platform domains | Control-plane capability set; documents 03.1 and 03.2 | COMPLETE |
| Inventory current assets, code, data sources, vendor relationships, and technical gaps | Operations documented in ClickUp / Drive; gap list in 10.4 | COMPLETE |
| Map end-to-end flows for onboarding, transaction processing, custody, reporting, and controls | Lifecycle architecture; live demo simulating 191 institutions | COMPLETE |
| Identify regulatory, licensing, and compliance constraints that shape architectural choices | Pathway mapped across CSA, OSFI, CIRO, FINTRAC; document 10.5 | COMPLETE |
| Assess buy-versus-build options for custody, tokenization, workflow, KYC/AML, and reporting components | SPEER contracted for the build; custody and AML vendors shortlisted | COMPLETE |
| Define security, privacy, resilience, auditability, and scalability principles | Verifiable-not-opaque design mandate; SOC 2 planned in pilot | COMPLETE |
| Produce a high-level architecture spanning data, application, integration, and control layers | Independent review scored 7.5/10 architecture fit, 8.5/10 strategic fit | COMPLETE |
| Identify integration dependencies across internal systems, external providers, and future partners | Rails, custody, and banking integration map; partly design-stage | IN PROGRESS |
| Surface technical, delivery, vendor, and regulatory risks with early mitigation options | SWOT with controls, document 10.4 | COMPLETE |
| Establish discovery success measures, assumptions log, and architecture decision register | Assumptions itemized in 05.5; formal decision register to stand up at close | IN PROGRESS |
| Define preliminary budget bands for discovery close-out, phase-one build, and enabling partners | Five-year model v7 (05.1); SPEER contract bands | COMPLETE |
High-level end-to-end architecture aligned to settlement, issuance, custody, and compliance; an initial buy-versus-build assessment; regulatory constraints mapped to architectural decisions; security and compliance design principles; and a discovery budget range with execution decision criteria. As of June 2026, these outcomes substantially exist ahead of the clock.
Objective: key resources, alignment, and risk. Focus: identifying two development leads, SWOT and contingency analysis, pre-seed budget validation, GTM solution alignment, and the technical team structure.
| KEY ACTION | EVIDENCE / GATE | STATUS |
|---|---|---|
| Consolidate discovery findings into a target-state architecture and phased delivery model | Execution-ready architecture pack reaches completion ~90 days post-close | IN PROGRESS |
| Sequence delivery by regulatory dependency, technical complexity, and GTM value | Sandbox application targeted Q3 2026; sequencing in 03.6 | IN PROGRESS |
| Confirm MVP and phase-one scope across settlement, issuance, custody, and compliance | MVP scoped as the deposit-token pilot | COMPLETE |
| Complete buy-versus-build decisions for core platform components and shared services | SPEER contracted; alternates kept warm; remaining component calls at close | IN PROGRESS |
| Validate pre-seed budget against scope, sequencing, partner needs, and hiring plan | CFA-audited model; $3M round sized to milestones | COMPLETE |
| Identify and begin recruiting two technical leads plus critical supporting roles | CTO candidate in advanced discovery; dev-lead hires gated to post-close | GATED ON CLOSE |
| Define the engineering operating model, decision rights, and accountability model | Ownership-versus-delegation framework drafted; formalizes with CTO | IN PROGRESS |
| Establish the SOC 2 readiness approach, ownership retained and execution delegated | SOC 2 scheduled within the pilot; process not yet started | GATED ON CLOSE |
| Align GTM requirements to platform capabilities, partner onboarding, and data readiness | Strategy reframe v2; tiered communication model live | COMPLETE |
| Create go/no-go criteria, contingency paths, and decision gates for execution | Three-step pilot validation defined; formal gates to be ratified at close | IN PROGRESS |
| Build the prioritized roadmap covering foundational platform, controls, and commercial enablement | Document 03.6, this data room | COMPLETE |
| Validate partner and SaaS integration assumptions needed for scale and rollout readiness | Partner stack reference in progress; LOIs are the near-term goal | IN PROGRESS |
Objective: establish competencies. Focus: development team build-out and hires, detailed architecture and roadmap, SaaS partner LOIs, and the operating model with the implementation budget. Everything in this phase is intentionally gated on the close; funding the build before the capital is in would contradict the discipline the rest of this data room documents.
| KEY ACTION | GATE | STATUS |
|---|---|---|
| Finalize the execution-ready architecture pack for partner, regulator, and engineering use | ~90 days post-close | GATED ON CLOSE |
| Mobilize core engineering resources against the first foundational workstreams | SPEER Phase 1 starts at close | GATED ON CLOSE |
| Launch the initial implementation backlog with ownership, milestones, and delivery cadence | Post-close | GATED ON CLOSE |
| Stand up delivery governance, architecture reviews, and weekly execution checkpoints | Post-close | GATED ON CLOSE |
| Initiate the security and compliance workstream with defined control owners and timelines | Post-close; SOC 2 within pilot | GATED ON CLOSE |
| Execute priority vendor selections and integration planning for approved external components | Shortlists ready; signatures at close | GATED ON CLOSE |
| Begin detailed solution design for foundational components and integration points | Post-close | GATED ON CLOSE |
| Finalize the implementation budget, delivery assumptions, and resource plan for the next phase | Model v8 carries the bands | IN PROGRESS |
| Publish the three-year capability roadmap aligned to the phased GTM strategy | Document 03.6 covers year one; years two and three extend it | IN PROGRESS |
| Firm up technology ownership, decision rights, and the long-term accountability model | Formalizes with the CTO seat | GATED ON CLOSE |
| Prepare the execution reporting pack covering roadmap status, risks, budget, and next decisions | Post-close cadence | GATED ON CLOSE |
An execution-ready architecture suitable for regulatory and partner discussions; core engineering capability mobilized; the security and compliance workstream formally initiated; the implementation plan and budget for the next phase finalized; a three-year capability roadmap aligned to the phased GTM strategy; and technology ownership, decision rights, and accountability firmly established. From here, the program hands off to Phases 4 through 6 of the Structured Roadmap Matrix (03.6).
Prepared for approved data room members. This document does not constitute an offer to sell securities or a solicitation of an offer to buy securities. 4orm Finance Holdings Inc. is the parent entity of 4orm OpCo, 4ormEx OpCo, and 4orm Trust Co; technology is developed by KCS Capital, an independent research and development firm.