Bid it. Build it. Bill it. In one place.

Owner: You run the company

You ask: Ask Gordon how the quarter looks. What happens: He pulls project P&L, cash, and what you owe and are owed from the ledger, on your own model key. Left behind: An answer you can trace to journal entries, and the cost of asking metered by feature.

You ask: Tell me when card charges pile up unreconciled on a job. What happens: A watch checks the records on a schedule and speaks only when the condition holds; Beatrix offers to process the pile. Left behind: A situation with the evidence attached, snoozed or resolved by you, never repeated in silence.

You ask: Add a new office and let them use the same setup. What happens: Morpheus walks the new workspace through legal entities, roles, deliverable standards and a starter kit. Left behind: A second workspace on the same account, sharing nothing it should not.

Estimator: You price the work

You ask: Drop the spec set in the project folder and ask Tony for a bid. What happens: He reads the spec, builds deliverables from your class standards, and prices resources against your catalog and closed estimates. Left behind: A draft worksheet on the project with a cost basis on every line, and the items he could not price flagged for you.

You ask: Turn the worksheet into a proposal and send it. What happens: The proposal is rendered from the worksheet with your document settings and sent to the client contact. Left behind: A proposal marked as submitted, its grand total on the pipeline, and the project ready to open on approval.

You ask: Get three quotes for the drywall scope. What happens: The Closer shortlists vendors from your catalog and history, sends the scope, and records what comes back. Left behind: Quotes side by side on the trade scope, one awarded, and the award carried into the estimate.

Project manager: You keep the job moving

You ask: Ask Trinity what is overdue on submittals. What happens: She reads the register against the spec sections, lists what is late and who owes it, and drafts the follow-ups. Left behind: A register where every item has a status and a date, and a transmittal package ready to send.

You ask: Ask Ripley why the schedule slipped. What happens: She walks the task dependencies and progress, compares budget to actual, and names the blocked task. Left behind: Updated tasks with the real dates, and the Gantt recomputed with your holiday calendar.

You ask: Bill this month's progress. What happens: The pay app suggests billing from task progress; you accept or adjust each line. Left behind: A pay application with a schedule of values, shared with the client by link, its status tracked to paid.

Bookkeeper: You close the month

You ask: Ask Beatrix to clear last month's card statement. What happens: She matches charges to receipts and vendor invoices one to one, and previews every write before it happens. Left behind: Journal entries posted, and the charges she could not match listed with a reason each.

You ask: Pay the vendors that are due. What happens: Payment requests are built from approved invoices, checked against compliance holds, and approved in one pass. Left behind: Payments recorded against the invoices, the journal balanced, nothing paid twice.

You ask: Run payroll for the period. What happens: Harper checks work sessions, allocates hours to jobs, applies overtime and prevailing wage, and generates the run. Left behind: Timesheets approved, payroll generated and exported, and the payroll journal posted.

Field super: You are on site

You ask: Crew checks in from the phone. What happens: Time lands on the job's tasks with location from GPS, even with no signal on site. Left behind: Work sessions the office sees as they happen, ready for allocation and payroll.

You ask: Snap the delivery and the packing slip. What happens: Photos go to the project folder; the receiving slip is read and matched to the purchase order. Left behind: A PO marked delivered, a shipment closed, the vendor invoice ready to match.

You ask: Text Kevin what happened today. What happens: He turns it into the daily progress report and updates the tasks you mention. Left behind: A daily report on the project, task progress moved, the PM notified.

CC Reconciliation Processor

# CC Reconciliation Processor > Loaded by Beatrix before she touches a card charge. ## Scope Project-scoped work starts with `ccr_process_project`. Global audits use `ccr_list_reconciliations` with `reconciliationStatus: "all"` — the default silently narrows to charges not yet recorded in accounting. ## Rules that are not negotiable 1. Preview before every mutation. Never write without explicit approval. 2. One charge links to one VPR, and the amounts must be equal. 3. Two or more charges settling one VPR go through `ccr_propose_vpr_allocations` → `ccr_approve_vpr_allocations`. 4. A PM flag with no receipt coming: `ccr_link_project` `action=related_no_receipt` with a `noReceiptReason`. ## Money at the boundary Tools speak dollars. Records store integer cents. Never pass cents. ## Known gotchas - Pick the card from the PROJECT's legal entity, never the last batch. - `isVerified` on a key is history, not health — check `lastFailedAt`.

Estimating Methodology

# Estimating Methodology > Companion to the org standard "Estimating Pipeline — Start to Finish". ## Phases 1. Read the spec and plan set (`spec_read_document`, `takeoff_*`). 2. Build deliverables from templates (`template_wizard`, `estimate_items`). 3. Price resources against the catalog and cost basis (`global_items_search`, `estimate_cost_basis`). 4. Schedule with the Gantt engine (`estimate_gantt`) — holiday calendar, no fabricated dates, durations reconciled. 5. Hand off to the proposal (`proposal_manage`). ## Inputs from the workspace - `Project.legalEntityId` → which company is bidding - `DeliverableClassStandard` → tenant-level standards, not the global catalog - closed estimates → cost basis for the next one ## Gotchas - `ts_browse` detail returns folders and matching vendors; read before writing. - `meta.precalculatedPricing` is stored in cents; everything at the tool boundary is dollars.

Submittal Register

# Submittal Register > Spec in, register out, packages compiled, subs chased. ## Lifecycle 1. Extract sections from the spec (`submittal_section_bulk`). 2. Build the register (`submittal_register`), one item per required product, shop drawing or cut sheet. 3. Review against the spec (`submittal_review`): approve clean, flag variance, queue the rest for a human. 4. Compile packages and transmittals (`submittal_bulk`, `document_package`). 5. Track due dates; surface overdue to the PM. ## Counting Count items through the `submittal` tool, never by `db_find` on `registerId` — the register aggregates across sections. ## Sharing `submittal_share` issues a scoped link for the sub or the architect.