Two low-code platforms can both display your request form. One lets a requester change the amount after approval. The other ties approval to the submitted version. That difference matters more than which demo has the cleaner dashboard.
Once you have decided to build an internal app, compare platforms against the transaction your business must protect. Use the same requirement, users, and exception on each candidate. Leave the broader question of whether you need an app to the spreadsheet-to-app decision.
Write the test before the demo
The following hypothetical requirement concerns equipment purchase requests. A requester submits an item, amount, reason, and department. A department manager approves a specific version. Finance records the purchase only after that approval. An administrator can repair an import error but cannot rewrite the approval history.
Give each vendor or builder this same acceptance script. Ask them to show the result inside the system, including the underlying records. A narrated slide about role-based access does not establish what the product does.
| Test | Expected behavior | Evidence to keep |
|---|---|---|
| Requester edits an approved amount. | The app requires approval for the changed version before finance acts. | Original approval, new version, and blocked finance action. |
| Requester opens another department's private request. | The system denies the read through both the screen and available data endpoints. | Test identity and denied access result. |
| Finance loses its connection during recording. | The app leaves a recoverable state and avoids duplicate purchases on retry. | Failed attempt, recovery, and final purchase record. |
| Administrator exports the request. | The export retains version identifiers, approval actor and time, and final status. | Sample file and explanation of how another tool reads it. |
Distinguish a feature from a workaround
During the test, note which behavior the platform supplies and which behavior the builder adds. A workaround may be acceptable. You need to know who will maintain it when a schema, permission, or connector changes.
For example, Candidate A may require custom code to invalidate approval after an edit. Candidate B may support versioned approvals but offer an export that drops the old versions. Neither earns a pass from the feature list. Ask the builder to resolve the missing requirement and show the revised transaction.
Record the constraint without guessing at its cost: “Approval invalidation requires a maintained custom function” or “Standard export omits approval history.” Obtain an estimate against that specific constraint. Do not compare a subscription price on one side with the whole implementation budget on the other.
Ask the future maintainer to make one change
Have the person who will support the app add a department, deactivate a manager, or change an approval threshold in a safe test environment. Watch where they need developer help. That observation tells you how the app will operate after the launch specialist leaves.
Check what the team must restore after a mistake. An export of current values may not restore relationships, permissions, approvals, and attachments. Ask the builder to demonstrate the recovery needed for this app rather than point to a generic backup claim.
Keep a change record with the edited rule, test result, owner, and rollback method. The platform must support the level of traceability your business requires, whether it does so through native features or a documented addition.
Make a decision the team can explain
Your platform comparison can fit on one page: requirement passed, unresolved constraint, added maintenance, export evidence, estimated implementation work, and designated maintainer. Mark critical failures as unresolved instead of hiding them inside an average score.
If both candidates pass, compare the work your actual maintainers must do and the full commercial terms for the agreed scope. If neither passes, narrow the app or investigate another platform. A successful form demo does not justify accepting a broken purchase approval.
Use our internal tool requirements guide to prepare the transaction brief. The Ops Guide's custom software development service can help turn those rules into an app the operating team can inspect and maintain.

