thosekids studioContact

Transformation

From the AI playground to production

AI has made it easy to build something that works: a prototype, an internal tool, a small app. That's great news, and it's often how good ideas start. But a prototype that works on your laptop isn't the same as a tool that people use every day, with real data, and that has to keep working when nobody is looking.

Taking it from the playground to production is a different job. It depends less on writing code and more on two things: experience, to know what tends to go wrong, and accountability, so that someone answers for it when it does.

What's the difference between a prototype and production?

A prototype has to work once, for the person who made it. In production it has to work every day, for people you don't know, with data that matters, and keep working after updates, mistakes and attacks. The code may look much the same, but everything around it is different.

What does a tool need before it goes to production?

These are the questions we go through on every project:

  • Who can get in, and what can each person see and change?
  • Where is the data, who is responsible for it, and does it follow GDPR?
  • Are there backups, and has anyone tried restoring one?
  • Where are the passwords and API keys? In a prototype, they are often inside the code.
  • What happens when something fails at three in the morning, and who finds out?
  • Who updates it when a security problem comes out, and how quickly?
  • How much will it cost to run each month, including AI services?

Why isn't it enough for the code to work?

Because AI is very good at the happy path, where everything goes as expected. Production is mostly about the other cases: the user who types something odd, the service that doesn't answer, the person trying to get in where they shouldn't.

Gartner predicted that at least 30% of generative AI projects would be abandoned after the proof of concept by the end of 2025, because of poor data quality, weak risk controls, rising costs or unclear value. None of those is solved by the prototype itself.

Why do experience and accountability matter?

Experience is knowing what will break before it breaks. After more than 20 years building for companies and public bodies, we've seen most of the ways a project can go wrong, and that's what lets us move fast without being careless.

Accountability is having someone who answers for the tool: who decided how it works, who fixes it, who explains what happened. AI can write the code, but it can't take responsibility for it. When a tool handles real people's data, someone has to.

How do we take a prototype to production?

We start by looking at what you've built, together, and keep everything that's good: often the idea, the flow and a fair part of the code. Then we rebuild the parts that carry risk, like sign-in, data and permissions, with the tools we use every day: Nuxt, Vue, TypeScript, Node.js and MongoDB. It runs on our own cloud servers in Barcelona, with backups and monitoring, and we keep looking after it once it's live.

If you've built something with AI and want to take it to production, write to us at hello@thosekids.studio or call +34 685 822 339.

← Back to the list