Real deals.
Better infrastructure.

We are designing Parcl with people who work in real estate — not just people who build technology. That means listening to dealmakers, developers, legal teams and institutions before writing code.

Who we build for

Three kinds of work. One record.

01 / PROFESSIONALS

Real estate teams

Agents, acquisition teams, brokers and developers managing on-market and off-market property — often across several spreadsheets and an inbox.

Private dealrooms with scoped visibility
Offers, diligence and approvals in one thread
Parcel records that keep their sources
Long-lived leases and development rights

02 / COMMUNITY

Community organizations

Municipalities, nonprofits, community development corporations and neighborhood groups working with property intelligence and redevelopment.

Vacancy and underuse research with dates
Neighborhood context, not just parcel lists
Documented interventions over time
Public read access without a wallet

03 / INSTITUTIONS

Institutions & regulated platforms

Organizations that need reliable identity, compliant workflows, custody integrations, asset records and transaction verification.

Identity and eligibility, jurisdiction-aware
Approval chains and auditability
Custody and settlement integrations
Verifiable transaction evidence

Parcl does not provide custody, brokerage, title insurance, investment advice or legal services. Where those functions are required, they belong to licensed institutions and are integrated rather than imitated.

02 — Jurisdiction

A system that assumes one legal system only works in one place.

Recording practice, identity requirements, ownership restrictions and custody rules differ — sometimes between neighboring provinces. Our emerging Canadian opportunities have made that concrete rather than theoretical.

So the core stays city-neutral and the law stays in adapters. No jurisdiction is treated as the default that everyone else has to work around.

Questions the core is not allowed to hard-code
Who may own	Eligibility, residency and entity rules vary by jurisdiction and asset type.
How title is recorded	Registry, land titles and recording systems expose different data and different guarantees.
What identity is required	Verification depth, retention and disclosure obligations are local.
Which transfers are permitted	Restricted transfers, consent requirements and regulated ownership regimes are not universal.
Who may hold assets	Custody arrangements and settlement finality belong to licensed providers and local law.

How we work

Four principles, in order.

01 Start with the problem We would rather spend a session on your worst handoff — the version that lives in someone’s inbox — than demo a dashboard.

02 Prove it on one real deal Small, specific, unglamorous pilots. If a workflow cannot survive a difficult closing, it is not infrastructure.

03 Keep the record portable You should be able to leave with your evidence and verify it elsewhere. Lock-in is a business model, not a feature.

04 Respect local law and counsel No architecture decision outranks jurisdiction, a recording office or the lawyer advising the transaction.

04 — Contact

Let’s start with a conversation.

No intake form, no marketing sequence, no qualification quiz. One direct email address, read by the people doing the work.

Email lloyd@emelle.me

Helpful first message

The jurisdiction and asset type you work with.
The stage that hurts most — sourcing, diligence, approval, closing or retention.
Whether a pilot would involve live transactions or a historical sample.
Who else would need to approve working with us.

We are shaping early collaborations now. No unannounced commercial project is a confirmed client, and nothing on this page implies an existing partnership or endorsement.

05 — The standard

Real-world deals. Generation-scale thinking. Infrastructure that does not need to be believed in — only checked.

Explore the platform Our story