Founder Chats - Vadim Dedov

Episode Summary

Executive Summary: Vadim Didov, CEO of Catchers, explains how an HR/staffing pain point born from running operations on Excel evolved into a worker-first platform for fast shift assignment, document handling, and compliance. The conversation covers early product trade-offs, architecture redesign for scale, a biometric-to-QR pivot after regulation changes, team-building principles, and why strong fundamentals and automation matter for infrastructure-heavy products.

Main Topics: Origin story: operational pain in staffing (Priority: 5/5): Catchers began as an internal solution to the founders’ own scaling problems in an HR agency, where Excel and manual coordination broke down under growing client and worker volume. Worker-first product design (Priority: 5/5): The product was differentiated by optimizing for the worker experience—fast applications, quick verification, flexible shift selection, and rapid start times rather than HR admin workflows. MVP constraints and early trade-offs (Priority: 4/5): The first usable version took months to build and required pragmatic decisions around integrations, legal uncertainty, and postponing non-core features to focus on document flow and compliance. Scaling, architecture, and stability (Priority: 5/5): As complexity increased, the team slowed down to rework architecture, codebase, and UX/UI, shifting priorities from speed of shipping to system stability and usability. Team building under constraints (Priority: 4/5): Vadim emphasized hiring for adaptability, creativity, responsibility, and shared values over pedigree, especially because no one on the market had built exactly this kind of system before. Setback and pivot: Face ID to QR (Priority: 5/5): A planned biometric check-in/check-out system was derailed by new biometric data regulations, forcing the team to pivot to a simpler dynamic QR-code approach. Automation, AI, and fundamentals (Priority: 4/5): Vadim sees automation and AI as net positive for reducing repetitive work, but argues that infrastructure-heavy products must start with clear structure, architecture, and priorities before scaling.

Key Arguments: Manual tools like Excel can work only until operational complexity and scale make them unmanageable. A staffing platform should be designed around the worker’s speed and convenience, not just HR department workflows. Building a product from internal pain points can reveal the real requirements better than abstract market analysis. Early-stage product teams should focus on core business processes first and defer secondary features. Scaling requires architectural redesign and UX simplification, not just adding more features. Hiring for problem-solving ability, adaptability, and shared values can be more important than prior domain experience. Regulatory changes can invalidate technically elegant solutions, so product design must account for compliance risk. AI and automation should remove repetitive work, but they do not replace the need for strong system fundamentals.

Data Points: Time to first usable version: About 8 months - Vadim said the initial internal MVP took roughly eight months to build. Scale of workforce: Workers went into the thousands - The operational pain emerged as the HR agency grew and managed a very large worker base. System redesign period: About 1 year - The team slowed down and spent about a year improving architecture, codebase, and UX/UI for scale. Shift-to-payment speed with verified workers: Minutes - If a worker is already verified, application to shift can take only minutes.

Pivotal Quotes: "You don't wait for someone else to fix things you step in." — Vadim Didov: He described how losing his father early shaped his sense of responsibility and accountability. "Catcher was designed around the worker, not their HR department." — Vadim Didov: He explained the core product insight and differentiation behind Catchers. "Build the backbone first, then scale." — Vadim Didov: His advice for founders building infrastructure-heavy products and avoiding premature feature expansion.

Implications: The episode reinforces that durable B2B platforms come from solving real operational pain, prioritizing fundamentals, and designing for compliance and scale early. For founders, the lesson is to simplify, focus, and adapt quickly when regulation or complexity changes the path.