CompStak is a commercial real estate comps platform built on a crowdsourced exchange model: brokers, appraisers, and researchers contribute verified lease and sales comps and, in return, earn credits that unlock access to the wider dataset. The result is one of the deepest sources of transaction-level lease comps in the market — actual signed rents, free-rent and TI concession packages, lease terms, escalations, tenant names, and sale prices that rarely surface in headline listing data.
Lease comps are the spine of office, retail, and industrial underwriting — and they are the single hardest input to assemble well. Asking rents are marketing numbers; what actually matters is the effective rent net of free months, TI allowances, and step-ups, plus how the deal was structured. CompStak's edge is exactly this transaction-level lease detail, which is why acquisitions, asset management, and valuation teams license it. The problem is operational: an analyst opens CompStak, filters a submarket, eyeballs a dozen comps, and retypes the relevant ones into the rent-comp tab of the model. It is accurate-ish, slow, and impossible to keep current across a pipeline of live deals.
Technical framework for CTOs evaluating AI solutions with Build vs Buy analysis
Auto-enrich contacts with property ownership, tax records, and market data
Keep HubSpot, Follow Up Boss, Salesforce, and spreadsheets in perfect sync
Discover how CompStak powers real estate automation workflows
Ingest the lease comps your team is entitled to under your CompStak license — via CSV/Excel export or, for enterprise customers, a provisioned data feed — capturing starting rent, free rent, TI allowance, lease term, escalations, and tenant.
Office, retail, and industrial underwriting lives on signed-lease economics, not asking rents. Automating ingestion turns a 30-minute retyping job into a clean, sourced comp set the moment you export it.
Get a personalized plan for your tech stack
Ready-to-deploy workflows powered by CompStak + NextAutomation
When a new deal reaches active underwriting, this workflow takes a CompStak export (or, for enterprise feeds, an authorized comp pull) for the subject's submarket and asset type, normalizes the comps to an effective-rent basis, scores them for comparability, and writes a clean, sourced rent-comp table into the underwriting model — so the analyst opens the model to a finished comp set instead of a blank tab.
1Workflow receives the subject property (submarket, asset type, target size band) and the licensed CompStak comp export or authorized feed pull
2Parse the comps: starting rent, free rent, TI allowance, term, escalations, tenant, and sale data where present
3Filter to the subject's submarket, asset type, and recency window using only comps the firm is licensed to use
4Normalize each comp to an effective-rent basis (net free rent and TI over term, apply escalations)
Every deal arrives with a normalized, ranked, source-attributed comp set already in the model. Analysts spend their time judging comparability and stress-testing rent, not retyping numbers from CompStak. The comps stay licensed-only and fully attributed.
Connect CompStak to your workflows with powerful triggers and actions
Fires when a new CompStak export (CSV/Excel) the firm has downloaded under its license lands in a watched folder or storage bucket, or when a scheduled authorized enterprise feed pull completes.
An analyst exports a submarket's lease comps from their CompStak seat into the shared drive; the automation picks it up and normalizes it into the deal's comp set automatically.
On a cron schedule, request the comp sets the firm is licensed to access for its watched submarkets — via export refresh or, for enterprise customers, a provisioned CompStak data feed/API.
Every Monday morning, refresh comps for the 12 submarkets where the firm holds active assets so the valuation dashboard starts the week current.
Read a licensed lease comp and extract starting rent, free rent, TI allowance, lease term, escalations, tenant, and floor/suite details into a structured record.
Convert a CompStak lease-comp row into a normalized record your model and dashboard both understand, with concessions broken out.
Compute an effective-rent figure for a comp by netting free rent and TI over the lease term and applying escalations, so comps are comparable on a single basis.
Turn a 'face rent $42, 6 months free, $60 TI' comp into a clean effective-rent number for apples-to-apples comparison across the set.
Filter the firm's licensed comps to a subject asset (submarket, asset type, size band, recency) and assemble a versioned, source-attributed comp set tied to the deal or property record.
Assemble the supporting comp set for a Class A office acquisition and freeze the version that backed the IC-approved underwriting.
Rank each comp's comparability to the subject — adjusting for floor, build-out, term, tenant credit, and concession structure — and return an ordered set with a rationale per comp.
Surface the three most defensible comps for a tower floor and flag the ground-floor retail comp as a likely exclusion with a reason.
Write a normalized, source-attributed comp table into an underwriting model (Excel/Google Sheets) or a property record, preserving CompStak attribution and as-of dates.
Drop the finished rent-comp table directly into the model's comps tab so the analyst starts from a populated, sourced set.
Push recomputed effective-rent, concession, and sale-comp metrics for a submarket into a valuation dashboard or BI tool, with source attribution retained.
Keep the asset-management dashboard's rent assumptions tied to the latest licensed comps and alert when a submarket conclusion moves.
Generate an IC-ready benchmarking narrative from the subject's licensed comp set — supportable face and effective rent, the driving comps, and excluded outliers with reasons.
Produce the rent-support section of an IC memo from the deal's comp set, formatted for GP review and attachment to the packet.
Get started in approximately 1-2 hours for the parse/normalize step and a first model-write workflow; half a day for the full refresh, dashboard, and monitoring suite
Before building anything, confirm with CompStak (or your account agreement) exactly how your firm is allowed to use and move its comps: manual export for internal use, an enterprise data feed/API, and any redistribution or seat restrictions. NextAutomation builds only customer-authorized, data-extraction workflows — they operate on comps your firm is licensed to access and never redistribute CompStak data outside your licensed seats.
Get the permitted-use answer in writing from your CompStak rep. The cleanest, lowest-risk path for most firms is internal export ingestion; an enterprise feed/API is worth pursuing only if your agreement explicitly provisions it.
Set up how licensed comps reach the automation. For the export path, define a consistent process: an analyst exports a submarket's comps from their CompStak seat to a shared folder or storage bucket in a stable column layout. For enterprise feeds, work with CompStak to provision the feed and capture credentials securely.
Standardize the export columns and filename convention (e.g., submarket + asset type + date). A predictable input is what lets the parser run unattended.
Create the core sub-workflow that reads a licensed comp file or feed payload and produces a normalized record per comp: starting rent, free rent, TI, term, escalations, tenant, and sale fields. Add the effective-rent calculation so every comp is comparable on one basis. Carry CompStak source attribution and the as-of date through every record.
Build this as a reusable 'CompStak Normalize' sub-workflow and call it from every downstream automation, so your effective-rent logic lives in exactly one place.
Connect the normalized comp set to its first consumer — typically the underwriting model. Build the path: trigger (new export / scheduled pull) → parse + normalize → filter to subject submarket → score comparability → write the attributed comp table into the model tab. Test with a real comp export for a deal in your pipeline and verify the numbers and attribution land correctly.
Add a fallback branch: if a comp file is malformed or a submarket returns too few licensed comps, route to a 'needs manual review' flag rather than writing an incomplete set into a live model.
Add the recurring workflows: the comp-set refresh that updates the valuation dashboard and the freshness check that flags deals whose comps have aged. Configure cadence (weekly is typical for valuation; align refreshes with your export rhythm), activate, and watch the first few runs to confirm filtering, normalization, and attribution behave as expected.
Log a one-line run summary (comps ingested, submarkets refreshed, conclusions moved) to Slack or a sheet after each scheduled run, so a change in CompStak's export format surfaces immediately as a zero-result anomaly.
Common questions about CompStak integration
Explore other tools that work great with your workflow
Get a free AI roadmap showing how to connect CompStak with your existing tools for maximum impact.
Get Your Free AI Roadmap