← Back to the blog
Procurement technology

Every team bought a solution. Who owns the whole picture?

The software bill keeps growing. Bring requests, assessments, approvals and signing together around the supplier relationship.

Every team has a tool. Who owns the whole picture? Fratera editorial cover with paper bundles and a teal document folder.

An IT team needs a better way to manage demand. Risk needs an assessment platform. Someone builds an approval process in Teams. Procurement buys an e-signature tool. Legal starts looking for a clause library and legal AI.

Each request makes sense. Each solves a problem someone has been carrying for too long.

Then a supplier comes up for renewal.

The business owner wants to know whether to continue. Procurement needs the contract and the notice deadline. Risk wants to check the latest assessment. Legal wants to know what changed in the terms. Finance asks what the company has committed to.

Who can bring those answers together?

That is where the cost of buying software department by department becomes visible.

The bill keeps growing

In our own company, the figures included about $100,000 to develop legal AI, $10,000 a year for e-signatures, $95,000 for an assessment platform, and $100,000 for demand management.

Those are examples from our own experience, with different cost bases. A development project and an annual subscription cannot simply be added up and called an annual software bill. They do show how substantial the separate investments can become.

And the purchase price is only part of the story.

Someone has to decide which supplier record is authoritative. Someone has to maintain the connection between the assessment and the contract. Someone has to update the approval process when responsibilities change. Someone has to explain why the information in one system differs from the information in another.

Often, that someone is a person with a spreadsheet and a very full inbox.

A relationship runs through all of these systems

A department sees the part of the relationship it needs to manage.

IT sees a request. Risk sees an assessment. Legal sees an agreement. Finance sees a commitment. Procurement sees a supplier, a renewal and a negotiation.

Those views need to meet when a decision depends on several of them.

An assessment matters more when the person approving a contract can see its outcome. A notice deadline matters more when the responsible owner knows which relationship it affects. An approval matters more when the decision and its context can be found again six months later.

When that context is scattered, people spend their time reconstructing it. They search folders, forward messages and ask colleagues whether a document is the latest version. The same questions return because the previous answers stayed inside one team's tool.

Start with a decision you actually make

Before buying another platform, follow one ordinary piece of work from beginning to end.

Take a new supplier request, for example. Where is the request raised? Who assesses it? Where does the assessment outcome go? Who approves the commitment? Where does the signed agreement live? Who receives the renewal reminder?

Then follow a renewal. Can the owner see the contract, the relevant risk position and the people involved without rebuilding the history?

These questions reveal what your organisation needs to connect. They also help you decide where a specialist tool earns its place. Deep capabilities can be valuable. The practical question is whether their outputs are available to the people making the next decision.

Put the relationship at the centre

Fratera is built around suppliers and contracts, with requests, assessments, approvals and signing forming part of the work around them.

That gives teams a shared place to understand the relationship and move work forward. A supplier becomes more than a name repeated across separate forms. A contract becomes more than a file someone has to retrieve.

For procurement, that means being able to bring the relevant information into the conversation. For the business owner, it means seeing what needs attention. For legal and risk, it means their work can inform the next step in the relationship.

The starting point is practical: make the record useful to the people who rely on it, and keep the decisions connected to it.

Take control of the whole picture

Buying software one request at a time is easy to understand. Every team has urgent work and a reasonable case for investment.

Someone still needs to ask what the combined result looks like.

Can you find the agreement? Can you see the assessment outcome? Can you identify the owner? Can you understand the commitment? Can you act before the deadline?

Those are the questions that determine whether your systems help you manage the relationship.

Before the next purchase, take one supplier and follow the work. See where the information holds together, and where people have to carry it by hand.

Then build around the whole picture.

Fratera. Where your relationships live.

Every team has a request

Demand management. Assessments. Approvals. E-signatures. Legal AI. Bring the work together around the relationship.

Read the video transcript

Every team has a request. And every request adds up.

IT: “We need demand management.” Added cost: $XXX,XXX. Risk: “We need an assessment platform.” Added cost: $XXX,XXX. Operations: “Let’s build approvals in Teams.” Added cost: $XX,XXX. Procurement: “We need e-signatures.” Added cost: $XX,XXX. Legal: “We need a clause library and legal AI.” Added cost: $XXX,XXX.

And where do your contracts and vendors live? In folders. In chats. In someone’s inbox.

Bring the work together. One relationship. Requests, assessments, approvals, contracts and signatures.

Bring it together. The symbolic bill changes from $XXX,XXX to $XX,XXX. One connected platform. The figures illustrate the concept.

Take control. Fratera. Where your relationships live. fratera.io

Where your relationships live

Take control of the whole picture.