Sound advice from the folks at Trizle

You have two choices:

• Option A: Build a state-of-the-art, custom-built enterprise system that integrates the works (e.g. CRM, ERP, EAM, SCM, wiki, etc.).
• Option B: Get something up quickly. Combine many smaller pieces of independent applications, and have them communicate with each other (e.g. through their APIs, etc.).

Mr. Techno-Wizzo tells you:

Option A:

• takes frickin' long to build (years, if ever)
• has a humongous chance for failure
• its modules become obsolete quickly
• you drain revenues fast while it's under development
• painful to tweak things as your business changes
• if you ever finish, you'll probably outgrow many of its features

Option B:

• quick, and flexible — can get something up freakishly soon
• causes slight dents to your cashflow, as you get an application module up quickly to use
• allows you to use best-of-class for every included application
• interchangeable (e.g. a state-of-the-art applications can be integrated into the system easily and continuously)

Option B = winner! Yay! Yay! Yay!

Read more