Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 36 ยท Getting Started

A Short History and the Software Landscape

Follow ERP and CRM from inventory control and MRP to cloud suites, and get a vendor-neutral map of the market: large suites, mid-market products, open source and best-of-breed tools.

Software categories make more sense when you know where they came from. ERP and CRM did not appear fully formed: each grew by absorbing the next problem a company ran into. Knowing the lineage also explains why the market is crowded with products that sound alike but target very different buyers.

This lesson gives a short timeline, the shift from on-premises to cloud, and a vendor-neutral map of today's landscape. Product names are examples only; features and prices change, so always check current information before a purchase.

From inventory control to ERP

The story is usually told in steps:

  1. Inventory control (1960s). Manufacturers wrote programs to track stock and reorder points.
  2. MRP (1970s). Material requirements planning calculated what to buy and when, from a production schedule and bills of materials.
  3. MRP II (1980s). Added capacity planning, shop-floor control and financial planning: manufacturing resource planning.
  4. ERP (1990s). Extended the idea to the whole enterprise: finance, HR, sales and distribution, all on one database. The term ERP became common.
  5. Extended ERP (2000s). Added supply chain, CRM and e-commerce extensions.
  6. Cloud and modern ERP (2010s onward). Subscription pricing, web interfaces, mobile access, embedded analytics and automation.

Growing outwards

Inventory control Count and reorder
MRP Plan materials
MRP II Plan capacity too
ERP Whole enterprise

Each step absorbed the next problem

1 / 2

The CRM timeline

CRM grew from different roots:

  • Contact managers and sales force automation (1980s-90s): address books and activity tracking for salespeople.
  • Customer service and marketing tools: helpdesk and campaign software joined in.
  • Web-based CRM (late 1990s): delivery as a hosted service, an early form of what we now call software as a service.
  • Social, mobile and analytics (2010s): social profiles, mobile apps, dashboards.
  • Intelligence and automation (recent): scoring, forecasting and drafting assistance built into many products.

On-premises versus cloud

Question On-premises Cloud (SaaS)
Who runs servers? You The vendor
Cost shape Large upfront licence, then maintenance Recurring subscription per user
Upgrades You plan and test them Vendor rolls them out
Customisation Deep, often code-level Mostly configuration and extensions
Control over data location Full Depends on contract and region

Many large firms run hybrid setups: finance on-premises, newer modules in the cloud. Chapter 7 returns to cloud and deployment choices.

Market map

Instead of listing products by popularity, group them by who they are for:

flowchart TD
  M["ERP and CRM market"] --> A["Large enterprise suites"]
  M --> B["Mid-market suites"]
  M --> C["Small business tools"]
  M --> D["Open source"]
  M --> E["Best-of-breed specialists"]

Five broad groups of products.

  • Large enterprise suites: broad, deep, global, expensive, with long implementations. Examples include SAP and Oracle products.
  • Mid-market suites: cloud-first products such as Microsoft Dynamics 365 or NetSuite.
  • Small business tools: simple accounting and CRM apps such as Zoho or HubSpot's free tiers.
  • Open source: Odoo Community and ERPNext, where you can host the software yourself.
  • Best-of-breed: a focused product for one area (for example, a warehouse system or a support desk) connected to the rest by integration.

Comparing options with a scoring model

You will build a proper selection method in chapter 8. For now, a short scoring stand-in shows how a market map becomes a decision. The weights and scores below are invented for the example.

Python Weighted scoring of fictional products

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The "winner" depends on the weights: raise the weight of cost and the small tool climbs. That is the point of making weights explicit.

A timeline as data

Timelines are easy to turn into data. This stand-in prints which developments happened before a given year.

Python Querying a timeline

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Why history matters for you

Old assumptions survive in today's products. ERPs still think in "documents" (order, delivery, invoice) because they grew out of paper processes. CRMs still revolve around the salesperson because they began as address books. Understanding this helps you predict how a product will behave and why a feature feels natural in one and awkward in the other.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What did MRP calculate?

    Material requirements planning derives purchase and production needs from the schedule and bills of materials.
  2. 2. Which is a typical difference of cloud ERP compared with on-premises?

    Cloud (SaaS) products are usually subscription-priced and the vendor operates and upgrades the service.
  3. 3. A 'best-of-breed' strategy means

    Best-of-breed combines specialist products, joined by integration.
  4. 4. Why make scoring weights explicit?

    Explicit weights show what the organisation cares about and let stakeholders challenge them.

Summary

  • ERP grew from inventory control through MRP and MRP II to enterprise-wide systems; CRM grew from contact managers and sales tools.
  • Cloud subscriptions have largely replaced big upfront licences, though hybrid setups are common.
  • Products can be grouped as large suites, mid-market suites, small tools, open source and best-of-breed.
  • A weighted scoring model turns a market map into a defensible choice.

Next: Key Terms, Roles and Data Concepts