Everyday life · Practical guide
Build a personal CRM to keep in touch
Make a private contact-and-follow-up tool for friends, mentors, or your professional network, with simple reminders and an export you control.
Before you start
- Choose the people and purpose: friends, mentors, or a personal professional network. Keep the first version to a contact list and manual follow-ups.
- Write three fictional contacts, including two with the same name and one with no email or next-contact date. Leave private conversations and sensitive notes out.
- Decide between one-device storage and a private account-backed app. Browser storage can be lost when clearing data and does not automatically sync or back up.
- Decide what “due” means in your local time zone and what changes when you mark a conversation complete. Choose a regular backup location you control.
When this helps
Useful when you want a small, personal way to remember people and follow-ups. It can also support an individual professional network at work. A shared customer pipeline needs the separate business CRM guide and more demanding access rules.
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 confirm one-device or account-backed storage.
- Your work
- Choose contact fields, follow-up rules, and a privacy and backup routine.
- Iteration
- Verify optional fields, same-name contacts, dates, privacy, persistence, and restore.
- Maintenance
- Review follow-ups weekly; own exports, account access, hosting limits, and repairs.
- One owner and fictional contacts until privacy and recovery checks pass.
- No automatic outreach, contact sync, or sensitive relationship notes.
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 people, fields, follow-up rules, and storage choices. Prepare the brief locally and open an eligible builder; an existing eligible tool comes first.
- Ask for the contact list and one editable detail screen with three fictional people. Confirm storage and privacy before entering actual contacts.
- Add a person, edit a note, leave email blank, and reload. Check the same record survives without a duplicate or an invented value.
- Add the due-follow-up view. Try yesterday, today, next week, and no date; mark a fictional conversation complete and choose the next date yourself.
- Try search and group filters on a phone. Reopening or clearing a filter must not change saved records.
- Check private access in a signed-out session if the app uses accounts. Export the fictional contacts and restore into a fresh test copy, comparing IDs, notes, and dates.
- Before real use, check the account plan and data location. Review the list weekly, keep regular exports, and own access, storage limits, dependency updates, and future repairs.
An illustrative example
Written to show the intended shape of a result; this is not a measured tool test.
Starting material
Three fictional contacts: Alex Reed in Friends, due 2026-10-01; Alex Stone in Mentors, no email or next date; Morgan Lane in Former colleagues, due 2026-10-07. One owner, private app, local calendar dates, manual follow-ups, export and restore. No messaging or address-book connection.
What success could look like
Illustrative acceptance example: with the test clock set to 2026-10-01, Alex Reed appears due today and Morgan Lane stays in the future list. Alex Stone has “No next date” and remains a separate person. Mark Alex Reed contacted, choose 2026-10-15 yourself, reload, then export/restore and compare all three IDs and dates. These are expected behaviors, not measured builder output.
Check before using it
- Can you add a person without an email and keep two people with the same name as separate records?
- Do edits and reloads preserve the same record ID, group, note, and dates, including a visible failed-save state?
- Does the due list correctly separate overdue, today, future, and missing dates in the stated time zone?
- Does marking a conversation complete update the last-contact date without automatically messaging anyone or inventing a next-contact date?
- Do search and group filters change only the view, leaving all saved contacts intact?
- Is account-backed data private to the intended owner when checked from a signed-out test session? A hidden screen alone does not establish private access.
- Does export and restore preserve commas, quoted notes, blank values, stable IDs, and calendar dates without duplicates?
- Can you find, edit, and save a contact on a narrow phone screen with the keyboard open?
If it needs work
- Two fictional people named Alex were merged. Keep stable IDs, flag possible duplicates for review, and do not use the name as the unique key.
- A contact without a next date appears overdue. Keep missing dates distinct and retest yesterday, today, next week, and no date.
- Remove email sending, contact scoring, and automatic reminders. Keep a manual due list and my own decision about who to contact.
- Restore changed the follow-up dates or duplicated people. Preserve local calendar dates and record IDs, show a preview, and retry in a fresh test copy.
The simpler alternative
Use your existing contacts app plus a calendar reminder, or a spreadsheet with Name, Group, Last contact, Next contact, and Note columns. Build only when that makes regular follow-ups easier enough to justify upkeep.
When a specialist product may be worthwhile
Consider a dedicated personal relationship manager when you need dependable contact sync or reminders. Get developer help for sensitive information, shared access, migrations, or reliable cross-device recovery.
Sources and review
Documentation reviewed 2026-09-30. Plan limits and interfaces can change. How we prepare these guides.