Before you build anything (AI, automation, systems, products) who usually handles the requirement-gathering part? I’ve noticed that a lot of projects don’t fail because of bad tech…they fail because the problem wasn’t clearly defined upfront. From a Business Analyst lens, this “middle layer” is where: - Initial ideas get unpacked into what’s actually needed - Grey areas are clarified early instead of during development - Assumptions get challenged before they become rework In my recent work around AI and automation, I keep seeing the same pattern: Teams jump straight to tools, models, or workflows and only later realise they solved the wrong problem or missed key constraints. I’m curious to learn from this community: - Do you handle requirements internally? - Is it the founder, the dev team, the client, or no one explicitly? - What’s been the biggest issue you’ve faced when this step is skipped? genuinely interested in how others approach this.

Hi Askool community 👋 I’d like to share a partnership that might be useful to founders and operators here. I work as an AI Transformation Partner, helping businesses: • Identify high-impact automation opportunities • Design practical systems (AI and non-AI) • Improve operations with a strong focus on ROI To strengthen delivery, I’ve partnered with Lutho Dodo, an experienced automation builder with deep execution skills: • n8n, GoHighLevel (4+ years), Airtable, Appfy • React, Node.js, JavaScript • Builds solutions based on business need, not hype Together, we support businesses end-to-end: Strategy → System design → Automation → Implementation If you’re: • A founder looking to streamline operations • A business ready to move from “AI ideas” to production-ready systems Feel free to DM me or comment here — happy to connect or point you in the right direction. Thanks 🙌