Innovation isn’t born from big budgets - quite the opposite. My adventures helping homeless cats with AI

var(--variable-AZGxkMO6x)

My biggest innovation “aha” moment lately came through volunteering at Cats Help MTÜ. And the innovation wasn’t so much in the solution as in my own thinking. It proved to me once again how important it is right now to practise using AI tools. It’s almost like retraining.

As with non-profits in general, Cats Help’s funds are limited and mainly meant for helping cats. That’s why the choice of IT solutions at our disposal is fairly limited too. (Or, well, maybe it’s useful for someone to know that Google Workspace and Wix are free for non-profits, but I’ll talk about that in another article.)

Our mantra is that if there’s a free solution, we use it, because donations have to go to animal rescue. But that often means processes can’t be automated and we have to rely on volunteers. That was the case with our charity calendar sales too, until this year.

The yearly calendar-sales merry-go-round

Every year around Christmas, with the help of a volunteer designer, photographers and other helpers, Cats Help makes a charity wall calendar and desk calendar. That way we can support more cats and give donors something beautiful in return.

Until now, all sales went through Google Forms. The buyer fills in the form, makes a separate bank transfer, and a volunteer:

  • checks that the buyer’s details are there and make sense

  • checks that the payment has arrived in the bank

  • contacts the buyer if needed

  • creates the parcel in Omniva

  • takes the parcel to a parcel locker

The process has been so labour-intensive that sometimes one person handles it, and sometimes three more have to help.

Volunteers have asked many times whether we could do something more automated. We considered Wix’s e-shop functionality, but it doesn’t work for us because of the payment solution and partly missing Estonian language support. Buying a separate e-shop for a couple of weeks a year doesn’t make sense either.

The best option would have been a custom solution, but unfortunately there was nobody who could help with that. As a product manager I’m used to always having a small army of developers - I describe what’s needed and they build it. Here there are only a handful, and they’re all already busy with other things.

But there has to be a way…

This year has been different. I’ve got to a place where I dare to experiment. And on the other hand, AI tools have reached a stage where even someone who doesn’t write code can genuinely build something.

I can’t write code, at least not at an acceptable level. But I understand how software works, how the logic flows and what the user journey should look like. And I felt that now is the time when I can do much more with my knowledge than before.

It surprised me how strongly I was used to thinking in the pattern: “I can describe the solution, but after that we need a developer.”

This time I decided to consciously test that thought.

I used Lovable, a tool that can genuinely build applications with the help of AI. I described it to Lovable exactly the way I’m used to as a product manager:

  • what the end user’s journey through the order form should look like

  • what information the volunteer needs to see

  • which statuses need to exist

  • how the Montonio bank link needs to work

  • what information needs to be saved and when

  • what errors should look like

I wrote it all down, gave Lovable the Montonio documentation and asked it to build a solution that:

  • collects the buyer’s details

  • lets them pay straight away

  • checks automatically that the payment has arrived

  • gives volunteers a clear overview of orders

Within a couple of hours, by the end of one Sunday, we had a genuinely working solution. I tested payments. Everything worked.

The real limitation was me

The real surprise wasn’t that Lovable built the solution. The surprise was how clearly I felt that the biggest limitation wasn’t the technology, but my own thinking.

At every step I had to argue with myself not to give up. Every time I got to the next step, the inner voice I’d built up as a product manager said: “okay, I probably can’t go further from here, now it’s a job for a developer”.

And at every step I decided I’d at least try. That if in the end it really didn’t work out or got too complicated, I’d hand the work over to someone.

But in the end it turned out, quite calmly and simply, that there was no need. The solution worked. It was there, it was logical and in many ways more convenient than anything we’d used before.

What changed

This year the calendar sales work like this:

  • one volunteer can handle it, not three

  • payments are checked automatically

  • all order information is organised and clear

  • volunteers can spend their time on something genuinely useful

And actually the biggest change happened in me.

I realised that in today’s AI era you essentially have an extra right and left hand as helpers, covering the places you can’t or don’t know how to cover yourself. And that gives you the courage to cross the skill boundaries I thought I had.

Scarcity drives innovation

Constraints aren’t an obstacle but a frame that forces you to keep focus and find solutions. No matter how. Often it’s precisely constraints that make innovation happen.

In the non-profit world there’s little money, few developers and few options. But motivation is high and creativity is limitless. And in today’s AI era, one product manager can build in one Sunday something that would previously have needed a whole development team.

A small call to action too. If you want to grow in your field or just make small miracles happen, I warmly recommend giving even a small part of your time as a volunteer to help a non-profit.

Want to know more?

Follow me on LinkedIn or get in touch!