Relationships

Relationships is the shared contact and account layer that runs across all of Foundaro. Contacts and accounts you add here can be linked to investors in Capital, buyers in Exit, team members in People, and partners in Partnerships — creating a single source of truth for your entire professional network.

The module is built around the idea that founders maintain multiple overlapping networks: investors they meet during fundraising, potential acquirers they cultivate years in advance, hires they track before a role opens, and partners they develop through business development. Keeping those networks in separate spreadsheets means missed warm intro opportunities and duplicated effort. Relationships centralises everything.

Overview

The Overview tab is the at-a-glance health dashboard for your relationship network. It surfaces the numbers that matter most without requiring you to navigate into each tab.

Stats bar — Eight key metrics are shown at the top:

• Contacts — Total relationship contacts in the system.
• Accounts — Total shared company accounts.
• Linked records — The number of module entities (investors, buyers, partners, team members) that have been connected to a shared relationship contact or account.
• Meetings — Total meeting log entries across all contacts.
• Today's meetings — Meetings scheduled for today, giving you a quick daily agenda.
• Needs follow-up — Meetings marked as completed but with no follow-up action recorded. These are the conversations at risk of going cold.
• Overdue actions — Planned meetings whose date has passed without a status update.
• Import queue — Module entities that have been flagged as candidates for relationship import but not yet linked.

Quick action links — Three buttons take you directly to add a contact, add an account, or log a meeting. These are faster than navigating to the individual tab when you just want to capture something quickly.

Recent contacts — The six most recently updated contacts, showing name, email, title, and account. Click through to the Contacts tab to view and manage the full list.

Recent accounts — The six most recently updated accounts, showing name, domain, company type, and contact count.

Upcoming meetings — Planned meetings that are in the future, up to five shown. This is your prep reminder list for the week ahead.

Warm intro opportunities — Contacts who share an email domain with a module entity that has not yet been linked. These are the highest-value introductions to pursue because the relationship evidence already exists.

Recent activity — A timeline of the ten most recent activity log entries across all contacts, including notes added, meetings logged, and follow-ups recorded.

Tips:

• Review the overview at the start of each week to identify which conversations need follow-up.
• Import queue items represent an efficiency opportunity — link them to reduce future data entry.
• Warm intro opportunities are ranked by recency of the underlying module entity, so the ones at the top are most actionable.

Contacts

The Contacts tab is where you manage individual people in your network. Each contact is a shared record that can be linked across modules, so adding a contact here means you never need to enter the same person's details in Capital, Exit, and People separately.

Contact fields:

• Name — Required. The person's full name.
• Email — Their primary email address. This is used for domain matching against investor, buyer, partner, and team records — it is how warm intro opportunities are detected.
• Title — Their current role or job title.
• Account — The company they work at. Linking to a shared account connects this contact to all other contacts and module entities at the same organisation.
• Tags — Freeform labels for segmenting your network (e.g. investor, advisor, journalist, warm-intro). Tags are searchable and useful for filtering when your network grows large.
• Notes — Freeform context: how you know them, what they care about, previous conversations.

Filtering and sorting:

• Search by name, email, title, or account name.
• Filter by account to see everyone at a specific company.
• Sort by name A–Z, name Z–A, recently updated, or most linked (contacts with the most module connections appear first).
• Pagination shows 12 contacts per page.

Import queue — When you add an investor in Capital, a buyer in Exit, a team member in People, or a partner in Partnerships, Foundaro checks whether a relationship contact already exists for that person. If not, the module entity is added to the import queue and shown at the top of the Contacts tab. Click Import to create a linked contact automatically. This keeps your relationship network in sync with your operational modules without double entry.

Create investor / Create buyer links — When adding or editing a contact, you can flag that this contact should create a corresponding investor in Capital or buyer in Exit. These shortcuts are useful when you meet someone at a conference and want to create the relationship record first, then fill in the operational details in the relevant module later.

Tips:

• Always check whether a contact already exists before adding a new one. Use the Manage tab's lookup tool to search by name, email, or domain first.
• Tags are most useful when you keep them consistent. Decide on a small set of canonical tags early and stick to them.
• Link contacts to accounts so that the Relations graph accurately reflects your company-level coverage.
• Import queue items should be processed regularly — unlinked module entities miss out on meeting history and activity logging.

