Build it yourself. Have it checked.
Describe the change the way you would say it to a colleague. It writes the app, builds it and puts it in your own sandbox to try. Then you say what is wrong, and it goes round again.
Follow a lap
You describe it in a sentence
No syntax, no field numbers, no template to fill in. You say the rule your company works by, and it goes and finds the pages and setup that rule belongs to.
The errors are its problem
It compiles the app against the symbols in your own environment. When the build fails, the failure goes back to the agent rather than to you: one button, and the list is there only if you want it.
You try it on data you know
It publishes into a sandbox copy of your own environment, so you try the app on orders you recognise. Reading a description tells you nothing; releasing a purchase order tells you everything.
Wrong costs three minutes
Say what is wrong in the same plain words and the lap starts again: rewritten, rebuilt, back in your sandbox. You leave the loop when you stop having corrections, and what you leave with is a change your consultant reviews.
Sales approvals
YOUR WORDS
What should change in Sales approvals?
Nobody should be able to approve a purchase order dated in a closed period.
Ideas
- Add a field to the customer card
- Create a report of open sales orders
- Add an approval step to purchase orders
How it works
- Together
- Plan first
- On its own
Start
It asks when it is unsure, and you decide when it is done.
It works in a copy of your environment. Nothing it writes can reach production.
Why you can use this without being a developer
- It asks, it does not assume
The questions come to you in your own language
Where a rule could go two ways, the session stops and puts the choice in front of you as a sentence with two answers. You are being asked a business question, which is the only kind you should have to answer.
- Wrong is cheap
A lap costs minutes, not a sprint
Each session runs under a euro budget you set before it starts, and the spend is visible while it runs. Going round again costs another few minutes and a few cents, which is what makes it worth trying the idea before anyone writes a specification for it.
- It does not stop at easy
The same project your consultant works in
Plain language is the way in, not the ceiling. Underneath it is a full Business Central development suite in your own repository, so the prototype you started is the thing your consultant finishes. Nothing is rebuilt to make it real.
Bring the thing you have been asking for since last year
Not a toy. The useful test is the small app your team has wanted for months and nobody has had time to build.
Or write to us at hello@uni4c.ai