Selecting a Systems Approach to the Solution of a Business Problem
Welcome to this guide on selecting a systems approach! When a business faces a problem—such as slow order processing, poor inventory tracking, or managing customer bookings—software is usually the answer. However, deciding how to acquire that software is one of the most critical decisions a business will ever make.
Should they write their own custom software from scratch? Buy a ready-made package? Or adapt something that already exists? Making the wrong choice can waste time, blow budgets, and disrupt daily operations. Let’s break down the different approaches and learn how to choose the right one for any business scenario.
1. The Three Main Systems Approaches
Think of getting software like getting an outfit for a formal event. You can buy one straight off the rack at a department store, have a tailor make one entirely from scratch to your exact measurements, or buy a store outfit and pay a tailor to alter the sleeves and hem. Software acquisition works in a very similar way!
Approach A: Off-the-Shelf (Packaged / COTS)
Commercial Off-the-Shelf (COTS) software is pre-built, ready-made software created by a third-party vendor and sold to the general public or businesses (e.g., Microsoft Office 365, Sage Accounting, QuickBooks).
• Analogy: Buying clothes off-the-rack. It is ready immediately and cheaper, but it might not fit every curve perfectly.
• Key Advantage: Available immediately with lower initial purchase costs and proven reliability (since many other companies use and test it).
• Key Disadvantage: May contain unnecessary features (bloatware) or lack unique features that your specific business requires.
Approach B: Bespoke (Custom-Built / Tailored)
Bespoke software is custom-designed and developed specifically for a single client or organisation to meet their unique business requirements from the ground up.
• Analogy: Visiting a tailor to get a custom suit made from scratch. It fits you flawlessly, but it takes time and costs significantly more.
• Key Advantage: Tailored precisely to business workflows; provides a distinct competitive advantage because competitors cannot buy it.
• Key Disadvantage: High development costs, long delivery timescales, and the business carries all risks for ongoing maintenance and bugs.
Approach C: Customised Off-the-Shelf (Hybrid)
Customised COTS starts with standard, pre-packaged software and modifies, extends, or configures it (often using built-in scripting, plugins, or APIs) to better match specific business workflows.
• Analogy: Buying a suit off-the-rack and paying for alterations to fit your measurements.
• Key Advantage: Faster and cheaper than building from scratch, yet more adaptable than plain off-the-shelf software.
• Key Disadvantage: Future software updates from the original vendor might break custom modifications, leading to unexpected maintenance costs.
Quick Key Takeaway: Choose Off-the-shelf for standard tasks and quick deployment, Bespoke for unique business operations needing a competitive edge, and Customised COTS for a middle-ground compromise.
2. In-House vs Outsourced Development
If a business decides to develop bespoke software or heavily customise an existing platform, they must decide who will do the work.
In-House Development
The company uses its own employed software engineers, analysts, and testers.
• Benefits: Complete control over the project; developers already understand the business culture and existing systems; immediate post-launch support is on-site.
• Drawbacks: Expensive to recruit, train, and retain specialist developers; takes internal staff away from other daily IT tasks.
Outsourced Development
The business hires an external software consultancy or software house to build the system under contract.
• Benefits: Gives access to specialist skills that the business lacks; no need to hire permanent developers; costs are often fixed in a contract.
• Drawbacks: Risk of poor communication; loss of direct control over daily development; risk of vendor lock-in where the external company charges heavily for future changes.
3. Key Evaluation Criteria for Choosing an Approach
When answering exam questions on which approach a company should pick, evaluate these six key decision factors:
1. Cost and Budget
• Off-the-shelf software has low initial acquisition costs (often subscription-based or flat licence fee), whereas bespoke software requires a large capital investment up front.
• Don't forget Total Cost of Ownership (TCO): Training, data migration, ongoing support, and future upgrades all add to long-term costs.
2. Timescale and Urgency
• If a business needs a solution immediately (e.g., to meet new legal compliance standards next month), off-the-shelf is the only realistic option.
• If a business can wait months or years for a long-term solution, bespoke development is feasible.
3. Uniqueness of Business Requirements
• If the business processes are generic (e.g., standard payroll, email, tax calculation), existing packaged software handles these well.
• If the company has unique processes, proprietary algorithms, or wants to offer exclusive customer features that competitors lack, bespoke is essential.
4. Internal Technical Expertise
• Does the company have skilled software developers and project managers on staff? If not, building in-house bespoke software carries a high risk of failure.
5. Integration with Legacy Systems
• A business may already run older databases or specialised machinery. Bespoke software can be engineered specifically to link directly into these existing legacy systems, whereas standard off-the-shelf packages might not integrate easily.
6. Support, Maintenance, and Control
• With off-the-shelf systems, the vendor provides bug fixes and updates, but the business has no control over when features change or if the product is discontinued.
• With bespoke systems, the business owns the source code and controls the roadmap, but must pay for or perform all repairs and maintenance themselves.
Memory Aid — Use the Mnemonic "CUTS-IT":
• C - Cost (Budget & TCO)
• U - Urgency (Timeframe)
• T - Tailoring (Unique requirements)
• S - Skills (In-house expertise)
• I - Integration (Legacy compatibility)
• T - Total Control (Support & maintenance)
4. Comparison Summary
Off-the-Shelf Solution
• Cost: Low initial cost.
• Implementation Time: Immediate.
• Customisation: Very limited.
• Best suited for: Standard business functions (e.g., accounting, word processing, standard retail POS).
Customised Off-the-Shelf Solution
• Cost: Moderate (licence fee + development time).
• Implementation Time: Short to medium.
• Customisation: Moderate.
• Best suited for: Businesses whose processes are mostly standard but need specialised report outputs or minor workflow tweaks.
Bespoke Solution
• Cost: High initial and ongoing development cost.
• Implementation Time: Long (months or years).
• Customisation: 100% tailored to requirements.
• Best suited for: Niche businesses, highly complex workflows, or creating unique market differentiators.
5. Common Mistakes to Avoid in the Exam
• Mistake 1: Assuming bespoke is always better. Many students argue that bespoke software is always superior because "it does exactly what the user wants". Remember to balance this against the immense cost, long development delay, and high project risk.
• Mistake 2: Forgetting long-term maintenance. Buying software is not a one-off expense. Off-the-shelf software requires recurring subscription/licensing fees, while bespoke software requires dedicated engineers on standby to patch bugs and handle operating system updates.
• Mistake 3: Overlooking vendor lock-in. If a third party builds your custom solution or hosts your data in a closed, proprietary format, you may be trapped paying high fees whenever you need updates or migration.
6. Step-by-Step Problem-Solving Guide for Exam Scenarios
When given a case study in an exam question, follow these steps to select and justify the best approach:
Step 1: Identify the constraints
Look closely at the scenario. Is there a strict budget limit? Is there a hard launch deadline? Note them down.
Step 2: Assess the uniqueness of the problem
Is the company doing something completely new, or are they managing everyday operations like bookings, invoicing, or payroll?
Step 3: Evaluate existing internal resources
Does the case study mention an IT department with programming experience, or is it a non-technical small business?
Step 4: Make a justified recommendation
State your chosen systems approach clearly. Justify your choice by pairing the business's specific needs with the strengths of that approach, and explain why the alternatives were rejected.
Key Takeaway: High-scoring answers do not just list definitions; they weigh advantages and trade-offs directly against the context and constraints described in the business scenario.