Episode Summary
Executive Summary: Ramiro Robayos explains how Tuki emerged from frustration with the opaque, error-prone U.S. immigration process and how the company built a service-first, tech-enabled workflow around transparency, control, and quality. He details the team’s manual MVP, the decision to keep all work inside one platform, the shift from heavy AI enthusiasm to workflow fundamentals, and the operational discipline needed to scale a labor-intensive legal service.
Main Topics: Origin story: personal immigration pain became the business (Priority: 5/5): Ramiro founded Tuki after experiencing his own stressful green card process and seeing the same frustrations across immigrant friends, leading him to build a better, more transparent immigration service. Service-first MVP before software (Priority: 5/5): The company began as a highly manual service where Ramiro acted as a paralegal/attorney workflow operator before the first product existed, learning client needs through hands-on execution. Platform philosophy: all work stays inside the system (Priority: 5/5): A core early decision was to prevent documents and workflows from escaping to Word/email, avoiding multiple sources of truth and preserving visibility, control, and process improvement. Roadmap evolution and limits of long-term planning (Priority: 4/5): Early AI enthusiasm gave way to focusing on foundational workflows and infrastructure. The team abandoned yearly roadmaps in favor of quarterly planning because priorities changed too quickly in an unfamiliar domain. Team-building and hiring rigor (Priority: 4/5): Tuki’s team grew through trusted relationships and an unusually extended hiring process: take-home task, interview, and a 1-2 month trial before full commitment. Scaling a tech-enabled service (Priority: 5/5): Because immigration is a service business, scaling risks degradation in quality. The team measures task time, studies attorney workflows, and deliberately resists hiring unless strategically necessary. Future: automation, quality control, and expansion (Priority: 4/5): Ramiro sees AI adding value mainly in error detection and drafting, with humans focusing on judgment and client interaction, and he believes the platform could expand beyond immigration over time.
Key Arguments: Immigration is too important to be handled with low-quality, low-visibility service; it should have excellent quality and transparency. A manual service can be a valid MVP if it teaches the team how the product should actually work before code is built. Keeping all work inside one platform is painful but essential because dual workflows create multiple sources of truth and destroy visibility. In a new domain, a yearly roadmap becomes obsolete quickly; quarterly planning is more realistic because priorities shift as the team learns. For service businesses, scale fails when headcount and process complexity grow faster than operational efficiency, so discipline and measurement matter. AI’s highest-value roles in legal workflows are quality control and drafting, not replacing human judgment. Strong hiring should be validated through extended real-world collaboration, not just interviews. Founders should align funding, go-to-market, team, unit economics, and long-term goals so strategy is coherent across the business.
Data Points: Time to usable first platform version: About 6 months - Ramiro said it took roughly six months from the first line of code to a usable end-to-end case workflow. Platform launch timing: June 2023 - He said development began around June 2023, shortly after the ChatGPT breakthrough. AI wave timing: 3-4 months after ChatGPT’s big explosion - Used to explain why the team initially over-focused on AI. Petition length: More than 1,000 pages - Some immigration petitions are extremely large and complex. Petition length: More than 2,000 pages - He emphasized the scale of some filings as a major operational burden. Hiring trial period: 1-2 months - Candidates are tested in real work before being fully hired. Daily trial workload: 1 hour per day to 2 hours per day - If a candidate has another job, Tuki asks them to work part-time during the trial. McKinsey tenure: 5 years - Ramiro referenced learning from his five years at McKinsey. Companies/groups worked with: More than 25-30 - He said he had worked with many companies and groups, shaping his perspective.
Pivotal Quotes: "The MPP of the service was myself working as a paralegal and an attorney with no technology." — Ramiro Robaios: Describing Tuki’s real MVP before the first software product existed. "Nothing was going to happen outside of the platform." — Ramiro Robaios: Explaining the foundational product decision to avoid Word/email side workflows and maintain one source of truth. "I think it’s a very fortunate position to be able to achieve your dream, to do what you like... and I think with all the responsibilities and pressures, it’s very easy to not enjoy that." — Ramiro Robaios: Advice to entrepreneurs about appreciating the journey while building.
Implications: Tuki’s story shows that in regulated, paperwork-heavy industries, operational excellence and product design must be built together. The model suggests AI’s near-term value is workflow augmentation, not replacement, and that service businesses must obsess over process discipline to scale without sacrificing quality.
About Code Story
Code Story is a podcast featuring startup founders, tech leaders, CTO's, CEO's, and software architects, reflecting on their human story in creating world changing innovation, disruptive digital products. Their tech. Their products. Their stories.