About
Botworks is a small firm on purpose.
I’m Matt Livingston. I work directly with the executive who has the problem and the employees who understand the work. AI helps me carry much more of the investigation, analysis, product, and engineering work; I bring in specialists when the problem genuinely needs them.
Why this firm exists
I spent 15 years in software product management, most recently as a VP of Product Management. I was used to working with engineers, designers, analysts, and product people around the same problem.
Most operating companies do not have that group in-house, and I do not think recreating a software organization is a sensible use of their budget. They may have an IT provider, but keeping laptops and networks working is different from investigating a business problem and building a dependable product around it.
AI changed what one experienced person can carry. It can help inspect data, write and review code, generate tests, research unfamiliar systems, and document decisions. Botworks uses that leverage to build with the client’s team, while I remain accountable for the problem, the tradeoffs, and whether the result actually works.
The employees are not an afterthought or a source of resistance to overcome. They know where the process bends, which exceptions matter, and whether an answer is useful. My job is to make AI effective inside that reality.
What I care about
Getting to the truth and making the result useful to someone.
With software, the test is whether people can depend on it in the conditions of their job. With data, the test is whether the definitions and sources survive scrutiny by the people who understand the business. In both cases I would rather show an unresolved question than hide it inside a polished answer.
What I am not building
A new SaaS product every time a workflow is unusual.
Botworks builds custom software all the time: data connections, scripts, agents, reports, document pipelines, and focused internal applications. I do not want to recreate mature products or add interfaces, user roles, and permanent support obligations that the important job does not require. The client owns the company-specific work; continued engagement should come from usefulness, not lock-in.
Have something you want to think through?
Email is the best place to start. The first conversation is simply a conversation.