Stonebridge × Singulari
DRAW-01

Construction draw

Adam Kirby · Phil · Brandy

The monthly package for the bank. Today it's eight manual steps against a day-10 deadline, with reconciliation done by eye and tracking done in email threads.

Today8 manual steps
01
Phil / Brandy

Copy prior month workbook

Find the file on SharePoint, copy it, rename it for the current month.

02
Phil / Brandy

Move Current to Prior by cost code

Each item allocated by cost code category. Copy and paste doesn't work. Slow and easy to get wrong — a Copilot trial never became standard practice.

03
Phil / Brandy · MRI

Export job cost draw detail

Run the report by job code, export to Excel, paste into the Current tab.

04
Phil / Brandy

Reconcile totals manually

Check that totals match. Items entered outside MRI regularly cause variances that have to be traced by hand.

05
Phil / Brandy · Nexus

Export bulk invoice PDF

Export PDFs ordered by cost code. The order has to match the workbook.

06
Phil / Brandy

Assemble the bank package

Print Excel tabs to PDF, combine manually with the invoice PDFs.

07
Phil / Brandy

Complete lien waivers and disbursement requests

Open the Word documents, update draw values and draw number. The requirement changes by lender.

08
Adam

Review the full package and submit

Adam reviews everything from scratch, signs, submits by day 10. Tracking lives in email and a basic Excel file with no consolidated view.

With Claude Cowork3 human touchpoints
01
Scheduled · Day 3

Claude creates the file and posts a message

Copies the prior draw workbook, creates the current-month version on SharePoint, and asks for the two exports by day 6.

02
Phil / Brandy · Days 4–6

Drop the MRI and Nexus exports in SharePoint

The only touchpoint with internal systems. Two exports, about five minutes.

03
Scheduled · Day 6

Claude detects the files and starts

If both are there, the sequence runs. If not, the reminder goes out again.

04
Claude

Migrate by cost code and reconcile

Moves Current to Prior with the right cost code categorisation, populates the Current tab from the MRI export, compares totals, and produces a variance list — only what needs a person.

05
Claude

Assemble the package and fill the Word documents

Tabs to PDF, combined with invoices in the right order. Lien waivers and disbursement requests pre-filled with draw values, per lender.

06
Scheduled · Day 7

Claude posts the summary for Adam

Package ready, variance list, documents waiting for signature.

07
Adam · Days 7–9

Review exceptions and sign

Adam sees only what Claude flagged. Twenty to thirty minutes instead of hours.

08
Adam · Day 10

Submit and report back

Adam submits the package. When the bank responds, he tells Claude and the tracking view updates.

Stays with the team
  • MRI export
  • Nexus export
  • Variance review
  • Signatures
  • Submission to the bank
  • Telling Claude when funding lands
Claude takes over
  • Creating the monthly workbook on SharePoint
  • Migrating data by cost code
  • Reconciling against the MRI report
  • Assembling the full PDF package
  • Pre-filling the Word documents
  • Running the schedule and the reminders
  • Keeping the tracking view current

Open questions · Draw-01

4 open · 4 total
How should Claude tell you a package is ready — a message in Cowork only, or email and Teams as well?
What should the draw tracking view look like, and who needs to see it besides Adam?
Does the lien waiver wording change by lender, and do we have a current copy of each version?
Are there draws where the cost code structure differs from the standard workbook?
PPD-02

Prepaid accounting

Adam Kirby · Phil · Brandy

The same workbook, rolled forward tab by tab, every month. The work is identical each time — which is exactly what makes it worth handing over.

Today5 manual steps
01
Phil / Brandy

Copy prior month workbook

Locate and copy the file, every month.

02
Phil / Brandy

Roll each tab forward

For every prepaid: reduce months remaining, highlight the next line, update the amortised balance. Repeated tab by tab.

03
Phil / Brandy · MRI

Export the trial balance

Export the monthly trial balance and paste it into the main tab by hand.

04
Phil / Brandy

Reconcile each account against its support

Compare every account balance to the support tabs. The variance has to be zero — anything else is investigated manually.

05
Adam

Review the full workbook

Adam reads every tab to validate the financial statements.

With Claude Cowork2 human touchpoints
01
Scheduled · Start of month

Claude creates the workbook and posts a message

Copies the prior month file and asks for the trial balance once the numbers close.

02
Phil / Brandy · MRI

Drop the trial balance in SharePoint

The only step that needs MRI access.

03
Claude

Roll every tab forward at once

Reads each prepaid tab, reduces months remaining, highlights the next line, recalculates amortised balances — all tabs, in one pass.

04
Claude

Import the trial balance and reconcile

Positions the trial balance in the main tab and compares each account against its support. Delivers what tied out and what didn't.

05
Adam

Review exceptions only

The workbook arrives reconciled with variances highlighted. Focused review instead of re-reading every tab.

Stays with the team
  • Trial balance export from MRI
  • Investigating accounts that don't tie out
  • Final validation by Adam
Claude takes over
  • Creating the monthly workbook on SharePoint
  • Rolling every prepaid tab forward at once
  • Importing and positioning the trial balance
  • Reconciling and highlighting variances
  • Posting the status message for Adam

