Every Salesforce feature was built to solve a business problem. If you skip the business, the features never make sense.
This is where the training starts. Not with a login screen. Not with a Developer Org. With the question every company answers before it buys any software: what do we sell, who buys it, and are we making money?
Thirteen lessons. No jargon. No prerequisites. By the end you will have the vocabulary that every Salesforce screen, every pipeline review, and every interview question is built on.
Who this is for
You have never worked in a company. Or you have worked in one but never understood what the sales team actually does all day. Or you switched careers from teaching, accounting, engineering, or BPO and nobody ever sat down and explained how a deal moves from "interested" to "paid."
It does not matter which. This section assumes you know nothing beyond how to read. Every word that appears later in the curriculum gets defined here first.
The problem this solves
Most Salesforce training starts at the product. "Here is a Lead. Here is an Opportunity. Click this button." You memorise the steps, pass the exercise, and then sit in a real meeting where someone says "our pipeline coverage is thin and the ACV on this cohort is dropping." You have no idea what they said.
That is not a Salesforce problem. It is a business vocabulary problem. The person who cannot explain what revenue means, what a quota is, or why a deal is different from a customer will always be confused by the software that tracks those things.
Thirteen lessons fix that. Not with textbook definitions. With a story.
Meet the company you will work in
Namaste Salesforce is a training company. It teaches Salesforce to individuals and sells corporate training packages to companies like Himalaya Tech and Konkan Logistics. Arjun Deshpande founded it. Priya Sharma runs the sales team. Aarti Menon closes deals with individual learners. Sneha Iyer handles support tickets when a learner's voucher does not arrive.
Every example from this point forward comes from their world. By the time you finish this training, you will know these people better than some of your colleagues. That is the point. Learning sticks when it lives inside a story you care about.
Why one company for a thousand lessons?
Because real Salesforce orgs grow messy over time. Sales reps skip fields. Data gets duplicated. Reports stop making sense. That mess is not a bug in the curriculum. It is the curriculum. You will watch Namaste Salesforce's org get more complex as the business grows, and you will fix each problem with the tool you have just learned.
What these thirteen lessons cover
What a business is and how it makes money
Product, service, customer, value, market, competition. The six words that describe any company on earth, before any software is involved.
Why companies have departments
Sales, marketing, service, finance, HR, operations. What each team owns, why they fight over data, and where the handoffs break.
B2B vs B2C and company size
Selling to a company and selling to a person are different jobs. Selling to a 50 person startup and selling to a 50,000 person bank are different universes. Both change the CRM setup completely.
What a deal is and why companies buy software
A deal is a possible sale that has not happened yet. It has an amount, a date, and a probability. Tracking thousands of those on spreadsheets is what finally breaks, and that breaking point is where CRM begins.
The road from here
What Is a Business?
A business solves a problem for someone and gets paid for it. That is the whole definition.
What Is a Product?
The thing a company sells. Physical or digital, boxed or downloaded. The thing with a price tag.
Product vs Service
A product sits on a shelf. A service happens when someone shows up and does the work. Most companies sell both.
What Is a Customer?
The person or company that pays you money. Keeping them is harder than finding them.
What Is Value?
The gap between what something costs and what it is worth to the buyer.
What Is a Market?
All the people who might buy. Finding the ones who actually will is the entire job of sales and marketing.
What Is Competition?
Someone else solving the same problem. Sometimes another company. Sometimes a spreadsheet. Sometimes doing nothing.
Departments in a Company
Sales, marketing, service, finance, HR, operations. Who owns what, and where data dies in the handoff.
Who Owns a Company?
Founder, owner, shareholder, board. Four words for the people who decide what happens next.
SMB vs Mid-Market vs Enterprise
Company size changes how it buys, how long the deal takes, and how many people say yes.
B2B vs B2C
Selling to a company and selling to a person are two different jobs. The CRM setup changes completely.
What Is a Deal?
A possible sale that is not done yet. An amount, a date, a probability that shifts every week.
Why Companies Buy Software
Nobody buys software because they want software. They buy it because staying broken finally costs more than changing.
After this section you will be able to
- Explain what a business does and how it makes money, in plain English
- Name the departments in a company and describe what each one owns
- Tell the difference between B2B and B2C and explain why it changes everything
- Define revenue, cost, profit and margin in one sentence each
- Describe what a deal is before any software is involved
- Explain why companies buy software and what pain drives the purchase
- Recognise the Namaste Salesforce team by name and know their roles
Where this sits in the full training
Business Basics is the first of seventeen sections in Phase 0. After this you will learn how money works inside a company, how people ran businesses before computers existed, how selling and marketing and customer service actually work day to day, and what a CRM is. Only then do we open Salesforce.
That may feel slow. It is not. Every hour you spend here saves you ten hours of confusion later. The people who struggle in Salesforce interviews are rarely missing a feature. They are missing the business context the feature was built for.
On pace. There is no deadline. There is no leaderboard. Some lessons you will finish in four minutes. Others you will sit with. Both are fine. The goal is not speed. The goal is that you can explain each idea to someone who has not read it. If you can, move on. If you cannot, read it once more.
The sections
- 01 · Order of execution, the map Before triggers, validation, after triggers, assignment rules, flows, roll-ups — what actually runs when you press Save. 15m
- 02 · One trigger per object Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework. 10m
- 03 · The handler pattern One method per event, a static bypass flag, and constructor-free classes your tests will thank you for. 15m
- 04 · Bulkification: 200 records or bust Triggers receive up to 200 records at once. Every query and DML statement inside a loop is a countdown to 'Too many SOQL queries: 101'. 15m
- 05 · Recursion control Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry. 10m