Extract offering memorandums to structured JSON
Offering memorandums present investment properties with financial projections, property details, and market analysis. OMs blend narrative with dense financial tables. Sensible converts OM data into structured JSON for deal screening, underwriting, and portfolio analysis.
Why offering memorandums resist automated extraction
Inconsistent tables, embedded photos, and broker-specific formatting make OMs highly variable.
Photos, market narratives, financial tables, all in one PDF. The extraction focuses on the numbers: structured data from financial sections, property details from the description, marketing content ignored.
Pro forma projections, cap rate analyses, cash flow schedules: each varies by broker and property type. Tables are extracted with their full multi-year structure into arrays your underwriting model consumes directly.
CBRE, JLL, Cushman, Marcus & Millichap: every brokerage uses their own branded OM template with different layouts, page ordering, and section naming. There is no structural standard. Sensible adapts to each broker's design while outputting the same acquisition analysis schema.
Fields we extract
Financial and property fields cover deal screening. Customize the schema for your acquisition model.
Property name, address, property type, year built, total units/SF, lot size, zoning, parking, occupancy rate, asking price/cap rate
Gross potential income, vacancy loss, effective gross income, operating expenses (itemized), NOI, cap rate, price per unit/SF, cash flow projections
Broker name, broker contact, seller information, marketing highlights, comparable sales, rent comparables, market overview
Shopping center or retail investment memo with lease abstracts and cap rate analysis.
Commercial office offering memorandum with tenant roster and NOI projections.
Investment offering for apartment properties with financials and unit mix.
Supported OM formats
Sensible processes OMs from any brokerage: CBRE, JLL, Cushman, Marcus & Millichap, and regional firms. The hybrid approach adapts to each broker's format while enforcing your target schema.
CBRE, JLL, Cushman & Wakefield, Marcus & Millichap, Newmark, Colliers, Berkadia, local/regional brokers
Multifamily, office, retail, industrial, mixed-use, hospitality, self-storage, senior living



Common Questions
Answers about OM parsing, financial projection extraction, and broker format support.
Sensible's table extraction handles multi-page financial schedules, rent rolls embedded in OMs, and comparable sales tables. Column headers and row labels are preserved in the structured output.
Sensible extracts property address, type, year built, total units or square footage, lot size, zoning, occupancy rate, and asking price. It also captures seller and broker information.
Yes. Sensible extracts income and expense tables, pro forma projections, cap rates, NOI, and cash flow schedules. Multi-year projection tables are returned as structured arrays.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
