Operations
Part of When to standardise proposal software operations as your team grows
Eight proposal software team roles to define and assign
Eight proposal software team roles for UK B2B quoting teams, with the duties, owners and seven assignment steps that keep quotes accurate.
What to take away
- The usual mistake is buying seats before deciding who owns the data, the template and the send.
- Eight roles cover most UK B2B quoting teamsdata steward, template owner, pricing checker, approval gatekeeper, sender, content librarian, integration contact and reviewer.
- Data protection duties attach to quote content that names people or carries personal terms, so the data steward role is not optional.
- Write one owner per role and one deputy, or the work drifts to whoever is nearest the deadline.
- Match each role to a named process in your proposal software operations and delivery guide rather than to a job title.
Why role clarity matters before you buy
Most teams evaluate proposal software, quoting software and CPQ tools on features, then discover nobody agrees who maintains the content library. The licence is the easy part. Ownership is the hard part.
Ownership also has a compliance edge. Quote documents that name individuals or carry personal terms sit inside the UK GDPR and the Data Protection Act 2018, and the Information Commissioner's Office is the regulator for both; the Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019 amended that framework after EU exit. That makes the data steward role a control, not a courtesy — someone has to decide what personal data a quote holds, where it sits and how long it is kept.
The eight roles
A practical inclusion test: a role belongs on this list only if a named person can be held to it in a weekly review. Roles that describe an aspiration, such as "champion", do not qualify. The geography here is UK-wide, with Scotland, Wales and Northern Ireland teams applying the same eight roles unless a sector regulator adds its own.
Each role below carries a line of duty and a decision right, so a weekly review can hold a named person to it.
- Data stewardowns the quote data itself: what personal data a quote holds, where it is stored, who can see it and how long it is kept. Can stop a send if data handling is unclear.
- Template ownerowns the master templates and their versions. Approves changes, retires outdated layouts and keeps one current version in use.
- Pricing checkerchecks prices, discounts, currency and margin figures against the approved price list before a quote leaves the system. Can hold a quote back when a figure does not reconcile.
- Approval gatekeeperowns the approval gates: decides which discounts, terms or non-standard clauses need sign-off, from whom, and records that it happened.
- Senderowns the final send. Confirms the recipient, the attachment version and the delivery route, and logs that the quote went out and when.
- Content librarianmaintains the content library: case studies, boilerplate, biographies and product descriptions. Sets review dates and removes claims that are no longer supported.
- Integration contactowns the connections between the proposal software and the CRM, e-signature and finance systems. Raises and tracks faults with the vendors.
- Reviewerreads a sample of sent quotes each month against the price list and the template, and reports errors back to the other seven owners.
Eight proposal software team roles
- Data stewardowns quote fields and retention
- Template ownerholds approved documents and versions
- Pricing checkerconfirms discounts, currencies, rounding
- Approval gatekeeperdecides and records sign-off
- Sendercontrols final send and audit trail
- Content librariankeeps case studies current
- Integration contactowns CRM data mapping
- Reviewerruns post-decision review
How to assign them in a week
Run this sequence rather than debating titles:
- List the eight roles and the work each one covers.
- Name an owner and a deputy for every role in a single shared document.
- Write one line of duties and one decision right per rolewho can hold a quote back, who can approve a discount.
- Map each role to the steps in your quote-to-cash process, from enquiry to signature.
- Walk one live quote through the whole map and note where nobody had a job.
- Publish the role map where quoting software users will see it, and link it from the template folder.
- Diary a quarterly review, plus an out-of-cycle check after any new product launch.
Assign roles in one week
- List live proposals and quote templates
- Name the current owner of each
- Map each template to the eight roles
- Mark gaps where roles overlap
- Nominate a deputy for every gap
- Agree monthly or quarterly review cadence
- Record outcome and share with sales, finance, legal
Cross-functional alignment is the point. Forrester describes cross-functional alignment as coordination between sales, marketing and other teams, which is exactly what a shared role map produces.
Keeping the roles alive
Document control is where role maps decay fastest. BSI's guidance on quality management systems standards covers document control and versioning, which maps cleanly onto the template owner and content librarian duties above.
Expect drift when a new product line launches or a salesperson leaves. A short internal review after each launch — checking who owns the template, the pricing fields and the send — catches role gaps before they reach customers. Reassign any gap in the weekly review rather than waiting for the quarterly one.
For example, a team paying £400 a month for quoting software can still lose a deal because nobody checked the currency field. The subscription did not fail. The role map did.
Common questions
Should one person hold several roles?
Yes, in small teams. Combine them deliberately and record the combination, so a gap is visible when someone leaves. Avoid leaving data steward and approval gatekeeper with the same person if deal volumes are high.
Do we need a data steward if we only send business-to-business quotes?
Yes, if any quoted document names an individual or contains personal terms. The data steward decides what is stored, where it sits and how long it is kept.
How often should the role map be reviewed?
At least quarterly, and after any change to your quoting software, CRM or product range. Add an out-of-cycle check whenever a new template is approved.
Who owns the quoting software contract itself?
Usually operations or finance, not the heaviest user. Keep the commercial owner separate from the template owner so renewal decisions do not rest with the person most attached to the current setup.
