Pohutch
A spreadsheet-federated purchase-order workbench for construction teams that mirrors approved rows into a relational project ledger, ingests authorized mobile receipt messages, proposes document-to-PO matches, and reconciles field and office edits without treating a sync, OCR result, attachment, approval, invoice, payment, or job-cost outcome as the same state.
Construction teams often rely on one shared PO sheet because it matches field habits, even while home-office reporting, receipts, commitments, and project rollups demand more structure. Pohutch preserves the visible sheet while assigning stable identities, versions, ownership, and conflict rules to projects, vendors, POs, lines, changes, receipts, invoices, and approvals. A changed cell is not necessarily authorized, sync success is not semantic correctness, a receipt photo is not an invoice or proof of payment, OCR is only a candidate, and routing does not approve cost. Sheet observation, normalized record, conflict, reviewer resolution, PO authorization, vendor acknowledgment, receipt, invoice, match, accounting export, payment, job-cost report, dispute, reversal, and correction remain distinct.
A construction owner, controller, project executive, office accountant, or operations lead whose field project managers already manage purchase orders in shared spreadsheets.
The source identifies current large-contractor spreadsheet use, though no regulatory or fixed deadline drives adoption.
Construction owners, controllers, project leaders, and office finance teams are concrete.
One cross-reference and three inbound connections support limited convergence.
One cross-reference, three inbound connections, four verified interfaces in the source stage, a concrete construction buyer, and no supplied competitor preserving a shared sheet while providing governed PO structure support the direction.
There are no direct connections, sync semantics and field ownership are hard, messaging and document data are sensitive, construction accounting varies, incumbents can extend, spreadsheet dependence may cap the segment, and pricing and implementation economics are unvalidated.
Discussion
No comments yet — be the first to weigh in.