cellect aia technical note

for the builders ahead of the curve

Fund it, build it, book it — on one set of numbers.

Construction management AI agent for tech-forward developers.

Get in touchSee how it works

One plan in three chambers — fund, build and book — over a single baseline.fundbuildbookone set of numbers
fig. 00 — keycellect ai

What happens between a document arriving and the books being right.

Five stages, in one direction

what it is

Investment management, construction and accounting in one place, not three.

One set of numbers, whoever is asking — the sponsor, the team on site, or the people who funded it.

Whichever one you start in, the others are already reading the same records.

$100M+in projects run on cellect

Three product bands hung off one shared rail, each with a door opening outward to the people who are not in the company.Fi InvestDeals, capital and what the funders see.principals and investor relationsinvestor and lender roomsFi BuildCost, change and the team on site.project managers and owner’s representativesthe project teamFi BookPayables, reconciliation and the statements behind both.controllers and bookkeepersVendor Portalone set of records
fig. 01 — three products, three outward doorscellect ai

for the sponsor

Scenario models, debt schedules and waterfalls on one set of numbers.

for the team building it

Budgets, draws and change orders, current while you can still act on them.

for the people keeping the books

Invoices read, transactions matched, entries proposed for approval.

for the people who funded it

Investor statements and data rooms built from live project data.

nothing to upload

Work arrives from the places it already lands.

Nothing is uploaded, and nothing waits on a person to pass it on.

Six outside sources dropping into one lane that runs to a single reading point.emailSharePointDriveSlackbank feedvendor portalreadpolled, not pushedevery 2 mintwo-day lookback
fig. 02 — six inboxes, not one drop zonecellect ai

Agents pick up work from email, Slack or shared drives.

Email is polled every two minutes. SharePoint channels, the Drive mirror, Slack threads, the bank feed and vendors uploading to their own portal all arrive the same way.

Inboxes, bank feeds and records are watched continuously.

Six inboxes watched, not one drop zone. Nothing waits on a person to send it on.

nothing to retype

Every document is read and checked against the books.

The vendor, the cost code, the commitment and the bank line are matched before anyone looks.

Six named worker groups over a rail of twenty-two tally marks.classificationfield and line extractionfive OCR backendsorientationvendor resolutioncost codingsix groupstwenty-two workers
fig. 03 — twenty-two workers, six groupscellect ai

Always-on agents read every document.

Classification, field and line extraction, five OCR backends, orientation, vendor resolution and cost coding — twenty-two workers in six groups.

Records, budgets and communications are cross-referenced.

Bank transactions are matched against ledger lines, invoices, commitments and cash events. Matching, second-pass review and agentic resolution run on a job, not on a click.

A bank line from outside, matched against four kinds of internal record.bank feedledger linesinvoicescommitmentscash events
fig. 04 — what one bank line is read againstcellect ai

nothing to assemble

What leaves the building is assembled from the same records.

Rooms, packages and drafts are built from the project itself, not collected by hand the week they are due.

Four things assembled inside the company crossing an edge to four parties outside it.data roominvestors and lenderssignature packagethe counterpartyRFI and change orderthe project teamchecklistthe recipient
fig. 05 — the company edge, and what crosses itcellect ai

Documents are filed into data rooms.

Pulled live from the library rather than copied, with per-recipient access. The investor package is built from project data as slides, sheets or web.

Signature packages are prepared and sent.

Geometry finds the signature lines, the agent proposes the parties, code validates the result, and the send is verified against the mail-transport event.

RFIs and change orders are drafted from the source document.

The question is written from the drawing or the letter it came in on, linked to the budget line it affects.

Checklists chase the recipient, not you.

Shared checklist items are exposed to the recipient, tasks are assigned per recipient, questions are threaded and the sheets they fill in stay in the room.

no data entry

The entry is written before anyone opens it.

How sure the agent is decides who gets asked to look at it.

One proposed entry forking two ways — a confident match to accounting, an unclear one back to the deal team.proposed entryaccountingthe deal teamconfidentunclear
fig. 06 — how sure decides who is askedcellect ai

Payables and transactions are coded before anyone opens them.

Waiting when you arrive, not queued for you to start.

Clear cases go to accounting, unclear to the deal team.

