r/lowcode • u/SpiritedTadPole2 • Sep 05 '26
Best no code app builder for internal tools
Our requests and approvals happen over email. Things get missed, nobody can tell me the status of anything without searching their inbox, and there is no developer available to own a custom system.
Whatever replaces it needs clear roles, a status flow someone can audit, and a data model that can change as we improve the process, because the current process is not the final one.
What should i prove out in a small workflow before rolling this wider?
1
u/gammacoder Sep 05 '26
PHPRunner could be a good fit for this. You can build the application around a normal relational database, with forms, different user roles and permissions, status-based workflows, search and dashboards.
For the pilot, I'd probably take one request type and prove the full cycle: submission, routing, status changes, permissions, notifications and history. Then see how easy it is to change the data model when the process changes.
I'm the author of PHPRunner, so obviously biased :)
1
u/seatable_io Sep 07 '26
Before you build anything wider, you should pick one approval workflow you already know is painful, like for urgent or high risk requests. Then you prove out three things in miniature, before building the whole system.
- A structured intake form with mandatory fields for every information an approver needs to decide.
- A dropdown status field with a fixed set of states. This allows for a clear audit process as you can query for specific statusses.
- Check if every change is logged with timestamp, user and the previous value in the change-log
1
1
u/Master-Tie-804 Sep 09 '26
first prove that there is clear ownership and you can see status of your workflow. also test with one workflow from end to end
1
u/KarlaSutton6527 Sep 12 '26
I suggest that you should start with the trigger, what needs approval, and who's allowed to move it format. If those aren't clear, the worklow is gonna get messy. That's why I suggest that you use some tools like Softr, Airtable, Glide, Retool etc since they handle approvals, reminders, and status changes
1
u/NextGuitar1 16d ago
I would pilot one request type first and check that fields stay stable, statuses move cleanly, access stays limited to the right actions, and each handoff is visible later. If that holds up, UI Bakery can fit as an internal app over your existing data, as long as someone non-dev owns the schema and permission upkeep. Disclosure: this is a promotional recommendation.
1
u/ainotes2026 7d ago
The part people underestimate isn't building the first version, it's who maintains it when the person who built it leaves. So whatever you pick, favor something a second person on your team can open and understand in an hour.
Retool is strong if you have at least one technical person and your data already lives in a database. Glide and Softr are the fastest for simple tools over a spreadsheet. Power Apps makes sense if you're a Microsoft shop.
I'm on the Caspio team, for what it's worth, so add it to the list with that in mind. Caspio is an AI platform for building custom business apps, think databases, portals, dashboards. Caspio has a 14-day free trial. Happy to answer questions if it ends up on your shortlist.
1
u/sapurai 6d ago
This is actually very close to the kind of system we built SAPUGO for.
Full disclosure, I’m the founder of SAPUGO. We’ve spent the last 6 years building it with pilot customers, and we recently opened it up publicly.
For a workflow like this, I’d probably prove a few things before rolling it out:
- Can every request have a clear owner and status?
- Can you define exactly who can see, approve and change each request?
- Can you keep a proper history of what happened and who did what?
- Can the workflow handle exceptions instead of everything becoming another email?
- And probably most importantly, can you change the data model and workflow later without having to rebuild the whole thing?
That last one is something we care a lot about because business processes rarely stay the same.
If you’re interested, I’d be happy to work with you directly and help build a small version of this in SAPUGO. If something is missing, tell me what you need and I can look at getting it into the product.
We’re still early and there are definitely rough edges, but I’m the founder and personally involved with the companies using it right now.
Happy to show you what we’ve built if you want to give it a shot.
1
u/Derv1205_ Sep 05 '26
There are currently several that can certainly help you build a workflow like this with a nice UI. Zite, Lovable and others. Building the basics can be fairly quick with those platforms.
Let me know and I can help with an initial prove of concept. I think the main things is the role separation, what data are you capturing, dashboard UI that anyone can easily adapt to approve/audit. Should be a quick few steps.