Skip to content

Studio projects

Defined formats for turning fintech questions into working systems.

Each format connects a specific question to concrete outputs and a typical build window. They can stand alone or combine across a broader product initiative.

Project formats

  • Typically 3 to 4 weeks

    Stablecoin Commercialization Sprint

    Take a working settlement or payments capability and produce the commercial thesis, the prioritized buyer, and the launch plan behind it.

    Outputs

    • Prioritized buyers and use cases, with the cuts made explicit
    • Product and commercial narrative used by sales, partnerships, and fundraising
    • Route-to-market and distribution model
    • Partner ecosystem map with dependency ratings
    • Launch roadmap with owners, dates, and the metrics that test the thesis

    Best for

    Infrastructure providers, issuers, and fintechs whose product works and whose commercial story does not yet hold in a room.

  • Typically 4 to 6 weeks

    Payments GTM Launch Package

    Build the commercial motion around a payments product, from segmentation through to the first 90 days of execution.

    Outputs

    • ICP and segmentation, defined by observable characteristics
    • Messaging architecture and sales narrative
    • Channel and partnership plan, including partner economics
    • Enablement assets that get used rather than filed
    • 90-day GTM plan with named owners and weekly review format

    Best for

    Teams moving from founder-led sales to a repeatable motion, or launching a product that depends on partner distribution.

  • Typically 3 to 4 weeks

    International Expansion Sprint

    Narrow the market list on evidence, understand how money actually moves there, and sequence an entry you can defend to a board.

    Outputs

    • Market prioritization with scoring criteria and a ranked shortlist
    • Local ecosystem, payment method, and partner map for priority markets
    • Entry model with dependencies and gating constraints
    • Localization requirements across product, onboarding, pricing, and support
    • 90-day execution plan with owners and decision points

    Best for

    Companies choosing their next corridor or country, or diagnosing why the first international market underperformed.

  • Typically 2 to 4 weeks, depending on integrations

    Agentic Workflow Pilot

    Select one workflow worth automating, design the approval structure, build it, and measure whether it actually helped.

    Outputs

    • Selected workflow with a measured baseline
    • Human-in-the-loop design, including permissions and escalation paths
    • Working prototype, or an implementation plan where integrations require one
    • Evaluation criteria and test cases agreed before build
    • Rollout recommendation, which is allowed to be no

    Best for

    Teams carrying structured manual workload, or teams whose previous AI pilot produced a demo and no operating change.

  • Typically 2 to 3 weeks, depending on provider onboarding and credentials

    Technical Spike & Reference Build

    Turn a stuck technical question into a running prototype, measured findings, and a decision your engineering team can act on.

    Outputs

    • Falsifiable question and pass criteria agreed before the build starts
    • Working prototype or reference integration against the provider sandbox
    • MCP server or agent-facing surface with scoped tools, auth, and logging, where that is the question
    • Findings on failure modes, undocumented behavior, and where the documentation is wrong
    • Build-or-buy recommendation with the engineering cost to finish
    • Repository handover with README, configuration, and known limitations

    Best for

    Teams choosing between infrastructure providers, exposing product capability to agents, or carrying a roadmap item nobody can estimate because nobody has built against the API yet.

  • Typically 4 weeks

    Ecosystem Activation Sprint

    Give a community, developer, or partner program a commercial job, a participation model, and a measurement system.

    Outputs

    • Ecosystem architecture and stakeholder map
    • Participant value proposition by segment
    • Activation program with journeys from first contact to first contribution
    • Operating calendar and governance definitions
    • Measurement framework based on contribution and adoption

    Best for

    Foundations, ecosystem teams, and platforms with programs running on activity metrics rather than adoption metrics.

  • Ongoing monthly, reviewed at 90 days

    Fractional Product & Commercialization

    Senior product and commercial ownership with a written mandate, a fixed operating cadence, and success measures agreed before the first week.

    Outputs

    • Written mandate covering decision rights, cadence, documents produced, and exit conditions
    • Commercialization plan and product narrative maintained in your tools
    • Roadmap and prioritization system with explicit criteria
    • Operating reviews, decision log, and board-ready materials
    • Defined handover when the mandate ends or narrows

    Best for

    Founders carrying product decisions alongside everything else, companies between product leaders, or a critical initiative that needs an owner.


How studio projects take shape

  1. 01Start with the questionDefine the product, system, market, or workflow under examination and what a useful answer would make possible.
  2. 02Choose the right formatMatch the question to the smallest useful combination of commercial modeling, product design, operating structure, and technical build.
  3. 03Build and documentProduce a usable artifact—such as a roadmap, operating model, prototype, integration, or launch system—and document what it proves.

Connect

Have a fintech question worth developing?

Use the contact page for ideas involving products, infrastructure, partnerships, speaking, or the studio itself.