Alternatives · Operator field guide
Keep the spreadsheet until coordination costs more than flexibility
Spreadsheets are excellent calculation surfaces. The problem begins when one file is also expected to handle permissions, approvals, versions, workflow state, and organizational memory.
Trace 01 · Signal → cause → consequence
Diagnose the operating failure before buying a tool
Visible signal
Files are named final-v7, producers copy old jobs, formulas are protected by folklore, and the team confirms the approved amount in email before rebuilding it elsewhere.
Underlying cause
A flexible personal tool has become multi-user infrastructure without transaction rules, stable identifiers, or controlled state changes.
Business consequence
The company pays in duplicate entry, senior review, preventable version mistakes, and lost learning even though the spreadsheet subscription appears free.
Control 02 · Operating principles
Three controls that survive the software
Do not migrate a bad template faster
Clean definitions, rate ownership, markup logic, and assumptions before importing. Software will enforce ambiguity as efficiently as it enforces good rules.
Preserve calculation transparency
Operators trust spreadsheets because they can inspect them. A replacement must expose line math, rate basis, assumptions, and totals rather than hide logic behind automation.
Keep an export escape hatch
The system can own workflow state while still exporting a legible spreadsheet or CSV for clients, accountants, archives, and operators who need offline analysis.
Runbook 03 · Smallest useful workflow
Run this on one real job
Do not begin with a company-wide migration. Prove the control on representative work, record the exceptions, and expand only when the operator can trust the new state.
Measure the spreadsheet tax
For ten recent jobs, count copy-forward setup, manual re-entry, version reconciliation, formula repair, approval lookup, and owner review. Convert that time at the actual operator cost.
- Include senior producer time
- Include errors caught before they became losses
- Separate document formatting from decision work
Define the canonical fields
Choose stable meanings for category, department, role, unit, quantity, days, unit rate, markup, line total, assumption, and source. Resolve inconsistent columns before migration.
- Every money field has one unit
- Percentage lines name their basis
- Text notes are not carrying hidden numbers
Rebuild, then run live
Reconstruct one closed job to prove parity, then run one live estimate. The closed job tests math; the live job tests collaboration, approvals, and behavior under deadline.
- Totals reconcile to the cent
- Known historical mistakes are not imported as rules
- The live job has a rollback plan
Retire the shadow copy
Once the workflow is trusted, state which system owns rate cards, estimate versions, approval, and initial budget. Allow exports, but stop maintaining a parallel editable master.
- Operators know the source of truth
- Legacy files are read-only
- Exceptions have an explicit owner
Instrument 04 · Evidence
Measure whether the control is earning its place
- Hours per estimate spent copying, reconciling, or formatting
- Version mistakes and formula defects per quarter
- Percent of approvals linked to a specific estimate version
- Time required to answer why a historical rate or total changed
Boundary 05 · Product truth
Where Production Engine fits today
The current build is strongest from company rate card through estimate, option approval, and initial budget creation. The design-partner program exists to test the next control on live work without pretending the whole production stack is finished.
Present in the current repo
- Stores normalized estimate lines and recomputes totals in integer cents
- Keeps tenant rate cards and estimate snapshots outside individual files
- Links a client decision to a scenario and initial budget record
Design-partner scope
- Map the existing spreadsheet into canonical fields
- Reconcile one prior job and one live bid
- Document exports and controls needed before the spreadsheet master can retire
Honest boundary: Production Engine should not replace specialist spreadsheet analysis or every client format. The design-partner test is whether it can own the decision state while preserving transparent exports.
Paid design-partner program
Put one live workflow under control in 90 days.
Implementation, rate-card and workflow mapping, access for five operators, and direct product-team collaboration.
$2,500 implementation + $499/month for five operators · 90-day commitment
FAQ 06 · Buying questions
Questions to resolve before implementation
When is a spreadsheet still the right answer?
When volume is low, one skilled person owns the file, approvals are simple, and copying history creates little risk. Do not add software merely to look more sophisticated.
Should all historical estimates be imported?
Usually no. Import current rate truth and a small set of representative jobs. Archive the rest and migrate additional history only when a real reporting or renewal need appears.
What is the safest cutover?
Run a closed-job parity test, then one live job with a named rollback point. Freeze the old master only after totals, approval, and handoff have been verified.
Index 07 · Internal route
Continue the operating system
An estimate version is a client promise, not a filename
A version-control workflow for production estimates that keeps revisions, options, assumptions, and approvals tied together.
Read the field guideCompare production management alternatives by the job they control
A neutral framework for comparing production management suites, specialist tools, spreadsheets, and a custom operating stack.
Read the field guideA production rate card is an operating control, not a spreadsheet tab
How commercial production companies can govern crew, equipment, post, and markup rates without slowing down estimates.
Read the field guidePaid design-partner program
If this failure costs real producer time or margin, test it on a live job.
Implementation, rate-card and workflow mapping, access for five operators, and direct product-team collaboration.
$2,500 implementation + $499/month for five operators · 90-day commitment