HubSpot earned its place as the default first CRM the honest way: the free tier is genuinely usable, not a crippled demo. But “sign up free” and “have a working system” are separated by setup decisions — and the order of those decisions determines whether the CRM gets adopted or abandoned by week three.
This guide is that order, on the free tier, no card required. It assumes you know what a CRM is; the deeper layers — pipeline craft and automation — have their own guides. For freelancers: this exact setup, delivered for clients, is a sellable service (the specialist path) — and the demo account you build today is your first portfolio piece.
Quick Facts
| Detail | Information |
|---|---|
| Provider | Fredeveloper Academy |
| Topic | Complete HubSpot free-tier setup, in working order |
| Best for | First-time CRM owners; freelancers building a demo/service |
| Cost | ₱0 — everything here runs on the free tier |
| Setup time | A focused afternoon for the core; a week to working habits |
| The order | Settings → clean import → pipeline → properties → first automations |
| Coming soon | CRM course — join the waitlist |
| Last updated | 17 April 2026 |
The ContextWhy Setup Order Decides Adoption
Most abandoned CRMs died of bad setup, not bad software. You're probably here because:
| Situation | Why it matters |
|---|---|
| You signed up and froze at the dashboard | HubSpot shows everything at once; the working path touches five areas in order |
| Your import made a mess | Dirty data in = distrust out. The clean-import step below prevents it |
| The default pipeline doesn't match your business | Defaults are placeholders — stage design is THE setup decision |
| You're prepping a client setup as a freelancer | This sequence IS the deliverable; scope it, deliver it, get the testimonial |
Step 1Foundations: Settings Before Data
Ten minutes that prevent weeks of weirdness: set company name, timezone, and currency (Settings → Account Defaults) so every timestamp and deal value means what you think; connect your business email inbox so conversations log to contact timelines automatically — this single connection is what makes the CRM feel alive instead of like data entry; and invite teammates with sensible permissions now, because a CRM one person uses is a private notebook.
Step 2The Clean Import
Your contacts live in exports, phones, and inboxes. Before importing: merge into one sheet, dedupe, standardize (one column each for first name, last name, email, phone, company), and delete obvious dead rows. HubSpot's import maps your columns to its fields — map carefully and import a 10-row test first; finding a mapping error on 10 rows is a do-over, on 2,000 it's an afternoon. Garbage imported is garbage enshrined: the team's trust in the CRM is decided by whether the first lookups return clean truth.
Step 3A Pipeline Shaped Like Your Business
Infographic 01 · Stage Design
Default stages vs your real process
Write your real sales process on paper first — inquiry to payment in 4-6 steps — then build exactly that in Settings → Objects → Deals. Full stage craft (exit criteria, hygiene, forecasting) lives in the pipeline guide.
Step 4Properties & First Automations
Properties are custom fields. Add the 3-5 your business actually decides with — lead source, service interest, budget range — and stop there; every field is a tax on whoever fills it. Then two starter automations (free tier handles both): a task auto-created when a new contact arrives (“call within 24h”, owned and dated), and a simple follow-up reminder when a deal sits too long in a stage. That's enough automation to feel the magic without building a machine you don't understand — the workflows guide takes it further when you're ready.
Infographic 02 · The Afternoon
The whole setup, in order
Setup DayA Real Setup Day, Narrated
Here's the setup afternoon as it actually unfolds for a typical small service business — three people, ~800 contacts scattered across two inboxes and a spreadsheet, no prior CRM. Timestamps approximate; decisions verbatim-shaped.
| Time | What happened | The decision worth copying |
|---|---|---|
| 1:00-1:30 | Account created; defaults set; both business inboxes connected; two teammates invited | Inbox connection FIRST — the team's email history starts logging immediately, so the CRM has life in it by day's end |
| 1:30-2:45 | The spreadsheet merge: three sources into one sheet; 94 duplicates collapsed; 60 dead rows deleted; columns standardized | The 'when in doubt, delete' rule for ancient contacts — a smaller clean list beats a bigger haunted one |
| 2:45-3:15 | 10-row test import caught a swapped first/last name mapping; fixed; full import ran clean | The test import earned its keep in one pass — on 800 rows the swap would have been an evening of repair |
| 3:15-4:00 | Pipeline built from the owner's paper sketch: Inquiry → Site visit booked → Quote sent → Decision → Won/Lost (reason required) | ‘Site visit booked’ instead of the default ‘appointment scheduled’ — THEIR process, their words |
| 4:00-4:30 | Three properties added (lead source, service type, budget band); two automations on: 24h new-contact task, 7-day stale-deal alert | Stopped at three properties despite temptation — 'we can add fields when we miss them' |
By 4:30 the system was live; by Friday the habit question had its answer — the owner's rule was "if it isn't in HubSpot, it didn't happen," said in the Monday meeting and enforced by example. Two weeks later the pipeline view ran the weekly meeting, which is the real definition of adoption.
Freelancers: this afternoon, delivered with a one-hour training call and a one-page "how we use it" doc, is a complete, scopeable service — the doc and the paper-sketch pipeline session are what clients remember paying for.
Worked ExampleA Tutoring Center's Setup Afternoon — the Log
Illustrative, hour by hour. 1:00-1:30 — foundations: account created; timezone and currency set; the center's Gmail connected (inquiry emails now log to timelines automatically); two teachers invited with member permissions. 1:30-2:30 — the clean import: contacts scattered across a signup sheet, Messenger, and the owner's phone get merged into one spreadsheet — 312 rows become 268 after dedupe; columns standardized; a 10-row test import catches a phone-column mapping error before it becomes 268 errors. Full import lands clean. 2:30-3:15 — pipeline: the real process on paper first — Inquiry → Trial class booked → Trial done → Enrollment offered → Enrolled / Lost (reason) — five stages, each exit-defined. 3:15-4:00 — properties + automation: three custom fields (subject interest, grade level, lead source); two starter workflows — new inquiry creates a “call within 24h” task, and any deal sitting 7 days in “Trial done” nudges the owner. The next two weeks: everyone logs everything. By month's end, “who needs a follow-up?” is a filter, not a meeting.
Infographic 03 · The Afternoon Log
Three hours, five layers, in order
Field NotesSetup Mistakes That Surface Weeks Later
| The mistake | How it surfaces | The prevention |
|---|---|---|
| Skipping the inbox connection | Manual logging fatigue → abandonment | Connect email in the first half hour |
| Importing without dedupe | Two records per person; trust erodes | Merge + dedupe in the sheet, before import |
| Mapping errors at full scale | A whole column of garbage fields | The 10-row test import, always |
| Default pipeline kept 'for now' | Stages nobody believes in; board ignored | Real process on paper first, then build |
| Ten custom properties on day one | Unfilled fields, cluttered records | 3-5 deciding fields; add only on proven need |
Take a screenshot tour of the finished setup — pipeline, a clean contact record, the two workflows. For your own team it's the training doc; for a freelancer it's the portfolio piece and the before/after a client proposal is built on.
ToolboxWhat Surrounds a Good Setup
The setup itself needs: the merge spreadsheet (one sheet, standardized columns — the unglamorous hero); a naming convention decided early (deal names like “Contact — package — month” keep boards scannable); a permissions sketch (who can delete vs edit vs view); and the training half-hour — a live walkthrough where each teammate logs one real call and creates one real task, because people adopt what their hands have done once. Afterward, the growth path is mapped: pipeline craft, then automation. HubSpot Academy's free courses slot alongside — and for freelancers, this whole package (setup + training + documentation) is the sellable unit described in the specialist guide.
GlossaryTerms You'll Meet During Setup
| Term | Plain-English meaning |
|---|---|
| Portal | Your HubSpot account/instance |
| Import mapping | Matching your sheet's columns to HubSpot fields |
| Deduplication | Merging duplicate records — HubSpot auto-matches by email |
| Object | A record type — contact, company, deal, ticket |
| Custom property | A field you add — use sparingly, decide-with only |
| Permission set | What each user can see, edit, or delete |
ScenariosFour Setups, Four Emphasis Shifts
| Setting up for | Shift the emphasis to |
|---|---|
| Yourself (solo freelancer) | Speed over ceremony: contacts in, a 4-stage pipeline, the new-lead task automation — done in an hour, refined later |
| A small sales-driven team | Permissions, owner fields, and the shared logging ritual — multi-user truth is the whole point and the whole risk |
| A client, as a paid service | Their process mapped BEFORE touching settings, a training session as deliverable, and documentation they keep |
| A business drowning in an old messy CRM | Different job entirely — cleanup and migration first (the rescue offer), fresh setup principles second |
The sequence in this guide holds across all four; what changes is where the care concentrates. The client scenario adds the most: in paid setups, the training session and the leave-behind documentation are worth as much as the configuration itself.
Deeper DiveThe Data Hygiene Rules That Keep the Import Clean Forever
The clean import is a moment; staying clean is a policy. Four rules, set in week one, prevent the slow slide back to chaos. One way in: decide how new contacts enter (forms, manual entry with required fields, inbox logging) and close the side doors — ad-hoc imports of random spreadsheets are how duplicates breed. Required minimums: a contact isn't created without name, email or phone, and source — three fields, no exceptions, because half-records are future archaeology. Owner on everything: every contact and deal has exactly one owner, so nothing is everyone's job and therefore no one's. The merge habit: when a duplicate surfaces, merge it that day — HubSpot's merge tool makes it a minute's work, and duplicates compound interest if ignored.
Write the four rules where the team sees them; they fit on an index card. The difference between a CRM that's trusted at year two and one that's quietly abandoned is rarely features — it's whether the data stayed believable, and these four rules are most of what believable requires.
ProgressSetup Quality, Verified
| Verification | Pass condition |
|---|---|
| The stranger test | A new teammate can find any customer's full story in under a minute |
| The pipeline test | Board total and stages match what the owner believes is true out loud |
| The automation test | Create a test contact — does the follow-up task appear, owned and dated? |
| The hygiene spot-check | Pull 10 random contacts: complete fields, single owner, no duplicates |
Run the four tests at the end of setup week and again at day 30 — for client work, run them WITH the client, because passing tests they witnessed is what converts a setup project into a maintenance retainer. A setup that can't pass them isn't done, however configured it looks.
RisksChallenges & Misconceptions
| Misconception | The honest version |
|---|---|
| “Free tier = toy tier” | HubSpot free runs real small businesses: contacts, pipeline, tasks, email logging, starter automation. Upgrade on real limits, not anxiety |
| “Import everything, sort it later” | Later never comes; distrust does. Clean before import — it's the cheapest data work you'll ever do |
| “More custom fields = more insight” | Unfilled fields are noise wearing a label. Fields you decide with, only |
| “Setup done = adoption done” | The system is the habits. Two weeks of everyone logging touches is the real go-live |
Next StepsYour Setup Afternoon
- Create the free account; set defaults; connect your inbox; invite the team.
- Clean your contact sheet; test-import 10 rows; then import all.
- Build your real 4-6 stage pipeline with exit criteria.
- Add 3-5 deciding properties; create the two starter automations.
- Run the two-week logging habit — then level up with the pipeline and workflows guides, or the course waitlist.
FAQFrequently Asked Questions
Is HubSpot CRM really free?
Yes — the free tier includes contacts, deals, pipeline, tasks, email logging, and starter automation, with no time limit. Paid tiers add depth (more automation, reporting, removal of limits) as you grow.
How long does HubSpot setup take?
The core — settings, clean import, pipeline, properties, first automations — is a focused afternoon. The working system arrives after about two weeks of the team actually logging touches.
How do I import contacts into HubSpot without a mess?
Clean first: merge to one sheet, dedupe, standardize columns, delete dead rows. Then map fields carefully and import a 10-row test before the full file.
What pipeline stages should I use?
Your real process, in 4-6 stages, each with a clear exit condition — not the defaults. Write inquiry-to-payment on paper first, then build exactly that.
Can I sell HubSpot setup as a freelance service?
Yes — this exact sequence, delivered with training, is a productizable service for businesses adopting CRMs. The demo account you build is your first portfolio piece; see our CRM specialist guide.
Can I change my pipeline stages after setup?
Yes — stages can be edited and deals reassigned. Early adjustment is normal; just re-brief the team on the new exit criteria so definitions stay shared.
Should I import old, inactive contacts?
Generally no — import active relationships and recent inquiries, archive the rest in a spreadsheet. Dead records bury live signal and inflate every future list and report.
How do I get my team to actually use the new CRM?
Connect their inboxes (so logging is mostly automatic), train hands-on for thirty minutes, agree that 'if it's not in the CRM it didn't happen', and run the two-week logging ritual together. Habit, not features, decides adoption.
How do I keep my CRM data clean after the import?
Four standing rules: one controlled way in for new contacts, required minimum fields (name, contact method, source), exactly one owner per record, and same-day merging of any duplicate found.
How do I verify a CRM setup is actually done?
Test it: a newcomer finds any customer's story in under a minute, the pipeline matches spoken reality, a test contact triggers the follow-up automation, and ten random records pass a hygiene spot-check.
What does a typical HubSpot setup look like in practice?
A focused afternoon: inboxes connected first so history starts logging, a deduplicated import tested on 10 rows before the full file, a pipeline built from the owner's real process in their words, three deciding properties, and two starter automations.
An Afternoon of Setup. Years of Not Losing Leads.
The upcoming CRM course turns this setup into guided practice and a service you can sell. Join the waitlist — and if freelancing is the goal, the Launch Kit handles the client side.
No income promises. No hype. Just the path.