Business systems
Giving Legal 40 hours a month back by fixing the contract flow
Asking the people who felt the pain, designing for Legal's ideal state, and taking PandaDoc CPQ from idea to go-live.
Written by
Bianca Lomeli
Technical Program Manager
A contract is where a sale becomes real. When the process behind it is slow, everyone feels it, but nobody owns it.
At ParsePort I ran our business systems as super admin, including the CRM our Sales and Customer Success teams lived in. From that seat I could see what the contract flow was costing us: hours of Legal's time every month, and a process that depended on a single point of failure.
I took a CPQ (configure, price, quote) tool, PandaDoc CPQ, from idea to go-live. Here's what made it work.
Start with the people who feel the pain
I didn't start with the tool. I started with conversations.
I interviewed Sales and Customer Success about the pain points in the contract flow: where they got stuck, where they waited, and where things went wrong. Then I spoke with Legal, but with a different question. Instead of asking what hurt, I asked what their ideal state looked like.
That difference mattered. The commercial teams told me what to remove. Legal told me what to protect.
Design for the ideal state, not just the fix
It would have been easy to speed things up by loosening control. That would have made Legal's job harder, not easier.
Instead, we locked the contract wording with permissions. The commercial teams could build and send what they needed, but the legal language stayed the way Legal had approved it. Speed for one team didn't come at the expense of risk for another.
Treat the vendor rollout as part of the project
A tool like this doesn't arrive ready. PandaDoc had to onboard us and build our templates in their backend, and I led the rollout, including that onboarding and template build.
The lesson: when a vendor is part of your delivery, their work is on your critical path. Plan for it, check it, and speak up early when it isn't where it needs to be.
Make go-live a decision, not a date
Before we switched over, I used a go/no-go checklist, and we recorded it in Google Drive so there was an audit trail of what we'd checked and who had signed off.
A switch-over succeeds or fails before it happens. Everything has to be in place and tested against real use before you flip the switch.
The result
Legal got 40 hours a month back, and the contract process no longer depended on a single point of failure.
What I'd tell anyone rolling out a business system
Ask the people who feel the pain what to remove.
Ask the people who carry the risk what to protect.
Build control into the tool, so speed doesn't cost you safety.
Put the vendor's work on your plan, not just in your contract.
Decide go-live with a checklist, and keep the record.
Good business systems are invisible. People just notice that the work got easier.