6d • General discussion 💬
Quick question for agency owners & business builders
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.
3
0 comments
Quick question for agency owners & business builders
skool.com/brendan
A free community for AI Voice Agents and n8n.
Join to learn, share ideas, and build real systems for the future.
Leaderboard (30-day)
1
+68
2
🔥
+56
3
🔥
+51
4
+34
5
+34
Powered by