CRM · Private relationship tracker
Remember the relationship context that makes the next conversation more thoughtful.
Personal CRM is a lightweight relationship tracker for individuals, freelancers, and consultants. Add people, record their company and tags, log conversations, and set a specific date to follow up. This Foundationbase implementation keeps its contact and interaction records in the current browser, requires no account, and provides a source copy for changing the fields and reminder workflow.
Open the working toolProduct preview
These screens come from the working Foundationbase implementation.
What this tool helps you do
Phone contacts preserve names and numbers, but they rarely capture why a relationship matters, what happened in the last conversation, or when you intended to reconnect. A conventional sales CRM adds deal stages, team administration, and automation that may be unnecessary for a personal network.
Personal CRM keeps two linked record types: people and interactions. A person can carry a company, tags, and one next-follow-up date. Each logged note is attached to that person and also appears in a chronological timeline across all relationships.
What is included
Create a person from a name, then edit the company, tags, and next follow-up date in the selected profile.
Why it matters: The record captures relationship context without demanding a large sales schema.
Verified in: Contact type and PeopleView
Add lowercase tags such as client, friend, prospect, design, or a label specific to your network; remove them directly from the profile.
Why it matters: A compact vocabulary makes relationships easier to recognize without imposing pipeline stages.
Verified in: ContactDetail tag editor
Write a note after a call, meeting, or message. The app stamps it with today's date and associates it with the selected contact.
Why it matters: The next conversation can begin with the context of the last one.
Verified in: Interaction type and logInteraction
Assign one next-follow-up date to a contact, clear it when plans change, or open the dated queue to see every scheduled person.
Why it matters: Intentions to reconnect become visible work rather than memory alone.
Verified in: followUpOn field and FollowupsView
The queue compares each follow-up date with the current date and labels contacts as overdue, today, or upcoming.
Why it matters: Attention can start with relationships whose chosen date has already arrived.
Verified in: FollowupsView date comparisons
Snooze moves the stored date forward seven days. Done clears the date and adds a 'Followed up.' interaction to that person's history.
Why it matters: Working the queue updates both future attention and the relationship record.
Verified in: snooze and markDone functions
The Timeline view sorts every interaction by date and displays the related person's name with the note.
Why it matters: You can scan recent relationship activity without opening contacts one by one.
Verified in: TimelineView
Contacts and interactions are serialized to one versioned localStorage key and restored when the same browser returns.
Why it matters: The demo works without an account or hosted database while keeping its data boundary easy to inspect.
Verified in: useLocalState and Foundationbase.personal-crm.v1
How it works
This CRM is organized around the relationship loop implemented in its People, Follow-ups, and Timeline views.
Enter a name in the People view. The new contact is selected immediately with blank company, tags, and follow-up fields.
A minimal relationship record exists without a long form.Enter the company and tags that help you recognize the person's role or relationship.
The record becomes useful when names alone are not enough.Write what you discussed or what matters next. The note receives today's date and appears in the person's history.
Conversation context is attached to the right relationship.Set a date on the contact profile. The person enters the global queue in chronological order.
The intention to reconnect becomes actionable.Open a due contact, snooze the date by one week, or mark it done. Completing it records a follow-up interaction automatically.
The queue and timeline stay aligned.Real use cases
For a consultant
Situation: Several clients and prospects matter, but an enterprise CRM would add more process than the work needs.
Workflow: Tag people by relationship, log important conversations, and schedule the next personal follow-up.
Outcome: Client context and next actions remain visible in a private, small system.
For a networker or community organizer
Situation: You meet useful people in bursts and need to remember the conversation after the event.
Workflow: Add each person, tag the event or community, record the discussion, and set a realistic reconnect date.
Outcome: New connections are less likely to disappear into an address book.
For a freelancer
Situation: A full sales pipeline is unnecessary, but prospects still need notes and next-touch dates.
Workflow: Tag prospects, log calls, and use the follow-up queue for overdue and upcoming conversations.
Outcome: A sales-lite workflow stays centered on people instead of deal administration.
For an individual
Situation: You want a private record of last contact and future check-ins for a modest circle.
Workflow: Use relationship tags, short notes, and selected follow-up dates without company data where it is irrelevant.
Outcome: The same record model supports personal attention without pretending to be a social network.
Who it is for
Use it, install it, or make it yours
Open the live CRM and work with the seeded contacts or reset the demo. New contacts, edits, notes, and follow-up actions are saved in this browser profile.
Download the source package to make an editable version. The core implementation is a small React client component plus shared local-storage and date helpers.
A coding agent can add fields, filters, birthdays, a dashboard, or import/export. The current Contact and Interaction types are the factual starting point; import and cloud behavior do not exist until you add them.
Publish the customized Next.js project to a compatible host and use its stable URL as your version. Add a backend only if the privacy, account, and synchronization tradeoffs are intentional.
Customization ideas
Personal CRM has an intentionally small model: contacts and interactions. That makes field changes approachable, but features such as import, multi-device sync, and reminders require real implementation rather than copy changes.
Add a relationship follow-up dashboard to Personal CRM. Use the existing Contact.followUpOn field, group overdue, today, this week, and later, and do not change or discard existing localStorage data.Add CSV export and import to Personal CRM. Export contacts and interactions separately, preview validation errors before import, preserve contactId relationships, and do not claim cloud sync.Add birthday and preferred-contact-method fields to the Contact type. Migrate records loaded from Foundationbase.personal-crm.v1 when the fields are absent and keep the People, Follow-ups, and Timeline views working.Technical details
Privacy and data behavior
By default, Personal CRM stores contact and interaction records in localStorage for this browser. The component does not call a third-party API or require an account. That local boundary is useful for a small private list, but it is not automatic backup, encryption, or cross-device sync.
Location: One JSON state object in the current browser profile under Foundationbase.personal-crm.v1
Network: The current Personal CRM component performs no application data fetches. Normal site assets still load from the host serving the page.
Delete: Delete individual contacts with confirmation; their linked interactions are removed too. Reset replaces the state with seeded sample data. Clearing site data removes the local record.
Export: No export or import method is included in the current implementation.
Verification and known limitations
Foundationbase verification checks expected functionality, packaging, setup clarity, and common implementation concerns. It is not a professional security audit, accessibility certification, legal review, or guarantee of production suitability.
Comparison
The meaningful comparison is the relationship model, follow-up behavior, and data boundary—not a generic list of productivity claims.
| Decision | Foundationbase tool | Starting from scratch | Generic alternative |
|---|---|---|---|
| Contact model | Name, company, tags, next follow-up, and created time | You decide fields, validation, and editing flow | Often includes many sales and organization fields |
| Interaction history | Dated notes linked to a contact and global timeline | Requires linked records and sorting | May include email and call automation |
| Follow-up workflow | One date per person with open, one-week snooze, and done | You define states and date behavior | Often tasks, sequences, and team assignments |
| Import and export | Not included in the current app | Can be designed for exact sources | Commonly available with provider-specific mapping |
| Data location | One browser localStorage record | You choose local or remote architecture | Usually provider-hosted cloud data |
| Collaboration | Single-browser, single-user behavior | Can be designed around a team | Usually central to the product |
| Customization | MIT source and a small inspectable domain model | Maximum freedom but no working flow | Limited to fields and settings exposed by the vendor |
FAQ
Yes. The live tool is free to use, and the downloadable source is listed under the MIT license. Check the license included with your copy before redistributing a modified version.
They are serialized to localStorage in the current browser profile under Foundationbase.personal-crm.v1. The current component does not send those records to an application backend.
No. Import is not implemented in the current app, despite older catalog copy describing an import-ready direction. It is a reasonable customization, but it needs mapping, validation, duplicate handling, and interaction-link preservation.
It does not send operating-system, email, or push notifications. The Follow-ups view surfaces overdue, due-today, and future dates when you open the app.
Yes, by modifying the source. Add fields to the Contact type, update the detail form, and handle existing local records that do not contain the new fields.
Not in the current implementation. It has no authentication, shared database, roles, or conflict handling. Those would be an advanced architecture change.
No export control is currently included. Until one is added, clearing site data or losing the browser profile can remove the records.
Start from something real
Use the relationship tracker in your browser, or create a source copy and change the fields, follow-up views, and data controls for the way you actually maintain relationships.