Fund it, build it, book it — on one set of numbers.
Agents read what arrives, check it against the books, and hand you the entry to approve.
Get in touchOne record for the deal, the build and the books.
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.
For developers running several projects, several entities and one set of books.
- 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.
Three products, one record underneath them.
Fi Invest
Deals, capital and what the funders see.
principals and investor relations
Investor and lender rooms
Fi Build
Cost, change and the team on site.
project managers and owner's representatives
The project team
Fi Book
Payables, reconciliation and the statements behind both.
controllers and bookkeepers
Vendor Portal
Whichever one you start in, the others are already reading the same records.
Issue a draw — the package, the G702 and the backup, assembled from the budget rather than by hand.
Budgets by cost code, draws, change orders and schedules that update as the documents land.

What happens between a document arriving and the books being right.
Work arrives from the places it already lands.
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. Six inboxes watched, not one drop zone. Nothing waits on a person to send it on.
Every document is read and checked against the books.
Classification, field and line extraction, five OCR backends, orientation, vendor resolution and cost coding — twenty-two workers in six groups. 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.
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.
The entry is written before anyone opens it.
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.
Numbers move together, and nothing is lost when they change.
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.
Ten you ask.Six that runwhether you arethere or not.
Every one of them proposes; none of them posts.
Nothing posts on its own — every entry comes back for you to approve.
- answers
- Answers are computed against the books as they stand, not a copy. Approvers are set for the company and for each project. Nothing automated runs until it is switched on.
- the tie-out
- The tie-out between QuickBooks, AppFolio and Cellect is a stored reference, not a hope.
Four units, one set of books, start to sold.
The Lugano ran on Fi from underwriting to the final distribution; three more are under construction on it now.
- the building
- Four residential units. 6,554 total sq ft. Three of four units with outdoor space.
- the run rate
- $100M+ in projects run on cellect. 4 projects live on cellect.