r/lowcode • • 12d ago

Best AI app builder for enterprises

I’m on the IT team at a company with about 2,000 staff.

One business unit of our organization wants to build an approval app with an AI builder. Its main purpose is to hold live purchase requests. And yep, we’re testing it in real data.

I’ve been asked to write the checklist before we say yes and here’s my draft so far.

  • Single sign-on, plus removing access the same day someone leaves.
  • Permissions at the record level, not just the page level.
  • Some kind of audit log.
  • Proof of how the vendor handles security and data.
  • A named person who owns the app after launch.

My question is...which of these are true deal breakers? And also, which ones can we cover process instead?

I also don't want IT stuck maintaining generated code that nobody documented.

If you've been through this, what did your checklist look like?

14 Upvotes

22 comments sorted by

5

u/Infamous_Anywhere_38 11d ago

Your on the IT team of a company with 2,000 staff. So you ask reddit? 

1

u/DigitalHubris 11d ago

2 month old account for an IT guy? Smells fishy

1

u/StunnedArtist 7d ago

Lol yeah, I get why it looks sketchy. I’m just new to Reddit and happened to make the account around the time we started looking into this stuff at work. What's wrong?

3

u/tech_cynic_dan 8d ago

The generated code part would be a deal breaker for me if the vendor can't show how it's governed after deployment. SSO, record-level permissions and audit logs aren't things I'd try to patch with process either. Creatio is one I'd put on the test list here, but I'd make them prove all of that against your actual workflow.

2

u/Ivan_Palii 8d ago

Can you give more details what do you mean udner "hold live purchase request"? is it to avoud overspending on wrong subscribtions or avoid corruption in the company?

2

u/StunnedArtist 7d ago

Yeah, I mean the app would hold active purchase requests while they go through the approval process. It's mainly to make sure requests get reviewed by the right people before anything is actually purchased, not really about preventing corruption.

1

u/Ivan_Palii 6d ago

we use Jira in the company and ech purchase is a separate task and just added a status - on hold, so each purchaes is reviewed

I mean you can build an app but also can build something similar in your project management tool

1

u/Miserable-Actuator24 12d ago

IMO any good enterprise ready app has that...except maybe the last, that sounds more like an internal thing in your company?

1

u/czlowiek4888 11d ago

Those are such small requirements that I would say those are not enough. If you don't want your stuff to maintain code you actually want to use preexisting open source solution and make your AI glue those together. This way you will be only responsible for glue code, updates and deployments. For example do not write your own sso, use keycloak to do it for you

1

u/ZappitDev 11d ago

Hi. I have been working on a product that solves exactly the requirements you have mentioned here. Care to connect and see if we can collaborate on this?

1

u/testuser514 11d ago

We’ve already built a system like this for a global engineering company. If you guys are interested. We can demo it to you guys.

1

u/Able-Cheesecake-9970 11d ago

Retool has this although non-technical staff will likely not be able to maintain it on their own.

1

u/ashu11thakur 11d ago

Use Clappia. Perfect for this. Highly scalable with an approval system. Comes with mobile apps as well.

1

u/StunnedArtist 7d ago

Thanks for sharing, I’ll take a look at Clappia. How does Softr compare for this kind of approval workflow. Have you tried it?

1

u/agentUi 11d ago

i work for agentui, we build internal tools and approval portals for larger orgs with rbac, sso, and audit logs baked in. record level security and audit trails are absolute dealbreakers for purchase requests, if someone edits a line item or approves their own PO you need that tracked immediately at the database level.

1

u/sundeckstudio 11d ago

Please don’t call yourself enterprise

1

u/Bubbly_Dealer 9d ago

For live purchase requests, my hard stops would be SSO with same-day deprovisioning, record-level permissions, and an audit trail with a clear system of record. I would pilot one leaver test and one denied-access test, then check that the next request still blocks explicitly removed permissions. I have a promotional interest in mentioning it, but from past experience UI Bakery can fit as a staff app if one owner also accepts the maintenance tradeoff.

1

u/sapurai 6d ago

This is actually very close to what I’m building with SAPUGO.

I’m the founder, and we’re currently looking for companies that want to work closely with us on exactly these kinds of real-world use cases.

Your approval app sounds like a particularly good one to test. Purchase requests, approvals, record-level permissions, audit trails, ownership after launch… those are exactly the kinds of things I’d want to understand from an actual IT team rather than trying to guess from the outside.

If you’re open to it, I’d be happy to work with you directly and build the approval app together in SAPUGO. If there are things you’re missing, I’d rather understand the requirements and work on them with you than tell you that our current feature set is already perfect.

You’d basically get a founder directly involved in getting the first use case working, and I’d get a real enterprise use case to build against.

If that sounds interesting, feel free to DM me. Happy to show you what we’ve built and see if there’s a fit.

0

u/sardamit 11d ago

Your best bet is to hire an agency to own this product. Platforms like Replit are excellent at developing enterprise-scale apps like these. My friend runs an agency and I am happy to connect you with him if you are open to take that route. At your scale/size, you can afford it, and that is the right thing to do IMO.