Bespoke vs. SaaS

Both have their pros and cons. In the basic sense, bespoke allows for increased customizations through changing the underlying core code of the software. Whereas SaaS platforms adapt to your requirements using the existing configuration options without changing the underlying core code which allows leveraging economies of scale.

While it may be appealing to having a granular level of control over your software with a bespoke solution, it may be unnecessary, or when slightly modifying your existing internal processes could mean the difference of using SaaS instead. The advantage of using SaaS will significantly lower or reduce the overheads compared to a bespoke system in time, costs and other resources.

	Bespoke	SaaS
Implementation times	6 - 12 months	2 - 6 weeks
Implementation resources	Intensive	Streamlined
Costs	$50 - $150k	Under $10k
Replacement	Every 4 - 5 years	Never
Support requirements	High need	Reduced need
Upgrade cost	Cost per enhancement	Included
Upgrade frequency	As requested	Weekly or monthly
Infrastructure	Basic	Enterprise

 

When to use Bespoke Software

It's obvious that no two organisations are ever truly alike. There may be many common challenges or requirements across many associations in which a SaaS solution will aim to address. However, a SaaS solution may only meet 90 - 95 percent of your overall needs. If you have both the initial capital, and ongoing resources then closing that gap with the last 5 - 10 percent can be an option. Bespoke gives you that granular level of control, but at the trade-off of significantly increased upfront and ongoing expense.

Many organisations also unintentionally pursue bespoke solutions without realising there are now more viable options available. Often, they begin with off-the-shelf software, but either initially or over time they 'tweak' the existing code to better suit their current workflows (rather than adapt internal processes to the platform), add custom modules, or create custom integrations to link the multitude of software components. This overall system becomes unique to your organisations and creates very complex software cross-dependencies making upgrading or enhancements more resource intensive (and costly).

When to use SaaS solutions

SaaS suits those organisations that don't operate with unique internal processes or don't have the budget for the upfront and ongoing development costs to sustain a bespoke solution adequately. SaaS will eliminate many of the random costs associated with bespoke or custom software that crop up due to bug fixes or feature enhancements - allowing organisations to more confidently plan and budget appropriately.

Frequent enhancements with SaaS ensure continuous improvements to workflows, communication, member engagement, security and reliability. SaaS also eliminates the typical major upgrade periods compared to bespoke around the four to five year period where the system becomes out-dated or "clunky".

Conclusion

In the same way as you could buy a house off the plan with configuration options OR approach an architect to have a house Custom designed and built to your specific requirements. Software can now be obtained in a similar sense, with SaaS being similar to off the plan with configuration options, and Bespoke being a custom designed and developed solution. Both have their merits and costs, it is just a case of determining which is most suited to your objectives and needs.

Read More

• What is the difference between an AMS and CRM?
• Importance of an Open Ecosystem over Closed Ecosystem AMS
• Maximum Design Flexibility
• Association Software Pitfalls - Making the right Choice
• Engage with Your Members