Your business · Practical guide
Build a CRM for your small business
Design a small contact-and-follow-up workflow, prototype it with fictional records, and verify saving, ownership, and export before real use.
Before you start
- Write the current sales process in plain language; avoid automating a process the team has not agreed on.
- Pick the smallest set of fields and stages. Use five fictional contacts covering different owners, stages, and due dates.
- Decide who can read, edit, assign, export, and remove records before choosing an authentication setup.
- Keep the existing contact source intact. A prototype and a successful preview are not a migration plan.
When this helps
Useful for a small custom follow-up workflow that a spreadsheet cannot handle comfortably. Customer records, multi-user access, and imports make a real CRM more demanding than a visual demo.
Build a small prototype first. Publishing, real user data, security and ongoing maintenance require separate checks.
Some setup and iteration · See the work involved
- Setup
- Choose a private test project and a clear data/authentication setup.
- Your work
- Agree on fields, stage meanings, record permissions, and a migration owner.
- Iteration
- Verify real save/reload flows, due dates, duplicates, exports, and access rules.
- Maintenance
- Own backups, user access, imports, billing, and repairs.
- Small team; fictional records until checks pass.
- Multi-user production use requires further review.
An editorial estimate for this task, based on documented requirements. Your experience can differ.
Opening the brief builder…
Use your chosen tool
- Fill in the workflow, data model, and permission rules, then choose an eligible builder you already use when possible.
- Build a single lead journey with fictional records: create, assign, set next action, change stage, and reopen.
- Add a due-follow-up view and validation. Check that stage labels and due dates follow the process you supplied.
- If there are multiple users, test the permitted and blocked actions with two fictional accounts in a private test project.
- Export the test records and restore into a fresh copy. Compare IDs, stages, owners, notes, and dates.
- Before real use, agree on migration, backups, access review, retention, costs, and a named maintainer.
An illustrative example
Written to show the intended shape of a result; this is not a measured tool test.
Starting material
Two-person design studio. Fields: contact, owner, stage, next action, due date. Stages: new, contacted, proposal, won/lost. Five fictional contacts. No email integration. Success: a proposal due tomorrow appears on the correct owner's follow-up list and survives reopening.
What success could look like
Illustrative workflow: create fictional lead Sam at Example Studio, assign owner Morgan, set "send proposal" due tomorrow, and move to proposal. Reload and verify the same record. Export and restore to confirm the owner, stage, and date survive. This describes expected behavior; no builder trial is claimed.
Check before using it
- Does a contact keep its ID and details after edits and reopening, without duplicating or losing records?
- Are duplicate email addresses flagged for a decision rather than overwritten silently?
- Does the due list handle overdue, today, future, missing, and invalid dates correctly in the chosen time zone?
- Can each test user perform only the view/edit/assign/export actions the brief allows?
- Does removing or changing a filter preserve the underlying records?
- Does export preserve quoted notes, commas, dates, IDs, owners, and stages, and does restore recover them?
- Are save errors visible, and can a user retry without creating duplicate records?
If it needs work
- The due list shows future tasks as overdue. Use these three fictional dates, explain the time-zone rule, fix it, and rerun the checks.
- Do not add automated outreach. Keep manual follow-ups and a clear due list for this first version.
- Teammate B can view a record assigned only to A. Fix the data-layer permission rule and retest both allowed and blocked reads with fictional accounts.
- CSV import duplicated existing contacts. Preview duplicate handling and ask for a merge decision before changing saved records.
The simpler alternative
Use a spreadsheet with contact, stage, owner, next action, and due date columns. Filter by owner and overdue date before building custom software.
When a specialist product may be worthwhile
Use an established CRM or a developer when you need sensitive contacts, many users, audit history, reliable integrations, compliance controls, or dependable bulk migration.
Sources and review
Documentation reviewed 2026-09-30. Plan limits and interfaces can change. How we prepare these guides.