anvisto
doxread by Anvisto

Turn documents into structured data.

Extract fields from PDFs, Word documents, and PowerPoint decks and map them to the schema your business systems expect.

Compare three responses to one RFP

In this fictional example, a sponsor issues a request for proposals for an inventory reporting platform. Three vendors reply with a PDF, a Word document, and a PowerPoint deck. Reviewers need to compare each submission against the same criteria and check the original wording when a response is ambiguous.

  1. Collect responses

    Group each submission and its source documents under RFP-104. Use the sponsor’s criteria to define what to extract.

  2. Map the data

    Extract pricing, rollout estimates, support hours, and exceptions into consistent fields. Keep the document and page, section, or slide reference alongside each value.

  3. Review in Salesforce

    Map the structured records to Salesforce custom objects. The sponsor reviews the comparison, opens source references, and follows up on missing answers.

Example Salesforce object model

One RFP can have several vendor submissions. Each submission can have multiple criterion responses, allowing the review team to compare the same criterion across vendors.

  1. RFP

    One parent record for RFP-104, its scope, the submission deadline, and the review criteria.

  2. Vendor Submission

    One child record per vendor response, with the vendor label and references to its source files.

  3. Criterion Response

    One record per criterion per submission, with a normalized value, a source locator, and a review status such as Extracted or Missing.

What the sponsor can compare

Fictional RFP-104 responses. Source locators identify where the sample values came from.
CriterionVendor A · PDFVendor B · WordVendor C · PowerPoint
Year-one costUSD 84,000p. 6, pricingUSD 92,000§ 4, commercial termsUSD 79,000slide 8, fees
Rollout estimate12 weeksp. 9, delivery plan10 weeks§ 3, timeline14 weeksslide 6, delivery
Support coverage24/7 for critical incidentsp. 11, service levelsBusiness hours§ 5, supportNot provided
Scope exceptionsMigration billed separatelyp. 12, exclusionsTwo data sources included§ 2, scopeTraining billed separatelyslide 9, assumptions

The sponsor can flag Vendor C’s missing support terms for follow-up and check what each quoted price includes before comparing total costs.

Send structured data where reviews happen

Salesforce is the destination in this example. Map outputs to the schema your review system expects, or use an integration layer such as MuleSoft to transform and route records to downstream systems.

Explore Anvisto products