How sure the agent is decides who sees it. A confident match goes to the accountant; an unclear one goes back to the person who knows what the money was for.

Once approved, work is booked and filed.

Approvers are set for the company and for each project. Nothing automated runs until it is switched on.

nothing overwritten

Numbers move together, and nothing is lost when they change.

Every version is kept, every figure keeps its source, and the tie-out across systems is stored rather than assumed.

Four offset plates, three of them superseded and still drawn, one current in front.v1v2v3v4currenttwenty-two kinds of recordversioned
fig. 07 — nothing overwrittencellect ai

Every change keeps what it replaced.

Twenty-two kinds of record are versioned — budgets, deal models, valuations, positions, vendors, entity facts, draws and loan terms. Change an assumption and every report moves; the old one is still there.

Every number keeps its source.

Each screen declares where its figures came from, and every open item carries the evidence and the trail of who acknowledged it.

Numbers tie out across every system.

The tie-out between QuickBooks, AppFolio and Cellect is a stored reference, not a hope.

what it covers

Seven capabilities, drawn on the same set of records.

Six of them are the work itself. The seventh runs under the other six.

A drawing-set index listing seven sheet numbers against seven capability names.a-01Dealsa-02Capitala-03Constructiona-04Accountinga-05Reportinga-06Diligenceq-01Automation
fig. 08 — the sheet indexcellect ai

a-01

Deals

Sourcing, zoning and underwriting in one place, so a deal arrives at committee with its numbers already attached.

  • Site & Zoning Research
  • Underwriting Models
  • Investment Committee Memos
  • Approval Workflows
  • Municipal & Market Data

a-02

Capital

Positions, calls, distributions and debt tracked as money actually moves, not reconstructed at quarter end.

  • LP Positions
  • Capital Calls & Distributions
  • Debt Schedules
  • Refinancing Analysis
  • Equity Waterfalls

a-03

Construction

Budgets by cost code, draws, change orders and schedules that update as the documents land.

  • Budgets & Cost Codes
  • Draw Packages
  • RFI Logs
  • Schedule Milestones
  • Change Orders

a-04

Accounting

Invoices read, transactions classified and entries proposed — then posted to QuickBooks once you approve.

  • Invoice Intake
  • Bank Reconciliation
  • Vendor Registry
  • Fee Billing
  • QuickBooks Posting

a-05

Reporting

Statements, board packs and performance drawn straight from the project itself.

  • Investor Statements
  • Board Packs
  • Portfolio Performance
  • Audit Trails
  • Report Packages

a-06

Diligence

Documents classified on arrival and shared through rooms you control, rather than an email chain.

  • Data Rooms
  • Document Classification
  • Diligence Checklists
  • Signature Packages
  • Access Controls

the seventh

The inbox, the bank feed and the numbers, kept current in the background.

Nothing posts on its own — every entry comes back for you to approve. Answers are computed against the books as they stand, not a copy.

  • Invoice Extraction
  • Transaction Classification
  • Bank Reconciliations
  • Slack & Email Intake
A proposed entry running into a gate that only opens on an approval, and on to the books.proposed entryyou approvethe books
fig. 09 — nothing posts on its owncellect ai
Three systems on three rails, joined by one stored reference.QuickBooksAppFolioCellecta stored reference
fig. 10 — the tie-out is stored, not assumedcellect ai

QuickBooks Online

System of record — every entity, kept correct automatically

AppFolio

Investor positions, contributions, and distributions

Microsoft 365

Invoice intake straight from email and SharePoint

Slack

Reconciliation and RFI questions land where your team works

next

See it on your own numbers.

Get in touch

Tell us a bit about your project and we’ll get back to you.

Get in touch

Read the five stages

What happens between a document arriving and the books being right, stage by stage.

how it works →

Look at the three products

Fi Invest, Fi Build and Fi Book, each with its own work and its own buyer.

fi →

Further reading

  • Shape Equity Partners →Four units, one set of books, start to sold. The Lugano — 477 Monmouth Street, Jersey City.
  • Eleven jobs, three parts →Fi Invest, Fi Build and Fi Book each carry their own work. The reason they hold together is underneath: one set of records, read by all three.
  • The five stages →Five stages, in one direction. Work arrives from the places it already lands, is read and checked, and comes back as a decision waiting to be made.
cellect aip52 · staging variant · not indexed