Automating SaaS Procurement: From Request to Contract in Days, Not Weeks

Manual SaaS procurement — email chains, spreadsheet trackers, waiting for approvals from people who are in meetings — is the primary driver of shadow IT. Employees don't adopt tools without permission because they want to bypass governance; they do it because the official process takes longer than the problem they're trying to solve.

The Anatomy of a Slow Procurement Process

Most slow procurement processes share the same failure modes: intake is informal (email or Slack), there's no single system of record, approvers don't know a request is waiting, and there's no defined SLA for a response. Each of these is fixable independently.

Step 1: Standardise Intake

Create a single intake form — in Liceo, Jira Service Management, or even a well-structured Google Form — that every software request flows through. The form should capture tool name, use case, user count, data types, and estimated cost. No form submission, no approval.

Step 2: Automate Routing

Based on the intake data, automatically route the request to the appropriate reviewers. Low-risk tools route to IT only. Tools processing personal data route to IT and DPO. Tools above a cost threshold route to Finance. Automation eliminates the manual triage step that often causes the first delay.

Step 3: Set and Publish SLAs

Commit to a response time — 48 hours for standard requests, five business days for tools requiring legal review. Publish this commitment. When employees know the process has a defined end date, they're less likely to go around it.

Step 4: Automate Contract and Compliance Record-Keeping

Every approved tool should automatically generate a contract record and procurement entry in your SaaS management platform. This closes the loop between procurement and asset management: the tool appears in the inventory from day one, with its cost, renewal date, owner, and compliance status pre-populated from the intake form data. No manual data entry, no gap between approval and tracking.

For tools requiring Data Processing Agreements, automated procurement workflows can generate a DPA request to the vendor as part of the approval flow — ensuring GDPR compliance is handled during procurement rather than as a separate post-implementation task that often gets forgotten. Track DPA status as a field in your software inventory and alert the DPO when tools processing personal data don't yet have a signed DPA in place.

Measuring Procurement Cycle Time

The most important metric for your procurement automation investment is cycle time reduction: how many days from request submission to tool available for use, before and after automation. Before automation, most organisations report 10–25 days for a standard tool request. After automation, well-run programmes achieve 2–5 days for standard requests and same-day for catalogue tools. This reduction is directly measurable and directly attributable to the process improvement.

Track cycle time by request type and by reviewer team, so bottlenecks are visible. If the IT review typically completes within 24 hours but the legal review takes ten days, the intervention point is legal, not IT. Automated routing and reminder escalations help, but some bottlenecks require process change — pre-approving standard DPA terms for common vendor categories, for example, can reduce legal review time from days to hours for the majority of tool requests.

Communicating the New Process

Even the best-designed procurement automation is useless if employees don't know it exists or how to use it. Launch the new process with an all-hands communication — explaining why the change was made, how to submit a request, what to expect in terms of timeline, and who to contact if there's an issue. Follow up with department-specific briefings for the teams most likely to submit software requests (Engineering, Marketing, Sales). A well-communicated launch achieves compliance rates 2–3× higher than a quiet system update.