What May Require Additional Development?

Additional development may be needed when an important requirement cannot be handled well with existing Booking Ninjas features, normal configuration, or a standard integration approach.

The first step should not be “build something new.” The team should first check what already exists, what can be set up, and whether another system can handle part of the need. Only then should new code or a new custom function be considered.

What Should Be Checked Before New Development?

CheckSimple QuestionPossible Result
Existing featureDoes Booking Ninjas already support the main need?Use the existing feature.
ConfigurationCan fields, rules, pages, permissions, reports, or workflows handle it?Set up the platform without new code.
IntegrationShould another system keep doing this job?Connect the systems instead of rebuilding the same function.
DevelopmentIs the need still not covered after those checks?Review a custom build.

This is the same basic difference explained in Configuration vs. Customization.


What Kinds of Needs May Require Development?

  • Special business logic. A rule or calculation that standard settings cannot handle cleanly.
  • A new user experience. A screen or action that needs behavior beyond the existing interface.
  • Complex integration behavior. A connection that needs special logic for timing, matching records, errors, or two-way updates.
  • Unique automation. A process that needs a special action that existing workflow tools cannot provide.
  • A new function that does not exist yet. The business need is valid, but the current product does not cover it.

The exact answer depends on the requirement. A request that sounds unusual may still be possible through normal configuration.


Why Not Build Custom Code First?

Salesforce provides many point-and-click tools for changing objects, fields, processes, pages, and apps without code. Salesforce also provides code when deeper changes are needed.

Using existing tools first can keep the setup easier to test and maintain. Custom code is useful when there is a clear reason for it, but it also becomes another part of the system that must be designed, tested, deployed, and supported.

Simple rule

Do not build a new function just because the current screen looks different from the old system. First ask what result the user actually needs.


How Should a Custom Request Be Reviewed?

  1. Describe the business problem. Explain what the user cannot do today.
  2. Check current features. Review Booking Ninjas Features before assuming something is missing.
  3. Check configuration. See whether the result can be reached with settings and workflow tools.
  4. Check integrations. If another system should stay involved, review Integrations.
  5. Estimate the extra work. Include design, build, testing, training, and future support.
  6. Decide when it is needed. A good idea can still belong in a later phase.

Can Additional Development Be Added Later?

Often, yes. If the first usable version can work without the custom function, the team can move it into a later phase.

If the first process cannot work safely or reliably without it, the custom work may need to stay in the first scope. This is why new requests should be reviewed through the same process described in What Happens When New Requirements Appear?.


How Does Development Affect Cost and Time?

New development usually adds work because the team has to design, build, test, deploy, and later maintain something that was not already part of the standard setup.

For the wider cost factors, see What Affects Implementation Cost?.


Sources and Further Reading

Sources support the general difference between configuration and development. Whether a specific Booking Ninjas request needs development depends on the agreed requirement.

Next Steps

WhatsApp Us

WhatsApp Us