Build, buy or generate on IFS Cloud
Three ways to close a gap in IFS, and how to choose.
The short answer
Build what is strategic, buy what is common, generate the rest.
Three ways to close a gap
Sooner or later, standard IFS and the business disagree. There are three ways to close the gap.
| Way | Fit | What it costs you |
|---|---|---|
| Build it by hand | Exact | Time and scarce IFS skills |
| Buy an add-on | Close, rarely exact | A process bent to the tool |
| Generate it | Tailored to you | A person’s review of the code |
How to choose between the three
Most backlogs land in the third row, where generating pays back.
-
Strategic and unique
Build it by hand, if the specialist cost is worth it.
-
Common, not a differentiator
Buy it, if a mature product fits closely.
-
Specific to you, needed soon
Generate it beside IFS, through its official interfaces.
Questions IFS teams ask
Does generating apps create technical debt?
Less than deep customisation does. Generated apps connect through official IFS interfaces and change nothing in the core, and a person reviews every change before it merges, so the code is read as well as written.
Can IFS partners use this for client work?
Yes. A partner can generate a custom app for one client and adapt the brief for the next, which turns one-off builds into assets the partner can offer again.
Do we still need developers?
Yes, for the work that is truly unique and for review. A person reviews all AI-written code before it merges, and secret scanning and static analysis run on every commit.
Describe a gap in your IFS
One sentence is enough to start. We build the app with you on your IFS test environment.