Run each project on a board where every card is one external organization. The emails, meetings, and files with them get filed on that organization's page — so next project you drop the same organization on a new board and nothing is lost.
Free to start · No credit card required
You worked with them two projects ago. The emails are in one person's inbox, the deck is in someone's drive, the decision was made in a chat thread that scrolled away. That person has since left. So the next project starts by guessing.
Four places. No answer.
Their budget closes in September. Someone learned that in 2025. You'll learn it again in October.
Three good projects together, and the new lead sends a first-contact email.
Because the only index of past work is a conversation with the person leaving.
This isn't a CRM problem or a project-management problem. The work has a home. What you did with each organization doesn't.
Three screens, one external organization — Meridian Labs — followed from this project's board to their page and onto next year's board.
Columns are your stages. Every card carries the owner on your team, the person you're talking to over there, and how long it's been quiet. This is where the team spends the day.
A card is this project's chapter with that organization — not a copy of the organization.
Connect the team's Gmail and threads with that organization land on the work — not only in one inbox. Add the call notes and the signed PDF where you're already working.
Context is what you did with them: who said what, when, and what came of it.
The project ended; their page stayed. Every chapter, who owned it, how it ended, and every email, meeting, and file underneath — searchable by anyone on the team.
Adding them to the next project creates a new card, not a new organization.
If your projects end but the organizations come back, the history is worth keeping. OutPost is built for the teams below first — the model fits any work where emails, meetings, and files with a third party matter on the next project.
Same sponsors every year, a new exec team every year. The page outlasts the handover.
Long conversations, several people on both sides, a decision made months later.
Funders have cycles and rules. What they fund is worth writing down once.
Many programs contacting the same employers and partners, often unknowingly.
Small teams, high turnover, partners who've been around longer than staff.
Internal-only work and engineering issue tracking. No outside organization, nothing to keep.
Put your current project on a board, add the organizations you're talking to, connect the team's Gmail. In a month you'll have something no spreadsheet gave you: a page per organization that says what you actually did with them.
Free to start · No credit card required