PactWise Source — Sealed RFPs
Run the RFP nobody can dispute.
Source runs your RFP from package to award and makes the unfair move impossible: pricing stays sealed until the deadline, a defective package cannot publish, and every decision lands on a record you can hand to anyone. A first-time buyer runs a process a veteran would sign.
- Sealed pricing
- Deterministic gates
- Append-only audit
- Vendor isolation
- Northwind Freightsubmitted 09:14sealed$412,900
- Halden Carrierssubmitted 11:52sealed$398,450
- Meridian Logisticssubmitted 14:03sealed$441,200
- Atlas Cargosubmitted 16:41sealed$405,000
Revealed 17:00:00 · reveal job · 4 envelopes opened at once · logged
The Protest
Every RFP is fair
until someone asks.
We request the complete record of the procurement: who accessed pricing and when, every deadline change with its reason, and the scoring rationale for each evaluator.
Absent that record within ten business days, we will treat the award as indefensible and proceed accordingly.
— Counsel for the second-ranked bidder
Absent by design
What Source cannot do.
Guardrails you can switch off are not guardrails. These capabilities were never built, so no admin, no insider, and no hurried Friday can use them.
- 01
Give one vendor a different deadlineThere is no per-vendor deadline anywhere in the schema. Every extension reaches every vendor at the same moment.
- 02
Shorten a deadline after publishPost-publish, deadlines only move later. Shortening one would let an insider fire the reveal early.
- 03
Open a sealed bid earlyPricing is envelope-encrypted per submission and the key never sits in the database. Not the buyer, not an admin, not a database dump.
- 04
Message a vendor about the package in privateQuestions arrive privately; answers publish to everyone, anonymized. There is no side channel to favor anyone through.
- 05
Write a free-text regret letterRegret letters come from templates, so no one improvises a reason after the fact.
- 06
Let an algorithm score a bidAI never scores, ranks, or recommends an award. That is a structural rule, not a setting.
The Envelope Live today
Sealed in the dark. Opened in the light.
Four envelopes. The buyer can count them — and nothing else.
17:00:00 · reveal job · four envelopes opened at once · pricing.revealed logged.
The Gates Live today
A defective RFP cannot leave draft.
Publish and award are database checks, not checklists. If the package fails, the state transition is refused with the list of what is unmet — try it.
Publishing is a database check, not a checklist: contact details, Q&A cutoff spacing, minimum response window, invitations, criteria weights that sum to 100 and a pricing schedule are all enforced before an RFP can go out.
Prep Studio In progress
AI drafts. Code validates. A human approves.
Prep Studio interviews you, drafts the scope, requirements matrix, weighted criteria and pricing schedule, then reads its own draft the way a hostile bidder would. Nothing it writes reaches a vendor until code has checked it and you have signed it.
AI drafts
- Interviews you about the buy
- Drafts scope, requirements matrix, criteria, pricing schedule
- Reads its own draft as a hostile bidder would
Code validates
- Criteria weights sum to exactly 100
- Every scored criterion maps to a requirement
- Response window meets the minimum
A human approves
- One artifact at a time
- Approval binds to a content hash — edits reopen it
- Nothing reaches a vendor without both
AI scores a bid
Never. Not as a setting, not as a plug-in. "An algorithm scored you" is protest bait.
The Workspaces Live today
Vendors never see each other.
Every vendor works in a workspace of its own: the package, the addenda, its own submissions, and nothing else. Not the other bidders' names, not their questions, not how many of them there are.
- Package · v2
- Addenda · 2 acknowledged
- Own submissions · 1 sealed
- Other bidders · none visible
- Package · v2
- Addenda · 2 acknowledged
- Own submissions · 1 sealed
- Other bidders · none visible
- Package · v2
- Addenda · 2 acknowledged
- Own submissions · 1 sealed
- Other bidders · none visible
“Is on-site staging required for lane 4?”
Q7 · No — lane 4 is drop-trailer only.
Deny-by-default row security, forced on every table. A cross-workspace isolation test runs on every merge: every vendor-visible table × a foreign workspace = zero rows.
The Record Live today
Defend the award in front of anyone.
Every read, write, extension and score is an append-only event, hash-chained to the one before it. Nothing is edited after the fact, because nothing can be.
| seq | event | actor | prev_hash |
|---|---|---|---|
| 0412 | rfp.published | buyer_admin | 9f3a…c21e |
| 0413 | invitation.sent ×4 | system | b07d…4a91 |
| 0417 | deadline.extended +48h | buyer_admin · reason: addendum 2 | 61e8…0f3b |
| 0421 | submission.finalized | Halden Carriers · sha256 ✓ | d4c2…77aa |
| 0425 | pricing.revealed ×4 | reveal job · 17:00:00 | 2b9e…e5d0 |
| 0426 | file.read | evaluator M. Chen · 60 s link | f1a7…93c4 |
The protest file Live today
When someone asks, one export compiles the whole story. It is the “we can defend this award in front of anyone” artifact.
- Timeline
- Addenda + acknowledgments
- Published Q&A
- Submission metadata + late reasons
- Locked scores + variance notes
- Conflict-of-interest attestations
- Approvals
After the award
The RFP becomes the contract's memory.
Award hands the whole pre-award record to Pactwise Contracts: the package, the addenda, the winning submission, the published Q&A. From there Donna reads the agreement, every obligation gets an owner, and renewals stop surprising you.
Award → contract file
The awarded RFP is pushed into Pactwise Contracts as the contract file’s pre-award history, idempotently, with checksums verified.
Every contract. Every obligation. Charted.
Clause extraction, obligation and renewal tracking, vendor scoring, approvals.
See Contracts →DonnaPlain questions. Cited coordinates.
Ask what you actually agreed to; every answer cites the clause it came from.
Watch Donna work →The Fine Print
What is live, what is next.
We're an early-stage product and we don't hold third-party certifications yet — so we won't claim any. Here is exactly what is built, what is landing, and what is still on the roadmap.
| Capability | Status | What it means |
|---|---|---|
| Sealed pricing | Live today | Each pricing submission is envelope-encrypted with its own data key, wrapped by a key the database never holds. The buyer sees that a bid exists — never its contents — until the reveal. |
| Scheduled reveal | Live today | A scheduled job opens every envelope at once after the deadline plus grace, re-checking the effective deadline at run time so an extension can never trigger an early reveal. |
| Vendor isolation | Live today | Deny-by-default row security, forced on every table. A cross-workspace isolation test runs on every merge: every vendor-visible table × a foreign workspace = zero rows. |
| Invitation-only access | Live today | Single-use invitation links that only an explicit click consumes (corporate link scanners cannot burn them), plus step-up re-authentication before sensitive actions. |
| Immutable submissions | Live today | Uploads are stamped with the server clock and a server-computed checksum, scanned, then frozen. Late uploads are accepted only with a written reason and flagged as late. |
| Reads become evidence | Live today | No one — vendor or buyer — reads a file directly. Every read is logged and served through a signed link that expires in 60 seconds. |
| Append-only audit | Live today | One write path into the audit log, no updates, no deletes, each event hash-chained to the one before. |
| Vendor portal on its own host | Live today | Vendors work on a separate host with its own sessions; a vendor identity can never become a buyer user. |
| Extend-only deadlines | Live today | After publish a deadline can only move later, every change is historized with a reason, and every vendor is notified at once. Lateness is frozen at submission time. |
| Publish gate | Live today | Publishing is a database check, not a checklist: contact details, Q&A cutoff spacing, minimum response window, invitations, criteria weights that sum to 100 and a pricing schedule are all enforced before an RFP can go out. |
| Leveled Q&A and addenda | Live today | Vendors ask privately; answers publish to everyone, anonymized. Post-publish changes go out only as versioned addenda every vendor must acknowledge, and an addendum inside the notice window forces a deadline extension or a written override. |
| Two-person award | Live today | An award needs a locked evaluation, a written justification, every vendor question answered, every abnormal-bid flag acknowledged, and an approver who is not the author. |
| Blind, attested evaluation | Live today | Evaluators attest no conflict of interest before scoring, see only their own scores until lock, and outliers are flagged at lock time. |
| Protest file export | Live today | One export compiles the timeline, addenda and acknowledgments, published Q&A, submission metadata, locked scores, attestations and approvals into a single hashed document. |
| Buyer console | Live today | RFP authoring, invitations, documents and addenda, Q&A, roll-call, evaluation, award, completion and audit screens for the buying team. |
| Prep Studio | In progress | AI-assisted intake that drafts the scope, requirements matrix, weighted criteria and pricing schedule, reads its own draft as a hostile bidder would, and hands every artifact to you for approval. Built and verified against recorded model runs; live-model drafting switches on with the model key. |
| Award → contract handoff | Roadmap | The awarded RFP is pushed into Pactwise Contracts as the contract file’s pre-award history, idempotently, with checksums verified. |
Live today · In progress · Roadmap
The Ticket
One plan, both products.
Source and Contracts share a subscription — the same prices as Pactwise Contracts, 14-day free trial, 2 months free with annual billing. Vendors never need a seat.
Starter
One team, its first sealed RFPs, and a record you can stand behind.
- Up to 100 RFPs and contracts
- Up to 10 seats · 50 vendors
- Sealed pricing nobody can open early
- Publish gates enforced by the database
- Vendor portal with hard isolation
- Leveled Q&A and versioned addenda
- Email support · 14-day free trial
Professional
For procurement teams running evaluations they may have to defend.
- Up to 500 RFPs and contracts
- Up to 25 seats · unlimited vendors
- Everything in Starter
- Blind, attested evaluation with outlier flags
- Two-person award with the award gate
- Prep Studio AI drafting (human-approved)
- Competition-health and price-sanity monitors
- 5 integrations · priority support
Business
For organizations where every award is a matter of record.
- Unlimited RFPs, contracts, seats and vendors
- Everything in Professional
- Protest file export — one hashed document
- Completion and vendor offboarding on a schedule
- Award → contract handoff into Pactwise Contracts
- Custom workflows and advanced analytics
- Unlimited integrations · dedicated support
Enterprise
$2,000/year · annual only · scoped per organizationMulti-tenant management for groups running RFPs across subsidiaries, consolidated visibility across child tenants, unlimited teams and evaluators. Talk to us about a rollout.
The same plans on the Pactwise Contracts page — where they start free.
Publish your next RFP on Source.
Bring the package you are about to send. Leave with a process nobody can dispute.
RFP-2041 — awarded on the record.Sample