So we thought: let's add a bot.

But before jumping in, we asked ourselves the real question — will this make our project more maintainable, or a nightmare?

Because the last thing we wanted was a bot so tightly coupled to our codebase that every FAQ update needed a redeploy. That's not sustainable for a side project. That's just creating more work for yourself.

So we set a constraint early: integrate once, update independently.

That one constraint led us straight to Typebot.

Getting started was almost suspiciously easy.

Typebot gives you templates out of the box. We picked a simple FAQ one, tweaked the questions to match our app, and hit publish. Then we grabbed the embed script, dropped it into our app — one time — and that was it.

No new component. No state management. No API to wire up. Just a script tag.

And the best part? That was the last time we touched the app for anything bot-related. Need to add a new FAQ? Go to Typebot, update the flow, publish. Done. The app has no idea anything changed — and it doesn't need to.

For a side project, that's huge. You're not always in "deployment mode." Sometimes you just want to update a line of text without spinning up the whole pipeline.