A package puts a need shared by many firms into a menu. Custom software starts when your rule is not on that screen. Writing code because a package feels “short”, or building a whole system for every rule, both get expensive. In a custom software discovery, Ayyıldızsoft first writes which step the package cuts.
If stock, sales and purchasing already run in a package, the talk is ERP If a field team will enter data from a device, a mobile app is a separate scope. Do not hide either inside the custom software sentence.
Where the package is enough
- The rule can be chosen on a settings screen
- The report comes from fields that already exist
- The user count sits inside the license
- The integration uses the package’s own connector
Where custom software starts
If an exception is fixed by hand on every order, that exception is a rule. No screen is drawn before the rule is written. Development does not start before the drawing is accepted. Maintenance is in scope too: a package upgrade can break your module at the same time.
The sentence “it will be customized a bit” can drop the package support contract. Do not start before that is written. For the meeting, see the Konya software company note. Related: stock count before ERP.
- Write the missing step in one sentence
- Ask if a setting already solves it
- If not, lock input, output and the exception
- Ask whether package support will drop
