Explore by following links
Open a contact and see who they work with, what they bought, and which documents name them. The graph view lays a company out with positions computed ahead of time, so it opens ready rather than settling in front of you.
A company's records usually live in a CRM, a few spreadsheets, a drive full of PDFs and a handful of exports nobody remembers making. Foundry reads all of them into one graph. A contact is linked to the deals they sit on, the invoices raised for them, the documents that mention them and the people who have worked with them, and you can open any of those links from the record in front of you.
Each record is a node. Each link between records is stored, labelled and searchable.
Open a contact and see who they work with, what they bought, and which documents name them. The graph view lays a company out with positions computed ahead of time, so it opens ready rather than settling in front of you.
Every node has a page with its properties, its connections, its comments from teammates and its history. Where a record came from is kept, so a figure can be traced back to the file or CRM table it started in.
Records carry dates, so the timeline shows what was created and updated in order. Saved views keep a filter and a layout you use often one click away.
Upload it, check the mapping, approve it. Not before.
CSV, TSV, Excel, JSON, XML, Word, PDF, plain text, Markdown, images, and the map formats GeoJSON, KML and GPX. Files can also be pulled from the company's drive.
The system proposes which columns become which properties and which rows should link to existing records. You can change the mapping, add connections, approve or reject the whole import, and the result is recorded in the chain of imports.
A file does not need to be sorted first. Foundry looks at what the data describes and suggests the record type it belongs to, with the suggestion shown to you to accept or correct.
For companies on DENDAT CRM the graph fills itself.
Questions are answered from the records in the graph.
Type a question the way you would say it. Foundry turns it into a query over the graph and keeps a history of what was asked, so a good question can be asked again.
Foundry reads the shape of a company's graph, such as which records are most connected and which sit alone, and writes up what it sees as a short list of things worth acting on.
When two records probably belong together, Foundry says so and shows why. A person confirms each one before the link is created.
The graph stays tidy because something is checking it.
A scan finds records that look like the same thing entered twice. Review the pair, then merge them into one.
Records that break the pattern of the rest are listed for a person to look at: important records with no links, small clusters cut off from the main graph, unusually over-connected records and repeated links between the same two records.
Save the state of the graph, and later compare two snapshots to see exactly what was added, removed or changed between them.
Follow the entities that matter. When one of them changes, an alert appears in the notification list.
Summaries of the graph are available as reports, and the data can be exported as CSV or JSON.
Records that are removed go to the recycle bin first, so a wrong deletion can be undone.
Foundry is a working tool for people who answer questions with company data.
People who are asked "how are these connected?" and currently answer it by opening four tabs.
People who want one place to look at the whole business, with each figure traceable to where it came from.
Sign in with your DENCRM account or your Foundry email and password.