11/04/2026
Anyone can have an app running in an afternoon now. That doesn't tell you whether to build it.
Our CEO Caleb Woods wrote three posts on adopting AI in business. Read together, they follow the order you face the questions.
Is it worth building? If lots of other businesses have the same problem, even in different industries, someone has already built a product for it. For accounting, that's QuickBooks. Build where the way you work is your competitive advantage.
Does it need to be an app? A lot of what people want to build is really reporting, and those questions change every month. Caleb runs his company-health questions through an AI workspace connected to our CRM, accounting, and time tracking. What he learns builds up with every session, and no reporting app had to be built or maintained.
How do you build it well? Build slow. A change takes minutes. Finding out whether it was the right change can take a week of real use. So start with the problem and the research, build in short bursts with time to use what you built in between, and put your effort into the process the agent works inside.
We started in 1997 as one of the first extreme programming studios. The tools have changed many times since, and the practices underneath still hold. As Caleb puts it, "Fast changes are a budget for more loops, not a shorter calendar."
Links to all three posts are in the comments.
