for the builders ahead of the curve
Fund it, build it,book it — on oneset of numbers.
Agents read what arrives, check it against the books, and hand you the entry to approve.
For developers running several projects, several entities and one set of books.
fig. 01
Issue a draw — the package, the G702 and the backup, assembled from the budget rather than by hand.
fig. 01 — one draw package: the cover sheet that foots, three tabbed parts behind it and the schedule of values pulled out of the stack. Completed and stored to date is the same figure in both places, which is what assembled means.
what this is
One record for the deal, the build and the books.
Investment management, construction and accounting in one place. One set of numbers, whoever is asking — the sponsor, the team on site, or the people who funded it.
- 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.
how it works
What happens between arrival and approval.
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.
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.
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 gets asked to look at 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. Change an assumption and every report moves; the old one is still there.
the three
Three ways in, one set of records.
Fi Invest
Deals, capital and what the funders see.
principals and investor relations
Fi Build
Cost, change and the team on site.
project managers and owner’s representatives
Fi Book
Payables, reconciliation and the statements behind both.
controllers and bookkeepers
each door is what the people outside your company get to see
case study
Four units, one set of books, start to sold.
Shape develops small multifamily in Jersey City through a separate company for each project. The Lugano ran on Fi from underwriting to the final distribution; three more are under construction on it now.
Budget by cost code, with committed, incurred and paid coming from the documents themselves. Draws assembled from the budget rather than by hand; RFIs and change orders answered in a thread and landed back on the line they moved.
- 4
- residential units
- 6,554
- total sq ft
- 3 of 4
- units with outdoor space
- 4
- projects live on cellect
$100M+ in projects run on cellect
what is guaranteed
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.
- Approvers are set for the company and for each project. Nothing automated runs until it is switched on.
- The tie-out between QuickBooks, AppFolio and Cellect is a stored reference.
the ask