Buy-box fit
Leads are organized around asset class, geography, parcel/use context, and source-backed property facts.
Find acquisition leads worth analyst time.
Define your market, asset class, and buy-box. Acren reviews coverage, builds a ranked acquisition agenda from public records, and gives each lead a source-backed packet before your team spends time on comps, lease color, broker calls, or expense underwriting.
Build the acquisition universe before the market is obvious.
Acren starts with explicit territory, asset class, and buy-box criteria. Coverage is reviewed before any property enters the lead universe. The output is not a buy recommendation. It is a cleaner list of properties worth the next diligence step.
Rank opportunities, then route diligence.
Owner/entity context
Recorded owner, entity filing, officers, and related-property context are attached where reviewed sources support them.
Source trail
Every lead keeps the recorder, assessor, entity, permit, tax, or other reviewed source visible.
Open questions
Unsupported fields stay as questions so analysts know whether to pull comps, ask a broker, confirm lease color, or review expenses.
Off-market without intent claims
Use public records to rank research priority, not to infer whether an owner wants to transact.
- 1 · Scope
Market, asset class, and buy-box defined explicitly. Coverage reviewed before activation.
- 2 · Universe
Reviewed records enter the acquisition agenda with source-backed context and open questions.
- 3 · Rank
Leads ranked by buy-box fit and public-record support, never by inferred intent.
- 4 · Inspect
Open the opportunity memo, read the source trail, and decide the next diligence step.
- 5 · Route
Send to comps, broker follow-up, lease review, expense review, monitoring, or dismissal.
What happens after Acren surfaces a lead?
Broker conversation
Ask for local color, owner knowledge, lease or rent context, and whether the property fits the market.
Sales comps
Pull comps to test pricing assumptions. Acren does not provide valuation.
Lease/rent research
Use broker, lease-intelligence, or internal data to test rent assumptions. Acren does not invent rent.
Tax and insurance review
Confirm tax history, assessment posture, insurance cost expectations, and local risk factors.
Expense review
Confirm operating expenses before underwriting.
Capex and condition review
Review permits, visible condition, inspections, and renovation needs.
Debt assumptions
Use lender and broker inputs. Acren does not provide financing advice.
Underwriting
Decide whether to model, watchlist, call, assign, or pass.
Acren helps decide which leads deserve those checks.
It does not perform or replace broker conversations, sales comps, lease research, expense diligence, capex review, debt assumptions, underwriting, legal review, or investor judgment.
Acquisition agenda
3 items · mandate-weighted
| Priority | Property | Market | Why surfaced | Confidence | Verdict |
|---|---|---|---|---|---|
| High | Acquisition lead | reviewed market | Asset-class, parcel, and ownership records align with the buy-box | Source-backed | Pull comps |
| High | Broker follow-up lead | reviewed market | Operating detail needs source confirmation | Needs review | Ask broker |
| Medium | Expense review lead | reviewed market | Operating-use context is source-dependent | Medium | Confirm expenses |
Lifecycle of an acquisition lead.
| Stage | What Acren does | Customer action |
|---|---|---|
| Surfaced | Property enters the lead universe with source trail attached | Review why it surfaced |
| Reviewed | Packet labels owner/entity context and open questions | Save, assign, or dismiss |
| Next diligence | Lead carries a suggested next step | Pull comps, ask broker, review leases, confirm expenses |
| Monitored | Watchlist tracks source updates and entity changes | Receive packet revision on change |
| Outcome | Closed, declined, or lost feedback writes back to workflow history | Mark outcome with reason |
Opportunity memo preview
opportunity memo · source-backed
Acquisition lead · reviewed market · records match within reviewed source set.
- Why it surfaced
- Asset-class, parcel, and entity context align with the defined buy-box.
- Supporting records
- REC-DED · ASR-PARC · SOS-ENT
- Confidence
- Source-backed
- Open questions
- Sales comps, lease color, operating expense assumptions, and permit history need customer review.
- Owner / entity context
- Resolved owner context; related-property links labeled separately.
- Next diligence step
- Save to universe; route to comps and broker follow-up.
Next action
- →Review packetInspect every supporting record
- →Save to universeAdd to reviewed acquisition set
- →Move to needs researchFlag verification gaps
- →Assign analystRoute to team workflow
- →MonitorWatch for source updates
How is ranking decided?+
By buy-box fit, record completeness, confidence band, source status, and public-record support. Acren never ranks by inferred intent.
What happens to dismissed records?+
They remain in the universe with the dismissal reason attached, so a future re-review can replay the decision.
Does Acren replace comps, lease research, or expense underwriting?+
No. Acren helps decide which leads deserve that work. Investors still make decisions with comps, market lease research, broker feedback, and expense assumptions.
“The product is a better lead list, not a guess about what an owner is thinking.”
Pipeline building
Lead first
Start with properties worth research time.
Source-backed reasons
100%
Every ranked lead carries its source trail.
Inferred-intent signals
0
Acren never publishes psychological inference.
Acquisition workflow
Build a better opportunity pipeline.
Bring your buy-box and a market. Acren returns a ranked acquisition agenda backed by public records, with next diligence steps attached.
Responsible use
Research priority, not seller intent
Acren ranks commercial property research priority. It does not infer disposition, hardship, or willingness to transact.
Responsible use
Source evidence required
Every recommendation must carry supporting records, field-level rights status, and verification gaps.
Responsible use
Verification before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-visible, generalized, internal-only, and suppressed fields stay visible as product controls.
Continue
See how each opportunity keeps the source trail attached.