Open questions · Ppd-02

3 open · 3 total
Which month should we run the first supervised pilot on?
Who signs off that a reconciled workbook is final — Adam alone, or Brian as well?
How should Claude handle a new prepaid that appears mid-year with no prior tab?
TRK-03

Team activity tracker

Brian Morrison

Brian has no visibility into where the team's work stands across projects. Processes and their statuses live in people's heads, so getting an update means asking someone directly.

Where it stands today

  • No single source of truth. The stages of each project and who is working on what are not written down anywhere Brian can see.
  • Status lives in conversations. Brian has to reach out to individuals to understand where something is.
  • No project-level view. It is hard to compare progress across projects or spot which ones are stuck.
  • Nothing carries forward. When a similar project starts, the team rebuilds the same mental model from scratch.

What we propose

A visual board for every project

We will build a lightweight tracking environment inside Microsoft 365 — a board or list per project where the team marks where each task stands. Brian gets the view he needs without adding another tool or login.

  • One board per project, with columns that match that project's actual stages. The structure is set together with the team, not imposed.
  • The team updates its own cards. When a task moves forward, the person doing the work drags or edits the card. No extra layer in between.
  • Brian sees status at a glance. Open, in progress, blocked, done — across every project he cares about, in one place.
  • History builds itself. Every update is timestamped, so it becomes easier to see how long stages actually take and where things get stuck.
TodayAsk and rebuild
01
Brian

Needs a status update

Brian realises he doesn't know where a project stands.

02
Brian · Team member

Ask the person directly

He messages or calls the owner of that piece of work.

03
Team member

Reconstruct the picture

The team member recalls the current state, sometimes checking other people first.

04
Brian

Mental note, no record

Brian has the answer for now, but nothing is stored for next time.

With a project boardLook and see
01
Brian

Opens the board

Sees every project and its current stage in one view.

02
Team

Updates their own cards

As work moves, the owner moves the card or updates the status.

03
Brian

Checks the view

Filters by project, owner, or status. No need to interrupt anyone.

04
Brian · Team

Uses the history

Past projects show how long stages took, making future planning easier.

What the team does
  • Defines the stages for each project with Brian
  • Creates and owns cards for their own work
  • Moves cards and updates status as things progress
  • Flags blockers so Brian can see what needs attention
What Brian gets
  • A single place to see every project's status
  • Visibility into what's open, in progress, blocked, or done
  • A record of how each project actually ran
  • Fewer interruptions for the team and faster answers for him

Open questions · Trk-03

6 open · 6 total
Does the team already use Microsoft 365 / SharePoint / Teams day to day? If yes, we'd make Microsoft Lists or Planner the primary recommendation.
What kinds of projects does Brian want to track first — developments, acquisitions, reporting cycles, or something else?
Who should be able to create a new project board and define its stages?
Who updates the cards — the person doing the work, a project coordinator, or both?
How often does Brian want to look at this view — daily, weekly, or only when he has a question?
Where should Brian access the board — Teams tab, SharePoint page, or direct link?
FIN-04

Portfolio financial dashboard

Brian Morrison

To see where a project stands financially, the only route today is MRI — open it, pull the statement for that property, then do it again for the next one. There's no view of the portfolio as a whole.

Where it stands today

  • One property at a time, one statement at a time.
  • Any comparison across properties has to be assembled by hand, and it's stale the moment it's finished.
  • Because it's slow to produce, it only gets produced when something prompts it.

What we propose

A dashboard that reads one workbook Claude keeps current

We don't integrate with MRI. The export is the interface. Claude consolidates the exports into a single Excel workbook — one row per property, standard columns — and the dashboard reads that workbook.

  • Portfolio on the first screen, drill-down to a single property from there.
  • Built in Lovable — a web app that opens in a browser. Nothing to install, works on a phone.
  • Movement against the prior period is flagged, so the dashboard points at what changed rather than just showing numbers.
  • If MRI changes, only the export step changes. The dashboard doesn't depend on it.
Team

MRI export

The statements you already pull, saved to a folder instead of read on screen.

SharePoint

Drop folder

One location, already governed by your existing permissions.

Claude

Consolidate

Reads every export, normalises it, writes one row per property.

Claude

Master workbook

A single Excel file, refreshed on a schedule. Auditable, and openable on its own.

Brian

Dashboard

Portfolio view, drill-down per property, current whenever it's opened.

Stays with the team
  • Producing the MRI export
  • Deciding what the numbers mean
  • Setting the thresholds worth flagging
Claude takes over
  • Consolidating every property into one workbook
  • Keeping it refreshed on a schedule
  • Comparing against the prior period
  • Flagging movement worth a second look

Open questions · Fin-04

6 open · 6 total
Which figures does Brian want on the first screen, before any drill-down?
How current does the dashboard need to be — daily, weekly, or at close?
Can MRI export all properties in one file, or is it one property at a time?
Which properties are in scope for the first version?
Who gets access, and does it need to be restricted by property?
Is there a budget or pro forma figure to compare actuals against, and where does it live?