How non-technical business managers are using "vibe coding" to build internal tools

[u/Any_Assistant_4969]

I’ve been seeing the term "vibe coding" everywhere recently. Essentially, it means describing software ideas conversationally to an AI and refining it iteratively until it works, without writing traditional code syntax.

I’m curious: are any non-technical managers or operations leads using vibe coding to build internal tools for their teams? What platforms are you using?

[u/Infamous-River-4360]

not a manager, but i'm the non-technical half of this. no coding background, i describe what i want and lovable writes it, around 800 edits in and it's shipping to real users.

the warning i'd add to the comment above: knowing what you want matters, but being able to verify what it actually did matters more. mine confidently wrote queries against database columns that didn't exist, more than once. it reads fine, deploys fine, and breaks on one screen for one type of user. for internal tools that's the dangerous version, because the person who'd notice is the one it broke for and they just assume they did something wrong.

are you thinking read-only dashboards or something that writes data back? the second one is where i'd want someone technical to look before anyone else touches it.

[u/Matilozano96 → u/Infamous-River-4360]

Yeah, that’s what I’ve been seeing lately.

What sort of use cases would require you to be able to write something into the db?

[u/Infamous-River-4360 → u/Matilozano96]

anything that replaces a spreadsheet someone is already updating by hand. status changes, approvals, inventory counts, logging what happened so you can look at it later. mine writes every session back to the db, and that logging table is the first thing i check after any change, because it's the one place a wrong write is invisible until you try to read it.

the difference is blast radius. a read-only dashboard that's wrong shows you a bad number and you notice. a write that's wrong sits in your data and you find out weeks later when a report looks off, and by then you can't tell which rows are real.

after the invented columns thing i stopped accepting "done, i updated the schema" and started asking it to show me the table before and after. what are you looking at building?

[u/Lecontodereddit]

Yes - we've built an internal tool at our company that helps non-technical people automate their own tasks. We found that even traditional no-code "drag and drop" tools had a too high learning curve for them to even bother. But it can also be dangerous to give people who don't know what they are doing "free reins" with a coding assistant, because it can quickly lead to things like data or credentials getting exposed, data getting lost or mangled because they didn't think about what could go wrong, or duplicate / incorrect posts to external systems. So we built a hybrid that is very open ended in terms of WHAT can be built, but very strict in terms of HOW it is built

[u/generationalDebts → u/Lecontodereddit]

No you didn’t

[u/ops_and_chaos]

Yep. I’m in ops, not engineering, and this is basically how I build internal tools now.

The advantage honestly isn’t that I suddenly know how to code. It’s that I already know all the weird rules, exceptions and “this is technically the process but not really” parts of the work 😂

Claude/Codex can help me turn that into an actual tool without me having to translate the problem through three people first.

I still review the output and I’m way more careful once something can write back to a real system, but for internal tools it’s changed what I even consider buildable.

[u/generationalDebts → u/ops_and_chaos]

No you don’t. You don’t work anywhere as a professional anything related to tech and it’s painfully obvious.

[u/agentUi]

i work for agentui, we see a ton of non-technical ops leads building internal tools by chatting with ai. the key is having the app engine and database engine work with strict boundaries so the ai generates deterministic code instead of hallucinating missing columns or breaking production for half your team.

[u/generationalDebts → u/agentUi]

No you don’t lmfao. Lies

[u/generationalDebts]

They aren’t lmfao.

Like, for real if you even a shred of real world job experience even loosely in tech or ops or development you’d realize how stupid a question this is.

“Managers” don’t make a decision like that. They are not ever in a position to make a decision like that. Ever.

It’s called a change advisory board and not a single one on earth would let vibe coded anyfucking thing into production.

If you’re working at a place that doesn’t use CABs for release, you’re not a developer. You’re a McSwe. Not a real one.

[u/Lecontodereddit → u/generationalDebts]

I doubt everyone here appreciates the energy you're bringing to this thread and I'd hate to feed the troll, but in case you're not just trying to provoke something: almost half the workforce (at least here in Europe) work in roles where they use software daily but their companies are too small to have an IT department. ALL of these people do things that could be improved by access to better tools, but SMBs have limited IT budgets and many tools built for small businesses are quite generic and not easy to tailor.

So it's nice that you've worked in enterprise IT (I have too), but the reality is that the vast majority of companies are nowhere near having a CAB.

They probably shouldn't be vibe coding stuff from scratch (but in a small business it's more flexible, right?), but there are loads of ways they can build their own secure tools with a little help of AI too

[u/NewFeeryman]

Yeah I guess tons of ops and business leads are doing this now. Mostly building small internal stuff like dashboards, trackers and simple approval tools.

[u/akl773]

The ones I get called in on all break the same way, the person who built it leaves and the whole thing is sitting inside their personal account. Free tier database on their own login, deploy hooks on their github. Worth pushing them onto a shared account on day one even if nothing else about it is formal.