Resolver status
unsupported
No matching entry exists in the governed resolver catalog.
For controllers, CFOs, and managing partners
Map why the cash number stops being trustworthy.
A read-only assessment documents how close, collections, and cash reporting actually happen using interviews and controlled exports. No live accounting-system access is required during assessment.
Evidence before claims
What this page is—and is not—promising
Assessment goal: identify the smallest governed workflow that can improve cash visibility without becoming the ledger.
Data boundary
Regulated or consequential records; map read-only boundaries before building.
Economic buyer
CFO, Controller, or firm administrator
Why now
The conditions that make the workflow worth examining
These are discovery signals, not proof that Forklift has delivered the outcome for a customer.
Common triggers
- Reporting depends on one person's spreadsheet
- Close stretches later each quarter
- Receivables age without a clear owner
- Leaders dispute the same figures in different meetings
Observable symptoms
- The weekly cash figure is assembled by hand
- Recurring reconciliation exceptions have no root-cause owner
- Collections follow-up depends on memory
- Preparing the board pack consumes nights or weekends
First artifact
Close and Cash Operating Map
Target assessment timeline: two weeks, subject to scope
- The current close path with owners and observed durations
- Every point where financial data is rekeyed
- Recurring reconciliation and collections exceptions
- Decision rights for entries, payments, and write-offs
- A bounded read-only implementation option, or evidence not to proceed
Governed progression
Prove the control loop before increasing authority
Every engagement progresses through explicit gates. Natural language expresses intent; it never grants production authority.
1. Diagnose
Confirm the repeated problem, owner, systems, data, decision rights, baseline, and economics.
2. Observe
Use interviews, fixtures, or controlled exports before requesting a read-only connector.
3. Control exceptions
Give bounded exceptions owners, deadlines, approvals, and reconciliation evidence.
4. Prove
Measure the agreed result against the approved baseline and preserve provenance.
5. Automate selectively
Permit only cataloged, tested, reversible actions under the exact approved plan.
6. Operate or stop
Monitor cost, health, incidents, recovery, upgrades, and exit—or record why the hypothesis failed.
Proof metrics
Agree on the baseline before claiming improvement
A metric becomes evidence only when its definition, source, window, owner, and comparison baseline are approved.
Close-cycle days
Forecast variance
Overdue receivables and DSO
Reconciliation exceptions per cycle
Report-preparation hours
Hard boundary
What remains outside this engagement
These exclusions are commitments. Changing one requires a new classification, plan, review, and approval—not an expanded prompt.
- Replacing the accounting ledger
- Posting journal entries, payments, or write-offs
- Reading client-confidential files during assessment
- Declaring legal or regulatory compliance
Commercial entry
Assessment first
The assessment scope, deliverables, fee, and credit toward any later build are agreed in writing before work starts.
No unmeasured agent price is published.
The first written proposal identifies the work, evidence, operating obligation, and commercial terms before authorization.
Questions
What buyers usually need clarified first
Why does this start with an assessment?
Financial and client-confidential data require an explicit boundary before a connector or workflow can be proposed.
Do you connect to our accounting system immediately?
No. Assessment uses interviews and controlled exports. A later read-only connection requires its own reviewed plan.
What does the assessment cost?
The deliverables, fee, and any credit toward a later build are agreed in writing during scoping.
Adjacent outcomes
Scope the next problem without inventing a page
Unpublished outcomes route to Open Flow. They do not produce a broken page or an implied implementation claim.