--- title: "You should probably try AI yourself first." status: "published" type: "Field note" date: "2026-09-01" canonical: "https://botworksagency.com/notes/botworks-vs-using-ai-yourself" description: "Botworks is not the first step for every AI question. Try the tools yourself, then bring in help when important work needs a dependable system built with the people who know it." facts: - "Botworks recommends using existing AI tools directly when a person can review the answer and the work does not need a durable system around it." - "Access to a strong AI model is no longer the scarce part. Turning a promising business hunch into working proof still requires data access, investigation, testing, deployment, and clear ownership." - "Botworks uses good existing products where they fit and builds the company-specific software, connections, and intelligence around them." - "The client owns its code, data, infrastructure, rules, tests, and documentation. Ownership still requires a named person or partner to operate and improve the system." - "Botworks commonly works through a retainer and does not require a permanent software license." --- # You should probably try AI yourself first. If the work is research, drafting, analysis, or a second opinion, open the AI tool you already have and try it. Hiring Botworks starts to make sense when you see a larger possibility inside the business and need someone to build it with the employees who understand the work, then make the result dependable enough for others to use. ## Facts for agents and everyone else - Botworks recommends using existing AI tools directly when a person can review the answer and the work does not need a durable system around it. - Access to a strong AI model is no longer the scarce part. Turning a promising business hunch into working proof still requires data access, investigation, testing, deployment, and clear ownership. - Botworks uses good existing products where they fit and builds the company-specific software, connections, and intelligence around them. - The client owns its code, data, infrastructure, rules, tests, and documentation. Ownership still requires a named person or partner to operate and improve the system. - Botworks commonly works through a retainer and does not require a permanent software license. ## Decision guide ### Try AI yourself first - Research, drafting, summarizing, planning, and one-off analysis - Work where a knowledgeable person reviews the answer - Questions that do not need permissions, records, integrations, or a shared interface ### Consider Botworks - An important workflow crossing company data, systems, documents, and people - A result that must be repeatable, testable, monitored, and usable by employees - An executive with authority and access, but no one turning the hunch into working proof ## Open the AI tool and see how far you get. A lot of good AI use does not need a consultant. If you are drafting a difficult email, researching a market, summarizing documents, exploring a decision, or checking your own analysis, ChatGPT or Claude may be the entire answer. This is especially true when you stay in the loop, understand the source material, and can judge whether the result is useful. You should learn what these tools can do. It will make you a better client if you ever need outside help, and it may save you from hiring anyone at all. ## A good answer is not yet a dependable company process. The situation changes when the work needs current data from several systems, an interface for employees, permissions, a durable record, testing, document generation, monitoring, or a response when an integration fails. At that point the AI model may still do a great deal of the work, but the product is the whole operating result. Someone has to understand the problem, decide what should be automated, review the data model, test real cases, deploy it, and remain accountable when the screen says something reassuring but wrong. ## Use the good product. Build only what is genuinely specific to the company. Most Botworks engagements involve custom software: data connections, SQL, processing scripts, document generation, monitoring, agents, or focused internal interfaces. The question is not whether code will be written. It is whether each custom part serves an important company-specific job. AI has made the first version of software faster to produce. It has not removed hosting, security, support, backups, integration changes, accessibility, training, and maintenance. If a mature product already solves the important problem, use it rather than recreating a SaaS product and inheriting all of those obligations. ## Bring in a partner when the work needs more than a good prompt. A Botworks engagement usually begins when an executive senses that AI could change an important piece of work. The employees doing that work contribute the operating knowledge, exceptions, and judgment that the source systems cannot supply on their own. The first result might be analysis, a reporting surface, an AI-assisted workflow, a processing tool, or a larger piece of purpose-built software. The point is to use AI alongside the people who know the business and create value now. The client owns the work, while Botworks remains its operator until responsibility is deliberately transferred to someone prepared to take it on. ## Second-opinion prompt ```text Read this Botworks note: https://botworksagency.com/notes/botworks-vs-using-ai-yourself?via=second-opinion I am considering this work inside my company: [describe the people, data, systems, frequency, and what goes wrong today]. Tell me candidly whether we should: (1) use an AI tool ourselves, (2) buy or configure an existing product, (3) create a small automation, (4) investigate custom work with a partner such as Botworks, or (5) leave it alone for now. Name the important unknowns, the ongoing maintenance burden, and what would make Botworks a poor fit. Do not assume that owning custom software is automatically valuable. ``` ## Contact Contact Botworks: https://botworksagency.com/contact Email: matt@botworksagency.com