Use the same brief for every option and check the smallest route that would work. Compare the complete job, not a prototype against a subscription price.
Now that AI can write code, isn’t building the obvious answer?
Not necessarily. Faster to create doesn’t settle who maintains it, connects it or supports it.
1. Use the same brief for every option.
The job. Who needs what result, using which information?
The operating need. What access, integration, support and recovery are required?
The limit. What cost, customer effort and ongoing ownership are acceptable?
2. Check the smallest viable route.
- Configure
- Can a tool already approved by the business do enough?
- Buy
- Does an existing service meet the need and fit the process?
- Build
- Is the remaining gap important enough to justify creating and maintaining software?
3. Test the hardest part before committing.
Use an approved example to examine the uncertain integration, permission or exception, not only the easiest screen. Record what each option covers, what remains manual, who maintains it and what leaving would involve.
Practical check: Choose the fit. Don’t defend a favourite method.
Read more: An AI-Built Internal App Works. Is It Ready for the Business? · Do You Need an AI Agent, or a Simpler Process?
This is general guidance, not advice for your situation.