IT Glossary
What is Machine Learning?
Software that works out its own rules from examples — instead of a programmer writing them by hand.
Classical programming runs one way: a person writes the rules, the computer applies them. Machine learning reverses the flow: you feed the computer examples — thousands of invoices labeled “paid on time / paid late”, order history, normal and fraudulent transactions — and it derives the rules itself: patterns too subtle or too numerous for a human to spell out. From that reversal come the business applications that have already survived contact with the market: prediction (which customers will churn, which stock will run out, which receivables will slip), classification (mail sorted, suspicious transactions flagged, products categorized), recommendation (which product this buyer is likeliest to want next) and estimation (prices, lead times, risk scores from historical data). Its family tree in one line: ML is the subset of AI that learns from data; deep learning is its neural-network subset — and generative models are the visible tip of that. Three truths any executive should hold before an ML project: the model mirrors the data — a thin or messy history yields predictions to match (clean data first, models second); outputs are probabilistic, not certain — use them as signals that assist decisions, with thresholds and human review where stakes are high; and value is measured in money on a concrete case (“the model cuts dead stock by X percent”), not in laboratory accuracy. Here too, a small pilot on one valuable question beats a grand strategy.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
The near future, estimated from data
Customer churn, stock-outs, late payments — flagged from patterns before they become accomplished facts.
Automatic triage at volume
Thousands of transactions, emails or requests sorted and prioritized automatically — people see only the exceptions that need judgment.
Personalization that sells
Recommendations learned from real customer behavior measurably lift average order value — the mechanism behind the retail giants, available at your scale too.
Frequently asked questions
How much data do we need for a machine-learning project?
It depends on the question: for classic tabular predictions (churn, late payment), thousands to tens of thousands of historical records are a reasonable start; for text and image tasks, pre-trained models have lowered the bar to hundreds of examples for specialization. More often than volume, the real problem is quality: inconsistently labeled history damages more than short history.
How does machine learning differ from a report or a business rule?
The rule you write yourself (“no order in 90 days — alert”); the model discovers predictive combinations on its own (“thinner orders plus smaller baskets plus support tickets equals churn within 60 days”) — including ones you'd never think of. The cost of the difference: rules are transparent and free, models need data, validation and upkeep — justified where the patterns outgrow rules.
Does the model keep learning, or stay as trained?
Whichever you build: by default a model remains a snapshot of its training data and degrades as reality shifts — markets, seasons, behavior — a phenomenon called drift. Healthy practice: monitor accuracy over time and retrain on a schedule — one more reason ML is a living service, not a one-off purchase.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247