Step 1 Define the CRM’s first job
Write the loop from lead to closed opportunity in plain language: who decides relevance, who owns it, where the next action is recorded and what history the company keeps. Decide whether partnerships, fundraising or member relationships share that loop or need their own pipelines.
Done when
- The loop from lead to close is written down, with an owner at each handoff
- Partnerships, fundraising and member relationships are in the loop or in their own pipelines
- The team updates the CRM during the work, not only before meetings
Why, and the detail
An early-stage company can lose surprising amounts of time to simple questions: Who last spoke to this person? What did we promise? Which opportunities need action this week? Is this address allowed to receive marketing? The first customer relationship management system should make those questions quick to answer. Enterprise-scale design can wait.
Write the first operating loop in plain language. A lead arrives, someone decides whether it is relevant, an owner takes responsibility, the owner records a next action, the opportunity advances or closes, and the company keeps the relationship history it needs. Even a solo business runs this loop; for an independent coaching practice, my ongoing conversion work covers the step where leads arrive. If the team also manages partnerships, fundraising or member relationships, decide whether those are variations of the same process or separate pipelines.
A CRM is useful when it changes daily behavior. If founders keep the real status in private messages and update the system only before a meeting, the database is reporting theatre. Design the first version around the moments when someone needs the record to do the next job, and let management reporting follow from that work.
Step 2 Choose the minimum trustworthy data model
Start with people, organizations, opportunities, activities and tasks. Give each open opportunity an owner, a stage, a value category and a dated next action, and give every record a stable ID. Keep identity, sales stage and consent in separate fields, and collect only the personal data you can justify.
Done when
- Every required field triggers an action, supports a decision or meets a real reporting duty
- Every open opportunity has one owner and one dated next action
- Identity, communication consent and sales status sit in separate fields
- Each category of personal data has a written purpose, source and list of who may use it
| Record | Minimum useful fields | Common mistake |
|---|---|---|
| Person | Name, organization, relevant contact method, source | Using one field for identity and marketing consent |
| Organization | Name, relationship type, owner, website or identifier | Creating duplicates for every spelling variation |
| Opportunity | Owner, stage, next action, value category, expected timing | Stages that describe optimism rather than observable events |
| Activity | Date, channel, participants, concise outcome | Copying whole private conversations without a purpose |
| Consent | Channel, status, source, date, evidence | Assuming a business card is permanent blanket permission |
Why, and the detail
Start with people, organizations, opportunities, activities and tasks. Depending on the business, products, subscriptions, projects or support cases may belong later. Give every open opportunity an owner, a stage, an expected value or category, and a dated next action. Keep a stable record ID so exports and integrations do not depend on names or email addresses that can change.
Japanese name forms in kanji, kana and Roman characters are covered in the guide to choosing a CRM for a Japan SME.
Separate identity, relationship and permission
A contact record says who the person is. A sales stage says where a commercial process stands. Communication consent says what the company may send and through which channel. These values change independently: someone can be a customer who has unsubscribed from a newsletter, or a prospect who requested a quotation but did not agree to general marketing. Treating “in the CRM” as permission to send anything creates risk and damages trust.
Collect less. Under Japan’s Act on the Protection of Personal Information, personal data creates obligations as well as possible value. Document why each category is needed, where it came from, who may use it and how correction or deletion requests are handled.
Step 3 Build a shortlist from constraints
Price each candidate for 12 months at your expected users, email volume, integrations and support, including cleanup and administration. Run the same scenarios in each, including one awkward case, and confirm the export and security controls in the tier you would actually buy.
Done when
- Each candidate has a 12-month cost at expected users, email volume and integrations
- Every candidate ran the same scenarios, including one awkward case
- A test export opened as readable tables with notes, files and activities included
- Multifactor authentication and role controls are confirmed in the tier you would buy
Why, and the detail
Affordable and free are different things. Estimate the 12-month cost for the expected number of users, email volume, pipelines, reports, integrations and support, plus import cleanup and administration. Some products offer a generous free entry but place a critical feature in a much higher tier. Others have a low per-user price but require more manual work or a separate marketing product.
For many startups, HubSpot, Zoho CRM, Pipedrive, Freshsales or a carefully structured Airtable-style database may enter the conversation. Salesforce can be appropriate when complexity, ecosystem or future scale justifies it, but it should not win on reputation alone. A table or Notion database can be enough for a controlled early process, though it needs more deliberate design for activity history, permissions and automation.
Shortlist two or three, then test the same scenarios in each. Add a bilingual contact, qualify an inbound request, schedule a follow-up, change an owner, record an unsubscribe, create a forecast and export the records. Include one awkward case, such as a person connected to two organizations or an opportunity that pauses for three months.
A CRM can be inexpensive to enter and costly to leave when the useful history is trapped in proprietary reports or attachments. Before choosing, confirm who can manage users, exports and billing, that multifactor authentication and role controls are in the plan you will pay for, and that an export gives readable tables with stable relationships, including notes, files and activities.
Connect only what supports the operating loop. Every integration is another permission, failure path and maintenance obligation.
Step 4 Implement in stages
Name a process owner and a technical administrator. Clean and map the data outside the CRM, import a representative sample, and repeat until the mapping is reproducible. Then launch one pipeline with one team, train with real work, and support it closely for the first two weeks.
Done when
- A process owner and a technical administrator are named, even if one founder is both
- A sample import passed checks on names, dates, owners, notes and consent before the full move
- One pipeline and one team are live, with a one-page field guide and office hours booked
Why, and the detail
Name a process owner and a technical administrator before configuration. At a startup, one founder may hold both roles at first.
Prepare data outside the CRM. Normalize obvious spelling and formatting differences, decide duplicate rules, remove records with no legitimate use, and map old columns to the new model. Import a representative sample first and inspect names, dates, owners, notes and consent. Delete the test records and repeat until the mapping is reproducible, then migrate the full approved set.
Launch one pipeline and one team. Train with real work: enter a lead, hand it to someone, update the next action, close it, and find the history later. Provide a one-page field guide with definitions and hold short office hours during the first two weeks. Fix friction quickly, especially duplicate entry and fields that require information users do not have.
Step 5 Keep growth and migration possible
At 30 days, remove the fields and automations the team routes around. Keep a data dictionary and configuration log, export core records and activities quarterly, and open the files to confirm the company could move without rebuilding its history from inboxes.
Done when
- Fields and automations the team routes around were removed at the 30-day review
- A data dictionary and configuration log cover fields, pipelines, integrations and admin roles
- Contacts, activities and attachments export quarterly and the files open with relationships intact
- Consent evidence and critical form definitions are kept separately
Why, and the detail
Thirty days after launch, remove the fields and automations the team routes around. The SME guide’s adoption step lists what to measure at 30, 90 and 180 days. A simple reminder on a reliable date is worth more than a multi-branch sequence built on uncertain stages.
Keep a data dictionary and configuration log: field purpose, pipeline definitions, integrations, administrator roles and the reason for important changes. Export core records and activities quarterly, open the files and confirm the relationships are understandable. Preserve form definitions and consent evidence separately when they are critical.
Clean identifiers, explicit definitions and tested exports let a startup outgrow its first CRM without reconstructing its commercial history from inboxes. Build a small system the team trusts for today’s work, and leave tomorrow’s choices open.
How to Set Up HubSpot CRM for Small Business
Video by HubSpot. Watch on YouTube ↗
Questions
Can a startup use a spreadsheet instead of a CRM?
Yes, when the team is very small and the sales process is simple. Move when shared ownership, activity history, follow-up reminders, consent records or reporting become unreliable. The signal is operational friction, not a fashionable headcount threshold.
Is a free CRM really free?
The entry tier may cost nothing, but add-ons, user limits, cleanup and an eventual migration still cost money. Price 12 months, not today’s license.
Should Japanese and English names use separate fields?
If the business needs both forms, store them separately and define which version appears in customer communications. Avoid forcing phonetic forms, legal names and preferred names into one value.
When should a startup automate follow-up?
After the team can run the process manually and explain the exceptions. Automating an unsettled process creates faster inconsistency and makes errors harder to see.
Official sources
Products, prices and Japanese requirements change. Check the source before a consequential decision.
- HubSpot CRM product information ↗ HubSpot
- Zoho CRM editions and features ↗ Zoho
- Salesforce small business CRM ↗ Salesforce
- Act on the Protection of Personal Information ↗ Personal Information Protection Commission, Japan
- Guidelines for cross-border personal data transfers ↗ Personal Information Protection Commission, Japan
Updated 19 Nov 2026 · 5 official sources · mkultraman.com