S5 E11: Alexander Alimovs, Automations.io

Episode Summary

Executive Summary: Alexander Alemovs, founder of Automations.io, shares how he shifted from tinkering with many tools to prioritizing developer productivity, speed, and batteries-included stacks. The episode traces his journey from Latvia to the UK, the creation of a no-code automation platform for non-technical users, and the lessons he learned about MVP focus, customer-driven roadmaps, scalability on AWS, and the importance of go-to-market execution over building in isolation.

Main Topics: Founder background and origin story (Priority: 4/5): Alexander’s path from growing up in Latvia (formerly USSR) to studying in the UK and moving into business and technology set up his entrepreneurial mindset and appreciation for practical product building. Why Automations.io exists (Priority: 5/5): He identified inefficiencies in small tech teams and built Automations.io to let non-engineers automate repetitive business processes without needing code or API knowledge. MVP discipline and developer productivity (Priority: 5/5): The MVP took 6–9 months, and Alexander reflects that it should have been faster. He emphasizes using batteries-included tools and avoiding unnecessary complexity to maximize founder velocity. Customer-led roadmap and feedback loops (Priority: 5/5): Product decisions are now driven almost entirely by customer feedback, with Alexander focusing on live calls and avoiding self-directed coding unless it addresses a real customer need. Scalability architecture on AWS (Priority: 4/5): The platform uses a SPA frontend, Node.js API, Docker/Kubernetes, and AWS serverless/Lambda execution to keep the control plane lightweight and make automation execution highly scalable. Hiring, culture, and long-term vision (Priority: 4/5): Alexander wants to build a 10+ year business, stay bootstrapped, and hire passionate people who want to help create one of the best workplaces they’ve ever had. Go-to-market and founder lessons (Priority: 5/5): He stresses that building alone is not enough; founders must identify ideal customers, do outreach, and define a go-to-market strategy instead of relying on Product Hunt or 'build it and they will come' assumptions.

Key Arguments: Developer productivity improves when founders choose batteries-included tools and minimize setup decisions, allowing faster shipping. A core MVP should focus only on essential functionality; extra features like CRM/contact management can distract from launch and customer learning. Customer feedback should drive the roadmap, especially in early-stage products where assumptions are often wrong. Non-technical users can be empowered to automate workflows visually, similar to how Wix and Squarespace enabled website creation without coding. Scalability should be designed in early using cloud-native infrastructure; AWS, Lambdas, SQS, and Kubernetes provide enough headroom for growth. A founder should spend more time speaking with customers and selling than coding once the product is viable. Go-to-market strategy matters as much as product quality; without distribution and target-customer clarity, good products often fail to grow.

Data Points: Country of birth: USSR / Soviet Union (now Latvia) - Alexander described being born in a country that no longer exists and later growing up in Latvia. Age when moved to the UK: 18 - He moved to the United Kingdom for school in 2008. MVP build time: 6–9 months - He said the first MVP took around six to nine months and should have been shorter. Company stage: Early stage / bootstrapped - He described Automations.io as an early-stage, bootstrapped business. Time since beta launch ended: 2–3 months - He noted the company came out of beta about two to three months prior. AWS usage: 100% on AWS - He emphasized that the platform runs entirely on AWS, including serverless components. System scale example: 1 million runs/day - He explained that if automations run a million times a day, AWS Lambdas handle the workload. AWS start year: 2013 - He said he began using cloud/AWS in 2013 and has designed for scalability since then. Business horizon: 10+ years - He wants Automations.io to be a long-term business rather than a quick exit. Time spent on growth now: 99% - After beta, he said almost all of his time is now focused on growth and acquiring customers.

Pivotal Quotes: "Velocity is key. Just want something out of the box where I can start." — Alexander Alemovs: Explaining his shift toward batteries-included tools and away from tool tinkering. "The roadmap right now is purely driven by feedback." — Alexander Alemovs: Describing how Automations.io prioritizes customer requests over founder assumptions. "If we build, they will come, but 99% of time they don't come." — Alexander Alemovs: Advising founders to take go-to-market and customer targeting seriously.

Implications: The episode reinforces that successful early-stage SaaS is less about overbuilding and more about speed, customer discovery, and distribution. For automation and no-code tools, the opportunity is in making advanced capabilities accessible to non-technical users.