It started with Max teaching himself to code. His first build, a projections engine, took months. Then the tools changed. A quarter's work became a fortnight's, and the gap between "someone should build that" and "that's built" collapsed.
He didn't stop there. Other businesses had the same problem.
Max took it into fast-moving consumer goods (FMCG). Replaced enterprise tools that had teams buried in data entry, and freed them for the forecasting that moved revenue. Then into trades, built so workshop teams could stop losing hours to admin and get back on the tools.
Finn took it into financial services. Replaced four separate tools with one, freeing a practice to see clients instead of chase paperwork. Then into commission reporting, cancelling a paid tool the business no longer needed and giving back the person who used to reconcile spreadsheets by hand.
Somewhere in doing that, both of us got obsessed with the same thing: delivering outcomes that freed up time, so that time could go back into the work that makes money.
Two different industries, same realisation. Both had constraints around privacy, compliance and audit that meant you couldn't just plug a chatbot in and hope.
whatcould.ai is the two of us doing that for everyone else. Delivering outcomes that let a business scale, spend less and serve its clients better, because the people running it are finally spending their time on the work only they can do.
We work from an office in Bentleigh East, Melbourne — happy to have you drop by, or we come to you.