Accounts

The Accounts tab manages company-level records. An account is a shared organisation record that contacts are grouped under and that module entities are linked to. It is the hub that connects an investor's firm, a potential acquirer, a partner company, or a customer.

Account fields:

• Name — Required. The company name.
• Domain — The company's website domain (e.g. acme.com). Domain is the most important field for deduplication and warm intro detection. Foundaro normalises domains automatically — entering https://www.acme.com/about will save as acme.com. Always set the domain when you know it.
• Tags — Labels for categorising accounts (e.g. vc, acquirer, strategic-partner, customer). Tags feed into relationship filtering and lookup.
• Notes — Context about the company: investment thesis, acquisition history, relationship background, or anything else useful to remember.

Metadata displayed per card:

• Normalised domain — Shows the cleaned domain or "No domain" if none is set.
• Company type — Inferred from the domain extension and contact patterns (e.g. VC / Investor, Enterprise, Startup, Unknown).
• Location hint — Inferred from domain extension and email patterns where possible.
• Contact count — How many relationship contacts are linked to this account.
• Link count — How many module entities are linked to this account.
• Last updated — When the account record was last modified.

Filtering and sorting:

• Search by name, domain, or tag.
• Sort by name A–Z, name Z–A, recently updated, or most contacts.
• Pagination shows 12 accounts per page.

Deletion behaviour — Deleting an account does not delete the contacts under it. Contacts are detached (their accountId is cleared) but preserved. Activity logs, relationship links, and module entity associations are also removed. Underlying CRM records in Capital, Exit, etc. are never affected.

Tips:

• Set the domain on every account you create. Domain is what drives warm intro matching and deduplication.
• Use tags to mark account types so you can filter your network by relationship category.
• If you have multiple accounts that represent the same company, use the Manage tab to merge them rather than manually reconciling.
• Accounts with zero contacts and zero links can safely be removed to keep the data tidy.

Relations

The Relations tab renders the full relationship graph — a structured view of how contacts, accounts, and linked module entities connect to each other. It is the answer to "who do we know at this company and what do they overlap with?"

Graph structure:

• Each account is a hub node. Under each account, you see its linked contacts and, for each contact, the module entities they are connected to.
• Contacts without an account affiliation appear in a Standalone contacts section at the bottom of the graph.

Module badges — Each linked entity shows a coloured badge indicating which module it belongs to:

• Capital — Investor (green badge)
• Exit — Buyer (blue badge)
• People — Team member (purple badge)
• Partnerships — Partner (amber badge)

The badge appears next to the entity name and shows the entity's current status (e.g. pipeline stage for investors, deal status for buyers).

Coverage label — Each account hub shows a coverage label summarising how many of its contacts are linked to module entities. High coverage means you have strong operational context for this company. Low coverage means you know people there but haven't connected the dots.

Filtering — The search bar filters by account name, contact name, or linked entity name. This lets you quickly navigate to a specific company or person in a large graph.

Inline editing:

• Edit or delete contacts directly from the graph without navigating away.
• Delete accounts from the graph (same detach-and-preserve behaviour described in Accounts).

Tips:

• Use the Relations graph before outreach to understand your full coverage of a target company. If you know three people there across Capital and Exit, you can approach from multiple angles.
• Standalone contacts represent network gaps — people with no account affiliation. If you know where they work, link them to an account.
• The graph does not paginate — all accounts and contacts are shown. Use the search bar to navigate in large networks.
• Coverage labels are useful for identifying which accounts are under-connected. Low coverage on a strategic acquirer or lead investor is a signal to do more introductory meetings.

Meetings

The Meetings tab is the operational log for your relationship conversations. Every time you have a meaningful meeting with a contact, you log it here. The log drives the follow-up workflow, action item tracking, and activity timeline.

Meeting stat bar:

• Today's meetings — Meetings scheduled for today.
• Needs follow-up — Completed meetings with no follow-up draft or action recorded. This is the most important number to keep at zero.
• Missing next step — Planned meetings with no next step defined. Set next steps before a meeting so you enter the room with a clear objective.
• Overdue actions — Planned meetings whose date has passed. These are either cancelled, missed, or forgotten — they need a status update.

