Launching a New Category with Modern Treasury's Dimitri Dadiomov

Founding Origin & Problem Definition

• Modern Treasury co-founders Dmitry Dadimov, Sam Aaron, and Matt Marcus launched in 2018 after identifying a critical gap in payments infrastructure while working at Lending Home.
• The core pain point involved "crazy spreadsheet math" required to reconcile complex money movements (ACH, wires, splits) between engineering teams and finance/ops departments.
• Most companies built subpar, one-off internal solutions because payments infrastructure was not a core competency and lacked sufficient investment justification.
• The resulting "Ugly Airbnb" internal tool highlighted the need for a unified platform bridging developer APIs and human-centric financial dashboards.

MVP Development & Technical Architecture

• The functional MVP took 10–12 weeks to build, with a total of five months required to onboard the first live customer due to banking integration complexities.
• The initial product architecture relied on a "three-legged stool" model: bank integration, a developer API for tech teams, and a dashboard for finance/ops reconciliation.
• Early feature scope focused strictly on bank rails (ACH and wires) rather than expanding into broader payment types immediately.
• SVB was selected as the first supported bank in Summer 2018 due to its dominance in the startup ecosystem and existing relationships with target customers.

Customer Acquisition Strategy

• The team abandoned outreach to larger, established companies (300–500 employees) due to internal inertia and the high risk of switching legacy systems.
• Focus shifted exclusively to early-stage startups (3–10 employees) that lacked dedicated payments engineering teams or heads of finance.
• The first customer was a friend of the co-founders launching a healthcare benefits company with complex payroll and reserve account reconciliation needs.
• Trust was established primarily through pre-existing personal relationships, which were critical for high-stakes infrastructure decisions involving money movement.
• Lead generation was broad and organic, utilizing cold outreach, investor referrals, and conversations with employees at other companies facing similar problems.

Organizational Structure & Hiring

• The founding team assigned clear primary and secondary decision-makers for all operational domains (e.g., banking, technical infrastructure, payroll) to accelerate execution.
• The company invested heavily in marketing and product development before hiring a dedicated salesperson until approximately two years post-launch.
• All co-founders and engineers participated in sales and customer discovery calls, often handling technical discovery before handing off to commercial discussions.
• The first full-time hire, Rachel Pike (later COO), was recruited for her expertise in healthcare payments and to lead brand and category definition.

Category Creation & Messaging

• The team consciously coined and defined the category "Payment Operations" to help customers identify the specific problem space they were solving.
• Marketing efforts focused on educating the market about the existence of the problem rather than inventing a new need, acknowledging that many companies still relied on manual processes.
• Product design principles ensured all features were accessible via both API and UI, catering to both "engineering-first" and "manual-first" customer workflows.
• Brand signaling emphasized long-term commitment and stability to reassure early customers of the vendor's survival and continued support.

Product Strategy & Feature Prioritization

• The team utilized a "birding" analogy to prioritize features: as the product matures, the marginal value of new feature requests diminishes, requiring a focus on the most common "boring" changes.
• Feature requests were treated as data points to identify recurring patterns, with a conscious decision to build only what solved the majority of known use cases.
• The philosophy of "homicide vs. suicide" was applied to competition, prioritizing internal execution and value delivery over tracking rival moves.
• As customers scaled, trust signals shifted from personal relationships to formalized SLAs, disaster recovery protocols, and quantifiable support metrics.

Forward-Looking Advice for Founders

• Early-stage founders should prioritize deep product mastery and user satisfaction over premature business model or pricing strategy optimization.
• Founders should avoid overthinking competition, noting that most business failures stem from internal missteps ("suicide") rather than external threats ("homicide").
• Charging early revenue is essential to validate genuine willingness to pay and uncover the true value of the product.
• Building a "cluster of excellence" around a niche domain allows startups to attract highly specialized talent and create a defensible market position.