Docs

BuildFinance

Milestone Payment Certification and Release Ledger

Executive Summary

BuildFinance Executive Memo Date: April 1, 2026 | Asking: $500K | Type: Pre-Seed Executive Summary BuildFinance is a blockchain-native payment certification platform for construction subcontractor networks. We use DUAL Network's state machine and event bus to automate milestone verification, eliminate payment disputes, and provide an immutabl

Token Data Schema

What this token holds — every field is specific to BuildFinance:

{
  "immutable": {"id": "uuid", "created": "timestamp"},
  "mutable": {"status": "string", "owner": "string"},
  "compliance": {"audit_log": ["string"]}
}

User Journey

Step 1: General Contractor

Creates milestone payment schedule tied to construction phases and subcontractor scopes

Token: milestone_token created, total_contract_value set, escrow_funded

Step 2: Subcontractor

Completes foundation pour; uploads timestamped photos, inspection report, and GPS coordinates

Token: state → Milestone_Submitted, evidence_hash recorded, completion_date set

Step 3: Independent Inspector

Verifies work quality on-site; signs off with certification number and deficiency list

Token: inspection_status = Passed, inspector_did signed, deficiencies = 0

Step 4: Lender/Escrow Agent

Confirms inspection passed and retainage hold; authorizes milestone payment release

Token: state → Payment_Authorized, retainage_held_percent = 10, payment_released

Step 5: Project Owner

Reviews final completion certificate; releases retainage after warranty period expires

Token: state → Closed, retainage_released, final_lien_waiver attached

Token Lifecycle

State machine transitions:

Planned→In Progress→Verification Submitted→Verified→Payment Released→Retainage Held

Why Not Just a Database?

ApproachPortabilityMutable StateCross-OrgCompliance
Traditional DB Locked to vendor Any field mutable Manual reconciliation Single audit trail
Public Blockchain Portable but slow Immutable-only Transparent but expensive Full transparency
SaaS Platform Vendor lock-in Centralized control Complex APIs Vendor-dependent
DUAL Token Portable across systems Selective mutability Native settlement Embedded rules

Market Opportunity

TAM
$2.5B
SAM
$600M
SOM
$80M

BuildFinance addresses growing need for tokenized asset management. DUAL enables native token solutions without blockchain overhead.

Business Model & Unit Economics

  • Platform License: BuildFinance subscription: $25K-$100K/year
  • Transaction Fees: 2-5% of tokenized volume
  • Compliance Services: Audits and reports: $10K-$50K/audit
  • Premium Support: 24/7 monitoring: $500-$2K/month
Unit Economics

$5-$15 per token transaction, 70% gross margin at scale.

5-Year Projections

YearARRCustomersNotes
Y1 $500K 5 Pilot phase
Y2 $2.5M 25 Product-market fit
Y3 $8M 75 Market leadership
Y4 $18M 150 Cross-vertical scaling
Y5 $35M 250 Regional dominance

Competitive Positioning

CompetitorWeaknessDUAL Advantage
Legacy DB Providers No cross-org portability Distributed settlement
Public Blockchains Immutable-only, expensive Mutable state, low-cost
SaaS Leaders Vendor lock-in, limited composability Open standard
Custom DIY High build/maintenance cost Out-of-box solution

Go-to-Market

Phase 1: Pilot (Months 1-6)

Target 5 pilot customers, prove ROI

Phase 2: Scale (Months 7-18)

Expand to 25+ customers, build partnerships

Phase 3: Dominate (Months 19-36)

Cross-vertical expansion, 100+ customers

90-Day MVP

  • Core token schema with immutable/mutable/compliance layers
  • State machine with 5-6 transitions
  • REST API for token lifecycle operations
  • Audit logging and compliance reporting
  • Basic dashboard for monitoring
  • Integration test suite with 80%+ coverage

Risk Factors

Regulatory Risk

Tokenization may require securities licenses

Mitigation: Engage legal counsel early, target compliant verticals

Adoption Risk

Enterprises slow to adopt new standards

Mitigation: Focus on high-ROI problems, build proof-of-concept

Competitive Risk

Incumbents may adopt tokenization

Mitigation: Build network effects, maintain innovation velocity

Technical Risk

State consistency in distributed systems

Mitigation: ACID compliance, comprehensive testing, gradual rollout

VC Pack Documents

Get Started with AI

Prerequisites: Complete the DUAL Quick Start Guide to set up your environment and API keys before building this concept.

## Design the BuildFinance Token Architecture

Your goal: Create a complete DUAL token schema that enables Milestone Payment Certification and Release Ledger on the DUAL platform.

**Start with:**
1. Immutable fields (identity, timestamps, core properties)
2. Mutable fields (status, ownership, metrics)
3. Compliance rules (state transition constraints)
4. Token lifecycle (5-6 state machine)
5. User journey with named actors
6. Competitive comparison

**Key constraints:**
- Every field must have clear owner and mutability rule
- Every state transition must be audit-logged
- Design for 10x scale, not just 2x
- Focus on cross-org composability

**Deliverables:**
- Token schema JSON (15+ fields)
- State diagram (5-6 states)
- 5-6 user journey steps
- Compliance rule set
- Integration playbook
Previous
AutoChain
Next
Carbon Integrity