2026-05-19 - 2026-08-19
Overview
29 Issues closed from 1 user
Closed
#29 Define the v1 rate structure types
Closed
#37 Build the clickable POC prototype for the internal demo
Closed
#36 Define the v1 component system and visual identity
Closed
#30 Build the synthesized response corpus
Closed
#35 Assemble the v1 code layout
Closed
#16 Design the extraction confirmation step on both sides
Closed
#15 Design AI bid ranking, scoring, and its defensibility
Closed
#14 Specify the two-party data release rules
Closed
#23 Design the app framework — retailer and vendor surfaces
Closed
#32 Define the eligibility path for a vendor with no vault
Closed
#34 Specify the vendor pricing and tier structure
Closed
#31 Resolve what eligibility references, and whether local categories are mutable
Closed
#33 Skeptical review pass over all closed decisions
Closed
#10 Define the common schema for RFPs and responses
Closed
#25 Obtain real completed vendor responses, including a compliance matrix
Closed
#26 Define the category taxonomy
Closed
#20 Specify the entitlement and subscription model
Closed
#13 Design the vendor profile and cross-retailer document vault
Closed
#12 Design the visibility and qualification model
Closed
#22 Collect real retail RFPs and vendor responses
Closed
#11 Define the tenancy, identity, and authorization model
Closed
#8 Research: Ramp's online sentiment and the critical case
Closed
#9 Research: the RFP / sourcing / procurement ecosystem, both sides
Closed
#7 Research: Ramp's product, positioning, and business model
Closed
#6 What do bidders actually pay for?
Closed
#4 Must a vendor author their bid in our tool, or can they submit from anywhere?
Closed
#5 Day one, a retailer posts an RFP. Where does the bidder pool come from?
Closed
#2 Where does the transmission system get built?
Closed
#3 Is this the retailer's system of record, or a layer on their existing stack?
37 Issues created by 1 user
Opened
#1 Retail RFP transmission system — v1 build spec
Opened
#3 Is this the retailer's system of record, or a layer on their existing stack?
Opened
#4 Must a vendor author their bid in our tool, or can they submit from anywhere?
Opened
#5 Day one, a retailer posts an RFP. Where does the bidder pool come from?
Opened
#2 Where does the transmission system get built?
Opened
#6 What do bidders actually pay for?
Opened
#7 Research: Ramp's product, positioning, and business model
Opened
#9 Research: the RFP / sourcing / procurement ecosystem, both sides
Opened
#8 Research: Ramp's online sentiment and the critical case
Opened
#10 Define the common schema for RFPs and responses
Opened
#14 Specify the two-party data release rules
Opened
#13 Design the vendor profile and cross-retailer document vault
Opened
#11 Define the tenancy, identity, and authorization model
Opened
#12 Design the visibility and qualification model
Opened
#19 Draw the HelmDocs integration boundary
Opened
#21 Design the audit trail and evidentiary record
Opened
#18 Define the retailer integration and export paths
Opened
#20 Specify the entitlement and subscription model
Opened
#17 Scope the post-award kickoff and coordination tooling
Opened
#15 Design AI bid ranking, scoring, and its defensibility
Opened
#16 Design the extraction confirmation step on both sides
Opened
#22 Collect real retail RFPs and vendor responses
Opened
#23 Design the app framework — retailer and vendor surfaces
Opened
#24 Design roster-entry claiming and its verification
Opened
#25 Obtain real completed vendor responses, including a compliance matrix
Opened
#26 Define the category taxonomy
Opened
#27 Define the v1 document type catalogue
Opened
#28 Define the v1 category spine
Opened
#29 Define the v1 rate structure types
Opened
#30 Build the synthesized response corpus
Opened
#31 Resolve what eligibility references, and whether local categories are mutable
Opened
#32 Define the eligibility path for a vendor with no vault
Opened
#33 Skeptical review pass over all closed decisions
Opened
#34 Specify the vendor pricing and tier structure
Opened
#35 Assemble the v1 code layout
Opened
#36 Define the v1 component system and visual identity
Opened
#37 Build the clickable POC prototype for the internal demo