A creator CRM does not need a sales pipeline with twenty stages. It needs to answer a smaller set of questions reliably:

  • Who is this person?
  • May I email them?
  • How did they arrive?
  • What have they bought or joined?
  • What would be a useful next step?

If the system cannot answer those questions, adding more fields will not help.

Use email as the practical identifier, but do not treat an address as permission. Store subscription status separately and preserve it during imports. An old unsubscribe must not become a new subscriber because a CSV cell was ignored.

Keep only fields you use. Name, email, preferred language and source are enough for many businesses. Phone and company are useful only when the offer or support flow needs them.

Record the source once

Source is how the relationship began: a workshop form, a course waitlist, a download or a purchase. A useful source value is stable and specific enough to compare later.

Do not replace the original source every time the person clicks a new link. Later campaign parameters belong in activity history; first source answers a different question.

Use tags as facts, not a filing cabinet

A good tag states something that can change a decision:

  • interest-podcast
  • customer-awaken
  • attended-workshop-aug-2026
  • coaching-applicant

Avoid tags such as important, new-list-2 or a separate tag for every email ever sent. If nobody can explain what action a tag changes, remove it.

Separate contacts from members without splitting the person

A contact can receive email without having an account. A member has signed in and may have access to content. The roles are different, but the person should not become two unrelated records after purchasing.

The useful CRM view combines contact data with access, purchase, booking and course activity. That is what lets support answer a question without opening four systems.

Build segments around a decision

A segment is a query, not a permanent identity. Examples:

  • subscribed people interested in podcasting who have not bought the podcast course;
  • members with access to a course but no activity in 21 days;
  • workshop registrants who attended but did not join the follow-up offer.

Each segment should lead to a specific message, export or manual review. “All active people” is useful for a dashboard, not necessarily for an email.

Keep a way out

Export should include email, name, language, tags, subscription state and relevant dates. Test the export before you need to migrate. A CRM that can collect contacts but cannot return them is not a safe home for an audience.

Idun’s people view combines contacts and members, supports CSV import/export, tags, saved segments and activity around purchases, access and bookings. See contacts and member CRM.