Skip to content
AEKO

Supported workflows. No published product.

Real Estate

Prepare property work with the asset, contract, history, and owner attached.

Aeko prepares property, lease, maintenance, vendor, and portfolio work. The asset, contract, history, and named owner stay on the dossier. Liability, access, and spend stay with authorized people.

Property team working across documents, leases, and a building

Buyers

These buyers do not share the same dossier.

Property operations, facilities, leasing, portfolio reporting, vendor management, and systems each carry a different piece of the work. Aeko names the roles to bound the first process. One Agent does not cover all of them.

  1. 01

    Property operations

    Operations receive incomplete requests and must know who acts next. That is often the first workflow to map.

  2. 02

    Facilities

    Facilities carries incidents, access, and asset history. That is not the leasing dossier.

  3. 03

    Leasing

    Leasing carries leases, amendments, and tenant commitments. That file is not a facilities ticket.

  4. 04

    Portfolio reporting

    Portfolio reporting assembles buildings, leases, maintenance, and figures. The draft can be prepared. Publication is signed by a person.

  5. 05

    Vendor management

    Vendors and their certificates have dates, contracts, and gaps. Preparing a follow-up is not dispatching anyone.

  6. 06

    Systems

    IT owns the systems the workflow crosses: property, lease, accounting, CRM, documents, maintenance. Not the operating judgment.

Handoffs

Where the property dossier is rebuilt.

The stall is not a missing application. It is a dossier rebuilt at every handoff, without the asset, the contract, the history, or the named owner.

  1. 01

    Requests

    Requests arrive by portal, mail, phone, and site staff, often without enough context to act.

  2. 02

    Leases

    Tenant versus landlord responsibility lives in the lease. It is not always on the ticket.

  3. 03

    Asset history

    Interventions, parts, and known faults sit in another system, or in one person’s memory.

  4. 04

    Documents

    Leases, drawings, certificates, and photos travel beside the system of record.

  5. 05

    Vendors

    Coverage, certificates, and availability get lost between spreadsheets and inboxes.

  6. 06

    Reporting

    Portfolio reporting is rebuilt by hand from extracts that do not speak to each other.

Workflows

One dossier. One boundary. Context that remains.

None of these workflows is a published product. Each follows the same rhythm. An input, a prepared dossier, a human decision, then writeback to Company Brain and the systems of record.

Lease and document abstraction

Supported workflow. Not a published product.

  1. 01Lease, amendments, drawings, tenant correspondence
  2. 02The Agent prepares a sheet: clauses, dates, responsibilities, missing pieces
  3. 03A lawyer or property manager interprets the lease. The Agent does not conclude.
  4. 04The approved sheet strengthens Company Brain. The lease system remains the system of record.

Maintenance-request preparation

Supported workflow. Not a published product.

  1. 01Tenant or site request, photos, asset reference
  2. 02The Agent packs asset, contract, history, likely vendor, and missing evidence
  3. 03The facilities coordinator decides what happens next
  4. 04The approved decision strengthens Company Brain. The maintenance system remains the system of record.

Work-order routing

Supported workflow. Not a published product.

  1. 01Approved maintenance dossier, vendors, access constraints
  2. 02The Agent proposes a route and the information packet for the work order
  3. 03An authorized person dispatches the vendor. The Agent sends nobody.
  4. 04The approved work order is entered in the maintenance system. Company Brain keeps the owner and the rule.

Vendor and certificate follow-up

Supported workflow. Not a published product.

  1. 01Contracts, certificate dates, compliance history
  2. 02The Agent prepares follow-ups and the list of expired documents
  3. 03The vendor team decides whom to chase and what to require
  4. 04Approved dates stay in the document systems and strengthen Company Brain.

Portfolio-report preparation

Supported workflow. Not a published product.

  1. 01Building, lease, maintenance, and accounting data
  2. 02The Agent assembles a reporting draft with sources and gaps
  3. 03The report leaves after a person reviews it
  4. 04The approved report strengthens Company Brain. Accounting and the property system remain systems of record.

Tenant-service exception packets

Supported workflow. Not a published product.

  1. 01Complaint, service gap, commitment, history
  2. 02The Agent packs facts, contract, owner, and requested action
  3. 03Tenant commitments stay with people
  4. 04The closed exception updates the CRM and Company Brain. No commitment is sent without agreement.

Company Brain

Company Brain keeps the property context.

This is not another wiki. It is operating context the Agent reuses: mappings, rules, owners, and corrections already approved.

  • Asset register01
  • Property and tenant mappings02
  • Contract responsibilities03
  • Preferred vendors04
  • Service history05
  • Access rules06
  • Approval thresholds07
  • Validated resolutions08

Human boundary

The human decision stays visible.

The Agent prepares the dossier. Sensitive actions stop. The boundary is written, not implied by color. Property, lease, accounting, CRM, document, and maintenance systems remain systems of record.

  • Liability stays with people.
  • Legal interpretation stays with people.
  • Tenant commitments stay with people.
  • Safety stays with people.
  • Access stays with people.
  • Vendor dispatch stays with people.
  • Spend stays with people.

Workflow review

Bring one maintenance request and the systems it crosses.

In 30 minutes Aeko maps what can be prepared and what must remain a facilities decision.

Book a 30-minute review of maintenance-request preparation