Skip to content

Relationship-heavy roles

You live in introductions, follow-ups, and a wide circle—not just an org chart.

Lots of intros and follow-ups? Keep context next to each person.

High-touch roles need Interaction + Note density per Person, not a flat vCard export.

If your job is people—sales, BD, founders, investor relations, community—you need more than static contacts. Calero ties each person to what you have discussed, promised, and prioritised, with reminders so nothing important slips.

Sales, founders, and community roles need more than a flat address book. Calero links each person to what you talked about and what you owe them, with reminders so nothing slips.

You are optimizing for recall before calls: local graph, dated touchpoints, and search that hits the same SwiftData indices as the UI. No separate “CRM server”—just your device and optional CloudKit.

  • Log interactions and notes per person so the next coffee is informed
  • Circles for clients, partners, or communities
  • Spotlight and in-app search to open someone in seconds
  • Notes and interaction log per contact
  • Group people into circles
  • Search and Spotlight to open someone fast
  • Interaction rows keyed to personId + occurredAt
  • Circle membership filters list queries app-wide
  • Spotlight donations use stable entity IDs for deep links

Consultants & multi-hat operators

Switch context between portfolios without duplicating your life.

Juggle clients or boards? Separate them without duplicate apps.

One database, multiple scoped subgraphs via active circle + saved predicates.

When you serve several companies or programmes, one flat address book breaks down. Circles and filters let you wear the right hat for the meeting, while still keeping a single private database on your devices.

One address book gets messy when you serve many clients. Circles and saved views keep each context clean while your data stays in one private place.

Consultants benefit when context switching is a query parameter, not a second app install. Circles partition membership; filters reopen identical views; Kanban reads the same Project entities under whichever circle is active.

  • Contact circles to separate worlds (clients, boards, side projects)
  • Saved filters to reopen the same project or people view
  • Projects and scoring when delivery work stacks up
  • Circles for each world you work in
  • Saved filters for repeat views
  • Light projects when work piles up
  • Active circle is global UI state applied to fetches
  • SavedFilter serializes People/Projects query + sort
  • Project scoring runs on the same store under each scope

Leaders & operators in complex orgs

Map structure when you need it—without losing the human layer.

Need org structure and still care about individuals? Do both.

Org tables + relationship edges overlay the same Person primary keys.

Calero still shines when you must understand an organisation: who sits where, who influences whom, and which projects are blocked. That sits on top of rich person records, not instead of them.

When politics and reporting lines matter, you still need rich notes on people. Calero adds org mapping on top of person records, not instead of them.

Operators read both formal structure and informal power. Org mapping gives you Company/Team containers; relationships capture influence; project scoring ranks initiatives with explicit stakeholder roles—all local, queryable together.

  • Companies, teams, and reporting lines when work is political
  • Stakeholders and project scoring for initiative overload
  • Network view alongside lists for orientation
  • Companies, teams, and reporting lines
  • Stakeholders and priority on projects
  • Network view when lists are not enough
  • Team hierarchy and reports-to as first-class relations
  • Graph view renders directed edges between people
  • Dashboard cards can key off team / sponsor gaps

Personal CRM power users

Contacts-plus for people who outgrew the default Contacts app.

Outgrew Apple Contacts? One app for people, notes, and history.

Power users care about merge semantics, backup JSON, and optional CK sync.

If you have been maintaining spreadsheets or notes next to Apple Contacts, Calero is the upgrade path: one place for people, context, and light project tracking, local-first, with exports and optional CloudKit when you want sync.

If you pair Contacts with spreadsheets or notes, Calero is the single upgrade: people plus context, on device, with exports and optional iCloud when you want it.

This persona pushes the app like infrastructure: deterministic exports, dedupe tools, timeline replay across entities, and WidgetKit snapshots—all without handing the graph to a SaaS backend you do not control.

  • Merge duplicates and import vCards; export JSON for ownership
  • Timeline of notes, interactions, and project touchpoints
  • App lock, optional iCloud sync, widgets where available
  • Merge dupes, import vCards, export your data
  • Timeline across notes and projects
  • Lock, optional sync, widgets where supported
  • vCard → Person import; merge rewrites foreign keys
  • Full JSON export for backup / migration
  • CloudKit container optional; app lock wraps UI

See the full feature list

Use cases are stories; the features page is the catalogue. Documentation covers setup and data ownership.

Stories here; features lists everything. Docs explain setup and your data.

Narrative personas vs module catalogue; see docs for schema and export.

All features Documentation