Approvals nobody can find
A new machine, a laptop, a trade fair: anyone who wants to order something sends an email, asks in the hallway or fills in a template that lives somewhere. Later, it's hard to tell who approved what. Every company has its own rules for this, and that's exactly why no standard tool quite fits.
A fictional example: at Keller & Sons, Anna, head of purchasing, handles purchase requests. She wants a clear path: who requests, who approves, and from which amount management has a say.
Describe
Anna describes in her own words how it should work:
"Employees submit purchase requests with an amount and a reason. Their manager approves. From 5,000 euros, management must approve as well. Requesters see only their own requests, purchasing sees all of them."
A build agent builds the app from that. No code, no IT ticket, no agency. And no workflow click-through: the result is real software with a data model, permissions and tests that reflects exactly your rules.
Answer the domain questions
Openbase.one only asks what Anna has to decide as the expert:
- "What happens when a manager is on vacation: does the request wait, or does a deputy approve?"
- "Can managers approve their own requests?"
- "Is the 5,000 euro limit net or gross?"
These are the questions every company answers differently. The team sets the answers, not a standard process.
Checked before it goes live
Every version is built and checked before it goes live. The data model and access rules are checked, and records are classified. Every page is opened in a real browser as every test persona:
- as an employee: only own requests visible, no approving
- as a manager: approve requests from their own team
- as management: approve requests from 5,000 euros
A version goes live only when the check passes.
Live, on the go too
The app runs isolated in the workspace, and every access is checked against workspace, app and permissions. The audit log shows who changed what. Approving works in the app for iPhone and Android too, because your own apps run there natively. The personal assistant can look up waiting requests with the person's permissions, and brings every change for approval.
HR can build a vacation request app the same way, with its own rules for deputies and remaining days.
Change it later
The limit goes up to 10,000 euros? Anna describes the change, and the new version is checked again. Every version is kept, and the previous one is live again in one click. Code and data belong to you: a git repository in the workspace, data exportable.
Whether your approval rules are right in substance is your call. A support contract helps, and can include a review of new apps before they go live.
What it costs
One price per workspace, no license per app and none per person. All plans are on the pricing page.
Describe your first app and watch it go live, checked.
Start for free