See the project behind the report.
GlassLedger connects, read-only, to the email, project software, files and accounting your project runs on. It tracks what happens each day, flags what changed, and checks each report and invoice against the record.
- Read-only access
- Nothing for the project team to install
- Built on NimbleBrain
Sample project. Illustrative data. Flip between the report and the record.
The project moves every day. The report comes once a month.
Between reports you work from a document the project team wrote about itself.
It is weeks old
A monthly report describes work that ended weeks before you read it. A draw request asks you to fund work you last saw a month ago.
The project team writes it
The developer, the contractor and the construction manager summarize their own work. You read the summary.
It depends on data entry
Project software holds what someone remembered to log. The live conversation runs through email, calls and chat.
It reads the work where the work happens.
A project leaves a trail in the tools people use each day. GlassLedger reads that trail against criteria you set.
- 01
Connect, read-only
Email, project software, files, chat and accounting for each party, as agreed. The project team installs nothing and fills in nothing.
- 02
Set the criteria
You say what counts as risk on this project, in plain English. Change the criteria any time.
- 03
It watches
GlassLedger reads each new message, update, file and invoice against your criteria as they arrive.
- 04
You see it
A live board, an alert when a criterion trips, and a weekly brief. Each flag links to its evidence.
- Flag any topic with five times its usual message volume.
- Flag any trade with no activity for seven days.
- Flag any issue with no next step after five days.
- Flag any invoice line the record does not support.
Connectors for Gmail, Outlook, Teams, Slack, Zoom, Google Drive, Box, Dropbox, Asana, Jira, QuickBooks and Sage Intacct exist today. We build connectors for construction systems such as Procore and Autodesk Build per project.
Three things a monthly report leaves out.
Each flag comes from the record, with the thread or file behind it.
Activity that breaks pattern
GlassLedger tracks the usual volume for each topic, trade and party. Twenty emails on one topic in a day is a signal. A subcontractor who goes quiet for a week is one too.
You get the flag and the threads behind it.
Issues raised and never closed
Someone raises a problem in an email. Nobody opens a task, names an owner or sets a date.
GlassLedger keeps a running list of each issue it finds. It flags the ones with no next step after the number of days you choose.
| Issue | Raised | Next step | Status |
|---|---|---|---|
| Groundwater at the east footing | 14 days ago | None in any system | Stalled |
| Fire alarm panel submittal | 9 days ago | None in any system | Aging |
| Elevator delivery date | 21 days ago | Supplier call Thursday | Moving |
| Added blocking, Levels 3 and 4 | 5 days ago | Pricing due Friday | Moving |
Reports and invoices that don’t match the work
A pay application says mechanical rough-in is 60 percent complete. GlassLedger checks that line against daily logs, deliveries, inspections and email.
You see which lines the record supports before you fund.
| Line | Billed | What the record shows | Result |
|---|---|---|---|
| Concrete, Level 4 deck | 100% | Pour logged on the 12th. Inspection passed on the 14th. | Supported |
| Framing, Levels 3 and 4 | 80% | Rework thread open since the 20th. | Check |
| Mechanical rough-in | 60% | No logs, deliveries or RFIs since the 18th. | No support |
| Stored materials, switchgear | $186,400 | No delivery ticket in the files. | No support |
| Glazing deposit | 30% | Supplier confirmation and deposit invoice on file. | Supported |
No gaps when the project software goes stale
People get busy and stop logging. GlassLedger reads email, files, chat and accounting alongside the project software. When the schedule sits untouched for three weeks, GlassLedger flags it and keeps tracking the work from the other sources.
Tone that turns
Messages between the contractor and the engineer shift from routine to adversarial.
Dates that pass
A promised delivery date goes by with no update in any system.
Numbers that move
A budget line or contingency balance changes between two versions of a file.
People who drop out
A superintendent or project manager stops appearing in the threads.
Built for whoever carries the risk.
Choose your seat at the table.
You fund each draw against a report the borrower’s team wrote. Your inspector walks the site once a month. Between visits you rely on what you’re told.
- Check each draw against the daily record before you fund it.
- Hear about a schedule slip, a stalled trade or a contractor dispute the week it starts.
- See each loan in your book on one board, sorted by what changed.
- Write read-only access into the loan documents and start monitoring at closing.
You run several projects with dozens of parties on each. A problem reaches you after it has a price and a delay attached.
- Catch an issue the day the thread starts.
- Know what is open with each contractor, consultant and sub.
- Track what your team promised, to whom, and by when.
- Give your lender and partners a live record alongside the monthly report.
You receive a quarterly update and the occasional capital call. From those, a healthy project and a well-written update look the same.
- See the same board the sponsor sees, under the access you agree.
- Compare each sponsor report against the project record.
- Follow budget and schedule drift across each deal you hold.
- Get an alert when a project needs a conversation.
You are the person who reads the threads. A live project produces more threads than you have hours.
- Start each week from a brief of what moved and what stalled.
- Keep one list of open items, each tied to its thread.
- Catch the RFI that is turning into a change order.
- Walk into the OAC meeting with the questions already written.
The same ledger, different criteria.
Construction is where GlassLedger starts. Wherever one party carries the risk of work other people do, the work leaves a trail.
Private equity
An operating partner watching management teams and key vendors.
CriteriaCovenant headroom, key-person and key-customer signals, disputes.
Insurance and surety
An underwriter or claims team watching the insured or bonded contractor.
CriteriaIncidents, safety, subcontractor defaults, disputes in email.
Outsourced delivery
A vendor manager watching a provider’s delivery teams and tickets.
CriteriaFailures raised by email and never ticketed, scope creep, turnover.
Your setting
Fund administration, franchising, M&A integration, public infrastructure, supply chain.
CriteriaYou bring the setting. We write the criteria with you.
A board, an alert, a brief and an answer.
Four views of one record.
The board
Green, yellow or red for each area of each project. The history shows what moved and when.
Alerts
A message by email, Slack or Teams when a criterion trips. You set the thresholds.
Pay application 7 bills mechanical rough-in at 60 percent. The record shows no mechanical activity since the 18th.
The weekly brief
One page on what moved, what stalled and what to ask about. Your weekly review starts from it.
- Moved
- Draws to red. Schedule to yellow.
- Still open
- 14 issues. 3 have no next step.
- Ask Thursday
- Where is the switchgear? Who owns the groundwater issue?
Ask it anything
Plain-English questions, answered from the record with the sources attached.
The record
Each flag keeps its evidence, its confidence score and what your team did about it. You hold that history for the life of the project.
| When | Flag | Evidence | Confidence | What happened next |
|---|---|---|---|---|
| Tue 09:14 | Invoice line the record does not support | Pay application 7, daily logs, delivery tickets | 0.91 | Lender held the line item pending a site check. |
| Mon 16:40 | Topic spike: Level 2 transfer slab | 31 emails, 2 RFIs | 0.87 | Owner’s rep called the structural engineer. |
| Fri 11:02 | Electrical sub quiet for 7 days | Daily logs, email | 0.94 | Contractor confirmed the crew returns Monday. |
Built on NimbleBrain.
GlassLedger runs on the NimbleBrain platform, an open-source runtime for AI agents. Each part of GlassLedger is a part of the platform you can inspect.
NimbleBrain is the open engine for AI at work: a model-agnostic runtime that runs agents on your systems, inside your boundary, and the senior team that builds, ships, and runs them with you.
Connectors · MCP serversOne read-only connector per system, each with its own sign-in and scope. A system with an API can get a connector.
WorkspacesEach project or portfolio runs in its own workspace. One project’s data stays out of another’s.
SkillsPlain-English instructions with a version history. You can read them, change them and roll them back.
AutomationsScheduled and event-driven runs read what is new. Each run has a budget and leaves a record.
JudgeA separate pass scores each flag against the criterion it tripped and attaches a confidence.
MemoryDurable project memory holds each flag, fact and status change. The trend lines come from it.
Apps · SynapseThe board is an app in your workspace. The chat calls the same tools, so both show the same record.
Model gatewayOne gateway holds the provider keys, caps each run and logs each model call.
Runs in your boundary
A private tenant we host, or your own cloud. Your data is never pooled with another client’s.
No model lock-in
Any model, from any provider. Change it as better ones ship.
Open source runtime
The runtime under GlassLedger is open source. Your technical team can read the code.
Read-only. By agreement. With evidence.
A monitor earns trust from the parties it watches as well as the party it reports to. These limits are built in.
Read-only
GlassLedger reads. It cannot send an email, edit a schedule, approve a draw or change a file.
Access by agreement
Each party’s access is scoped and documented before anything connects. You can write it into the loan or development agreement.
Evidence with each flag
A flag links to the thread, log, file or invoice behind it. You check the source yourself.
Your people decide
GlassLedger flags and reports. Your team makes the call on each one.
Alongside your reports
The monthly report, the draw and the inspection stay in place. GlassLedger tells you if they match the work.
A private boundary
It runs in a private tenant or in your own cloud. Your data is never pooled with another client’s.
Questions people ask first
Does GlassLedger replace my construction monitor or inspector?
No. Your monitor walks the site and certifies the work. GlassLedger reads the record between visits and hands your monitor a list of what to look at.
What if the project team barely uses the project software?
GlassLedger reads email, files, chat and accounting too. It reports from those sources and flags the stale system.
Does the project team know it is connected?
Yes. Each party agrees to its access, and the scope is documented before anything connects.
How long does a first project take?
The starting engagement covers one project over six weeks. It ends with a review of what GlassLedger caught and what the reports missed.
Which AI model does it use?
You choose. NimbleBrain works with any major provider, and you can change the model later.
Does it work outside construction?
Yes. The criteria change and the monitor stays the same. The same approach fits private equity, insurance and outsourced delivery.
Start with one project.
Bring a project you have real exposure to. Fixed scope, fixed price. The first conversation is thirty minutes on that project and what you can see of it today.
- Each party connected, read-only, with access agreed and documented.
- The criteria for this project, in plain English and running.
- A live board and a weekly brief for whoever carries the risk.
- A week-six review of what it caught and what the reports missed.