Operations · App Starter
Procurement Template
Purchase requests, approval chains, RFQ comparisons, and vendor scorecards — generated as a full-stack app your company owns.
Describe how spending gets approved at your company and Dual7 generates this procurement system around it: six connected entities, approval routing that matches your actual thresholds, and an RFQ workflow that puts quotes side by side. It ships as source code, so the process in the app is the process you run — and stays that way when the process changes.
- 6 core entities
- Configurable approval chains
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Procurement is a chain of records that have to reference each other cleanly: a request becomes an RFQ, quotes come back against it, an approval releases it, and a contract governs the price. Six tables carry that chain end to end.
| table | what it holds |
|---|---|
vendors | Every supplier you buy from — contacts, payment terms, categories served, and a performance history that feeds the scorecard. |
purchase_requests | What someone wants to buy: line items, estimated cost, cost center, justification, and current position in the approval chain. |
rfqs | Requests for quotation sent to selected vendors, with specs, quantities, deadline, and the requests they originated from. |
quotes | Vendor responses to an RFQ — unit prices, lead times, validity windows — structured so comparison is a table, not a stack of PDFs. |
approvals | Individual approve/reject decisions with approver, timestamp, and comment — the audit trail every finance review asks for. |
contracts | Negotiated agreements with vendors: pricing terms, start and end dates, renewal windows, and the spend recorded against them. |
02 · Screens
Signature modules
Approval chains
01Requests route by amount, category, and cost center — a $200 order clears one approver while capital spend climbs the chain. The routing rules are readable code in your project, so when the CFO changes the thresholds, you change a file, not a support ticket.
RFQ-to-quote comparison
02Send an RFQ to chosen vendors, and incoming quotes land in one comparison table: price, lead time, and terms aligned line by line. Award from the table and the decision, the losing quotes, and the reasoning stay on record.
Vendor scorecards
03On-time delivery, quote responsiveness, and pricing trend per vendor, accumulated from real transactions rather than annual gut feel. The next RFQ shortlist starts from evidence.
Contract register
04Contracts carry their renewal windows and negotiated rates, and purchases check against them — so off-contract spend is visible the week it happens, and no renewal date sneaks past because it lived in a spreadsheet tab.
03 · Process
How it works
- 1You
Describe your purchasing process
Who requests, who approves at which thresholds, and what needs competitive quotes — plain language covers it. Dual7 shapes the entities and routing to match.
- 2Vibe mode
Refine in Vibe mode
Adjust conversationally: add a three-quote rule above $10k, a budget-check step, or a category tree that mirrors your GL codes. Each change lands as inspectable code.
- 3Governed mode
Go live through the governed pipeline
Ship with approval gates and a full audit trail — fitting, for a system whose whole job is auditability — deployed on your infrastructure with spend data in your database.
04 · Fit
Who the Procurement starter is for
Finance teams replacing email-thread approvals
When approvals live in inboxes, the audit trail is an archaeology project and nobody can say what's committed but not yet invoiced. This starter gives every request a record, every decision a timestamp, and finance a live view of pipeline spend.
Operations leads at companies outgrowing spreadsheets
The purchasing spreadsheet works until two people edit it at once or a vendor asks which PO a payment covers. Moving the same columns into connected tables buys you concurrency, history, and reporting without adopting an enterprise suite sized for a company ten times yours.
Companies quoted enterprise pricing for basic workflow
Procurement suites price for global enterprises, and mid-size companies end up renting a fraction of a platform. Generating your own system costs a fraction and covers the workflows you actually run — requests, approvals, RFQs, contracts — with room to grow into more.
Regulated businesses that need the trail
If audits or certifications require documented purchasing controls, the system of record matters. Here the controls are explicit code you can show an auditor, and every approval is a row with a name and a timestamp — not a forwarded email someone has to find.
05 · Yours
Customize it, own it
Make it yours
Start by making the vocabulary yours: cost centers become departments or projects, categories mirror your chart of accounts, request forms carry the fields your finance team actually needs. In Vibe mode, adding a budget-remaining check at submission or a preferred-vendor flag on categories is a conversation, not a project.
Deeper changes stay ordinary engineering: sync approved purchases to your accounting system, add a receiving step that closes the loop between what was ordered and what arrived, or expose a lightweight request form to the whole company while keeping the buyer's console internal. It's a standard codebase — your team extends it like any other app, with no runtime tie to Dual7.
Why a starter, not a subscription
Procurement platforms charge per user and per module, which quietly shapes your process to fit your license count — requesters share logins, approvals happen offline, the audit trail leaks. When the system is code you own, everyone who spends money gets a seat, because a seat is a database row. Your spend data, vendor history, and approval records live in your database, not in an export you'll negotiate for later.
The honest trade is that you operate it. Dual7's governed pipeline carries most of that weight: gated releases, an audit trail on the system itself, and regeneration when your purchasing process outgrows its current shape.
06 · Industries
Industry versions
Procurement template — frequently asked questions
What's included in the procurement template?
Six connected entities — vendors, purchase_requests, rfqs, quotes, approvals, contracts — plus threshold-based approval chains, an RFQ workflow with side-by-side quote comparison, vendor scorecards, and a contract register. Generated as a full-stack codebase you own and run.
Can approval rules match our actual thresholds and hierarchy?
Yes — that's the point of generating rather than configuring. Routing by amount, category, cost center, and role is written into your code from your description, and revising it later is an edit you can review, not a settings maze.
Does it handle RFQs and competitive bidding?
The RFQ flow is built in: create an RFQ from one or more requests, send it to selected vendors, capture structured quotes, and compare them line by line before awarding. The award decision and all competing quotes remain on record for later review.
Can it integrate with our accounting or ERP system?
The generated app has a standard relational schema and codebase, so pushing approved purchases or vendor records to your accounting system is normal integration work against tables you control — no vendor API tiers between you and your own data.
Is this suitable for a purchasing audit trail?
Every approval is a persistent row with approver, timestamp, and comment, and requests carry their full chain of decisions. Because you own the schema, you can extend retention and evidence to whatever your auditors require.
How is this different from procurement SaaS?
SaaS procurement rents you a workflow shaped by its largest customers, priced per user per month. This starter generates a system shaped by your process, at a fixed cost, in code your company keeps — including every record in it — regardless of your relationship with Dual7.
Related
Dual7 App Starters
Build your Procurement on your terms
Purchase requests, approval chains, RFQ comparisons, and vendor scorecards — generated as a full-stack app your company owns. Describe your version to start — the output is a project you own.