Spray call 1 — reporting, inventory accuracy, and data recovery

Source

Field	Value
Source file	insights/transcribes/spray-call-1.md
Recording	GMT20241212-210854_Recording (2).m4a
Call date	2024-12-12
Contributor	null — not recorded in the transcript or authoring session
Captured	2026-07-27
Statement type	call_learning for what the buyer said; founder_instinct for the seller's product claims

Speakers are not labeled in the transcript. Attribution below is inferred from context. The buyer represents a single-site, 13-person manufacturer. Gabriel identifies himself as the seller's founder and software architect.

The contributor confirmed during authoring that this was the first call with a prospect that later converted to a paying customer. Conversion is provenance, not proof that every mismatch or seller claim in the call was true.

What this proposes

Three new canonical problems:

1. Management questions require spreadsheet reconstruction outside the operating system.
2. Recorded inventory does not reconcile to physical stock, and the source of the variance is not traceable.
3. Replacement planning lacks a verified export of linked operating records.

Observations, kept traceable

1. Every reporting modality requires export and spreadsheet work. On the call, the buyer said, "I cannot even call up a report that will tell me what my top five sellers are. I have to export everything." For purchasing and vendor reporting, the buyer likewise said, "I gotta export all of that and put it into Excel and try again." During authoring on 2026-07-27, the contributor clarified that this was not limited to those examples: all reporting modalities required Excel.
2. Recorded inventory differs from physical counts. The buyer said the current system "doesn't do a very good job of maintaining our inventory and our inventory counts", that the team could not understand where the glitches occurred, and that the result was "just not reliable." During authoring on 2026-07-27, the contributor confirmed that unreliable counts meant differences between the recorded quantities and physical counts.
3. Data recovery had not been verified before replacement. The buyer said, "I have no idea if I own this data or when we stop using it am I going to lose everything." Manufacturing, purchasing, sales, inventory, and accounting were tied together in Global Shop Solutions. CSV export was discussed as a possible workaround, while both parties noted that a flat export might not preserve linked document references.
4. Post-conversion recovery was partial. During authoring on 2026-07-27, the contributor confirmed that only part of the incumbent data was recovered after the customer converted. The missing record types and relationships were not specified.
5. System usability was described negatively but not isolated as a separate mismatch. The buyer asked for a robust, user-friendly system that was not "big and bulky" and called the incumbent a "Frankenstein monster." The call supplies no separate user task, workaround, or adoption failure beyond the reporting and inventory observations promoted here.
6. Project management was described as unavailable without a stated workaround. The buyer said, "project management forget about it, it's not gonna happen." The process, alternate record, and operational consequence were not described.
7. Custom components and alternate suppliers were account context, not a mismatch. Many plastic parts and springs were custom-tooled, and the ISO certified company maintained relationships with more than one vendor. The buyer called this "nothing special, nothing hard."
8. The account was actively evaluating a replacement. The search had begun more than a year earlier, the desired deadline had passed, another incumbent renewal was due, and the buyer wanted a parallel transition. These are deal timing and account context rather than a reusable operational mismatch.

Buyer requirements and seller product claims

The buyer asked about work-in-process costing, outside processing, quality control, permissions, financial statements, ordinary hardware, mobile access, WooCommerce, customer portals, implementation, migration, price, and dedicated support. These are capability requirements and route to create-solutions, not to problem records.

The seller described configurable dashboards, AI analysis, forecasting, inventory movements, manufacturing and accounting workflows, integrations, data pipelines, mobile access, rapid implementation, and ongoing support. These are founder_instinct product claims until product validation records exist. They were not promoted as problems.

The buyer's concern about AI accuracy, employee input, and whether AI could be disabled is an objection and potential Q&A input for W8; it is not a current operational mismatch established by this call.

Duplicate decisions

Observation	Closest existing	Decision
Reporting requires Excel reconstruction	P_00002	Create a materially distinct problem; P_00002 concerns multi-site, cross-system, unit-level margin reconciliation
Inventory differs from physical counts	none	Create a new problem
Linked-record recovery is unverified	P_00001	Create a materially distinct problem; P_00001 concerns operating rules held in internally built code

The user approved all three decisions and the complete YAML drafts on 2026-07-27.

Outcome

Candidate	Outcome	Record
Reporting requires Excel reconstruction	New canonical problem	P_00010
Inventory differs from physical counts	New canonical problem	P_00011
Linked-record recovery is unverified and later partial	New canonical problem	P_00012
General usability complaint	Needs input; retained in inbox	Not promoted
Project-management capability gap	Needs input; retained in inbox	Not promoted
AI trust and control concern	Route to W8	Not promoted as a problem
Buyer capability requirements	Route to create-solutions	Not promoted as problems
Seller product claims	Route to create-solutions	Not promoted as problems
Custom supplier arrangements	Account context	Not promoted
One site, 13 employees, no on-site IT, shop-floor tablets	Route to W4 as possible signals	Not promoted as problems
Replacement timing and renewal	Account context	Not promoted

This item remains the audit trail. No evidence record was created because the owning location for EV_ records is unsettled. The resulting problems therefore carry evidence_ids: [] and remain hypotheses rather than assertable market facts.