Must a vendor author their bid in our tool, or can they submit from anywhere? #4

New Issue

christian · 2026-08-02T03:05:51Z

christian commented

2026-08-02 03:05:51 +00:00

Question

The bid intake contract. Determines whether structure is mandated, extracted, or absent.

Parent: #1

## Question The bid intake contract. Determines whether structure is mandated, extracted, or absent. --- Parent: #1

christian added the

wayfinder:grilling

wayfinder:ticket

labels 2026-08-02 03:05:51 +00:00

christian commented

2026-08-02 03:05:58 +00:00

Resolution

Submit from anywhere; structure on ingest. Accept PDF/DOCX from any vendor and extract the response into the common schema so it is rankable. Native authoring is offered as the better path, never required.

Why. This is the side being charged. Charging them and forcing a tool migration is two asks where only one is affordable. Vendors who author natively emit cleaner structure and get better outcomes, which pulls adoption without mandating it.

Symmetry this creates. Both sides now submit documents and both get extracted, which settles the RFP-shape question by implication: extraction on both ends, human confirmation on both ends. The confirmation step is load-bearing, not polish — see the extraction-confirmation ticket.

What this costs. Extraction quality varies, so the moat is a gradient rather than a wall.

## Resolution **Submit from anywhere; structure on ingest.** Accept PDF/DOCX from any vendor and extract the response into the common schema so it is rankable. Native authoring is offered as the better path, never required. **Why.** This is the side being charged. Charging them *and* forcing a tool migration is two asks where only one is affordable. Vendors who author natively emit cleaner structure and get better outcomes, which pulls adoption without mandating it. **Symmetry this creates.** Both sides now submit documents and both get extracted, which settles the RFP-shape question by implication: extraction on both ends, human confirmation on both ends. The confirmation step is load-bearing, not polish — see the extraction-confirmation ticket. **What this costs.** Extraction quality varies, so the moat is a gradient rather than a wall.

christian closed this issue

2026-08-02 03:05:58 +00:00

christian referenced this issue

2026-08-02 03:06:00 +00:00

Retail RFP transmission system — v1 build spec #1

christian referenced this issue

2026-08-03 16:47:06 +00:00

Design the app framework — retailer and vendor surfaces #23

Sign in to join this conversation.