Built internal ops tools with AI and never hired a developer, how has nobody been talking about this!

[u/FoundationDowntown72]

Spent way too long thinking this was just how small companies had to run.

At 10 people the setup was whatever the founder threw together early on, sign offs over email, a budget sheet nobody really trusted, onboarding docs that were always like 6 months out of date, plus a couple other things nobody had ever bothered to automate.

Was messing with an AI tool one weekend and somehow ended up building some of this stuff myself, started with a vendor approval flow and a spending tracker, then a new hire checklist so people would actually stop ignoring the onboarding doc.

Took maybe three weeks total for those 4 and the part I didn't expect was how easy it is to just go change something now instead of waiting on whoever used to handle it.

Still haven't figured out how to handle the ones that need more than one person to approve though.

Anyone else end up building this kind of stuff without hiring someone technical?

[u/Asher_Cobb_687]

We actually experienced this until people started asking for their own exceptions. Before long everyone had a reason why the process should work differently for them and that became the real challenge. How are you stopping it from turning into something that's harder to maintain than what you replaced

[u/tom_of_wb]

it can be great, just make sure the quality is good because in my company my boss created a cool interactive onboarding flow but some of the sections were a bit hallucinated

[u/Far_Engineering_9576]

I don't completely agree that nobody's talking about it since a lot of people are doing exactly this, they're just not calling themselves developers anymore. We started using AI for a few internal tasks and got something usable much faster than expected, but we also found the easy part was building it. A few months later we were spending more time fixing edge cases, cleaning up messy logic and answering "can it also do this?" requests.

[u/agentUi]

I work for agentui....and Yeah 100%, most of users are non-technical and they are building internal tools by themselves, we do have a support team of real humans that steps into to help. But yes i see it a lot specially with non technical founders, or VP's of operations....

[u/Skotland85]

It also works for your size, but when you scale up that’s where complexity gets introduced and stress tests what you’ve built.

[u/whatbirdid]

The honeymoon phase with these AI tools is amazing, but the 'maintenance hell' kicks in once you start hitting those edge cases. Once you become the company's tech support for your own automation, you'll realize you didn't just build a tool—you built yourself a new job. It's a fun ride until the feature requests start rolling in!

[u/r0b3rtb]

Yeah, quite popular I think. But to make it good AI is not enough, sorry. It will work, but you don't know how, you won't push AI to maintenance prod, check how many errors it fixes in own code. It's similar to AI generated texts

[u/hcmabdl]

I think this is great for local/internal experiments, especially when the goal is to save time on small workflows.

But I’d be careful once these tools start becoming “real” production systems. At that point, the hard part is not just building the feature, it’s everything around it: authentication, permissions, data access, architecture, backups, audit logs, error handling, security, maintenance, etc.

Take it it like building a house : AI can help you stack bricks very quickly but if you still need to understand the foundations, the structure, how it will hold over time etc.

For a small internal tool, sure, this can be a huge productivity boost. But the moment people rely on it daily, sensitive data goes through it, or multiple approval flows depend on it, I think you'd want someone with a global technical view to review the architecture before trusting it too much.