The problem

Relationships do not live neatly in one tab

Notes sit in three apps, context lives in your head, and the “real” org chart never matches how work actually happens.

Notes sit in three apps, context lives in your head, and the “real” org chart never matches how work actually happens.

Notes sit in three apps, context lives in your head, and the “real” org chart never matches how work actually happens.

• Threads and docs scatter across mail, chat, and files—then you walk into a meeting half-informed.
• Heavy sales CRMs optimize for pipeline, not for people you already know and need to stay close to.
• Spreadsheets and Notion boards go stale the week after you build them.

• You mean to check in, but life gets loud and names slip.
• Birthdays and milestones are buried in different places—or nowhere written down.
• Generic contact apps store numbers, not the story of how you know someone.

• Context is fragmented across silos; there is no single local graph keyed on Person.
• Cloud CRMs duplicate sensitive relationship data onto vendor infrastructure.
• Ad-hoc notes lack stable foreign keys into people, projects, and time.

The Calero answer

One private graph on your Apple devices

People, notes, interactions, projects, and optional org structure—local-first, with optional iCloud (CloudKit) sync across your own devices.

• Capture in seconds (Quick Add, share sheet) before the moment fades.
• Circles and saved filters match the hat you are wearing today.
• Dashboard and reminders answer “who needs me next?” without a sales pipeline.

• Gentle reminders and a timeline of touchpoints—not another social feed.
• Tags, circles, and notes so the next message is easy to write.
• Your data stays on your devices; optional sync uses Apple’s stack.

• SwiftData model with Person at the center; projects and org are optional overlays.
• Core Spotlight and App Intents integrate with system conventions.
• JSON export for backup and portability—no Calero-hosted graph.