A&A INSIGHTS
Use existing tools or build a system of your own?
Compare existing tools, configuration and integration, and custom development against the same workflow. Include review effort, maintenance, changes, and exit as well as initial cost.
日本語で読む
THE STARTING POINT
Compare existing tools, configuration and integration, and custom development against the same completed task. Consider user effort, review, costs, maintenance, and future changes, then test the part that matters. The aim is a justified scope for your business.
Compare three routes against the same completed task
A&A perspective
Before choosing an existing tool or a custom build, define who uses which information and what counts as completing the task. We suggest comparing options against one workflow. For inquiries, preparing a draft response is a different scope from assigning an owner and recording the response status. Describing the completed task gives all options the same target. The presence of AI alone does not tell you whether an option covers the functions and handovers your company actually needs.
From the sources
Anthropic’s engineering guide distinguishes workflows with predefined paths from agents that direct their own process. It recommends starting with the simplest adequate approach and adding complexity when justified. We use it as design guidance published in 2024, not as a current ranking of products.
Use, configure and connect, or build
A&A perspective
For direct use of an existing tool, ask whether current features complete the task. Configuration and integration aim to connect your material and existing tools or fill a missing handover. Custom development can address requirements such as a particular approval process, a customer interface, or business-specific rules. These are options, not a ladder of quality. The comparison below is our analytical framework rather than a guarantee about every product in a category. A single workflow can combine more than one route.
From the sources
As an example of configuration within an existing platform, Microsoft documents setting instructions and knowledge sources and testing an agent in Agent Builder. Available sources and capabilities differ by license. This illustrates a configuration route; whether the needed capabilities are included in your own agreement still requires checking.
| Route | Where to examine fit | Check first |
|---|---|---|
| Use an existing tool | Current features may complete the required task | Usable information, access conditions, remaining manual work |
| Configure and integrate | Internal material or existing tools need connecting | Available connections, permissions, failure handling |
| Develop the required part | A specific interface, approval, or decision process is essential | Acceptance criteria, maintenance owner, changes and exit |
Compare ongoing work as well as acquisition
A&A perspective
Compare user steps, information handovers, exception handling, permissions, recurring charges, review effort, and ownership of changes and maintenance. A low subscription price can still leave manual copying to account for. A development quote also needs to be considered alongside usage charges and future changes. Record supplier terms, estimated implementation work, and your own review effort separately. This makes the comparison easier to revise when a condition changes, without pretending that every part is equally certain.
A&A perspective
We also suggest comparing how the setup can be changed or retired. Can you export documents and records? Will another operator understand the configuration? Can work return to an earlier process if a connected service is unavailable? A custom application can still depend on outside models and services. Identify those dependencies instead of assuming that ownership of the code removes them. Choose something the company can manage at its current scale and record what would justify changing that choice.
A hypothetical hybrid inquiry workflow
Hypothetical example
Consider a hypothetical company already receiving inquiries through a form. The proposed task is to summarize the inquiry with AI and have an employee review it before preparing a reply. Keep the form and customer records initially, and test whether existing integration features can move the necessary information. If the problem is the effort of reading and organizing inquiries, question whether rebuilding the intake screen belongs in the first scope. This keeps the implementation tied to the stated problem.
Hypothetical example
If testing shows that person-specific approvals or shared processing status are essential and cannot be covered by configuration, consider developing that part. Include confirmation before external sending, prevention of duplicate processing, and a way to handle failed connections in the completion criteria. This example does not claim that a particular product supports the workflow or that A&A has delivered it. The boundary between configuration and development must be established by checking the actual connections and operating conditions.
Define the first completed scope and its fallback
From the sources
NIST’s AI Risk Management Framework addresses human oversight and testing before deployment and during operation. We use this as risk-management context, not as evidence that a particular implementation method guarantees safety.
A&A perspective
For the first scope, write not only what will run but who reviews it, which inputs will be tested, and how work falls back after failure. In the inquiry example, clarify whether completion means an internal summary or an approved reply. Test missing information as well as ordinary inputs. Identify who maintains documents and rules after handover, and distinguish everyday configuration from changes that require additional development. This makes an estimate and an acceptance decision easier to assess.
Use the comparison to scope the next step
A&A perspective
If existing tools complete the task, begin by improving how they are used. If the gap is a connection, a small integration prototype may be the next step. If a particular interface or decision process is required, define that part before estimating development. An A&A discussion can work through these boundaries alongside the business objective. You do not need to arrive committed to a custom build; unresolved questions from the comparison are useful material for the conversation.
A&A perspective
A&A’s published standard AI advisory retainer is JPY 50,000 per month excluding tax, focused on advice. Initial foundations and development are separately scoped and quoted. The comparison above does not imply unlimited development within that retainer. One possible sequence is to establish a foundation first, then continue discussing use and business decisions through advisory work. The appropriate scope depends on the workflow and support the company needs.
Choose the approach that lets the business complete and sustain the work it needs. Define the outcome, verify the gaps, and make the first scope concrete. That gives you a reasoned choice whether it involves existing software, development, or both.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Building effective agents
Anthropic · 2024-12-19 (current page checked)
Accessed 2026-09-14 - Build agents by using Agent Builder in Microsoft 365 Copilot
Microsoft · Updated 2026-08-19
Accessed 2026-09-14 - AI RMF Core
NIST · 2023 (AI RMF 1.0; revision in progress)
Accessed 2026-09-14
AI-assisted editorial production
A&A uses AI for research, writing, translation and editorial checks. Source facts, our analysis and hypothetical examples are labeled separately.
Editorial check: 2026-09-14