Meeting fields:

• Title — What the meeting is about (e.g. "Intro call — Jordan at Acme Capital").
• Contact — The relationship contact this meeting is with.
• Linked module — Optionally link to an investor, buyer, partner, or team member to connect meeting history to operational records.
• Date — When the meeting is or was scheduled.
• Status — planned or completed. A meeting cannot generate follow-up actions until it is marked completed.
• Meeting type — Intro, check-in, pitch, diligence, negotiation, other.
• Next step — The specific action to take after this meeting to advance the relationship.

Prep section — Before a meeting, use the prep section to capture talking points, questions to ask, and background research. This lives inside the meeting record and can be referenced during the call.

Notes section — During or after a meeting, add freeform notes. What was said, what was agreed, what changed.

Action items — Structured follow-through captured as a checklist. Each action item has a description and optional due date. Action items from meetings feed into the activity timeline.

Follow-up draft — A freeform field for drafting the follow-up email or message. Keeping the draft inside the meeting record means you can write it immediately after the call while context is fresh, then copy it out when you're ready to send.

Activity log — Each contact has an activity timeline that shows all meeting entries, notes, and logged actions in chronological order. Click "Activity log" on any meeting card to view the full timeline for that contact.

Composing a meeting via deep link — If another part of Foundaro links to /relationships/meetings?composeMeeting=1, the new meeting dialog opens automatically. This is used by modules like Capital and Exit to let you log a meeting without navigating away from your workflow.

Tips:

• Mark meetings as completed as soon as they happen. "Needs follow-up" is only accurate when completed meetings are recorded promptly.
• Write the follow-up draft immediately after the meeting, before you forget the tone and specifics.
• Use action items for concrete commitments, not vague intentions. "Send deck by Friday" is an action item. "Follow up at some point" is not.
• Link meetings to module entities so that investor, buyer, and partner records show meeting history inline.
• A planned meeting with no next step is a red flag. What is the objective of the meeting? Define it before you go in.

Manage

The Manage tab provides two maintenance tools: relationship lookup (to check for existing records before creating new ones) and duplicate resolution (to merge records that were created in parallel).

Lookup and enrichment:

Before creating a new contact or account, search here. The lookup queries across:

• Contact names, emails, and titles
• Account names and domains
• Linked module entity names and identifiers
• Relationship links

Enter a name, email address, or domain. Results show matching contacts, accounts, and linked entities, along with the module they belong to and their current status.

Use this tool when:

• Someone gives you a business card and you want to check if they're already in the system.
• You're about to add a new investor firm and want to confirm there's no existing account with the same domain.
• You want to see everything Foundaro knows about a specific person before reaching out.

Duplicate resolution:

Foundaro detects potential duplicate records using domain matching for accounts and email/name matching for contacts. Duplicate groups are shown with a primary record (the one with the most complete data) and one or more duplicates.

Merge behaviour:

• Account merge — All contacts, links, meetings, and activities from the duplicate accounts are migrated to the primary account. The duplicate account records are then deleted.
• Contact merge — All links, meetings, and activities from the duplicate contacts are migrated to the primary contact. The duplicate contact records are then deleted.

Merges are non-destructive to underlying module records. Investors, buyers, partners, and team members are never deleted by a relationship merge — only the relationship layer is consolidated.

Data summary — A tile at the bottom of the page shows the total count of contacts, accounts, links, and activities in your workspace. If duplicate groups are detected, a warning banner appears with the count and a prompt to resolve them.

Tips:

• Run lookup before every new contact or account creation. Duplicate data is harder to clean up than it is to avoid.
• Domain search is the most reliable lookup method for accounts. Email address is the most reliable for contacts.
• After a merge, verify the primary record's fields are correct. Merges migrate data but do not update fields — if the primary had outdated contact info, you may need to edit it manually.
• The duplicate detection algorithm is conservative. It flags definite duplicates but may miss near-matches (e.g. "Acme Ventures" vs "Acme Ventures LLC"). Use lookup to catch these manually.
• Review the data summary monthly. A growing "Links" count relative to contacts and accounts means the network is becoming well-connected. A stagnant or zero count means module entities are not being linked to relationship records.

See also: Automations guide — automatically create follow-up tasks from meetings and get notified when accounts go stale.