Skip to content
Resources // Insights

Own the outcome

The four questions we ask of every technology decision.

Avatar photo
Chris Renaud
Chief Technology Officer

If you’re evaluating a technology partner, ask them two questions. How will you know it worked? And who answers if it didn’t?

We put those questions to every decision we make at Derivative Path, and we expect our partners to answer them too. This series is about how we answer them. This first piece covers how we know.

Most technology decisions get judged on the day they launch. The release goes out, the project closes, and everyone moves on to the next thing, even though launch day is when the client’s experience of it only begins. We judge ours on the day the client feels the difference.

AI has made it faster to build almost anything, and that makes one question matter more: does the work change anything for the treasurer or CFO on the other end?

The outcome test

Every decision we make, from a platform change to a hire to a vendor selection, has to answer four questions.

  1. 1. What should be different when we’re done? We describe it in the client’s terms: time saved, errors removed, risk reduced. “We’ll implement a new system” doesn’t count. “A treasurer sees their exposure in seconds instead of hours” does. If a piece of work can’t name its outcome, we say no.
  2. Who owns it? One person, by name, and they stay accountable after launch, well past go-live.
  3. How will we know? If we can’t measure it, we haven’t defined it, so we agree up front on the signal we’ll watch and the date we’ll look. I’d rather see milestones that show impact than a date on a slide.
  4. Did it show up? We go back and look on purpose. If the result is there, good. If it isn’t, we decide whether to fix it or unwind it, and we share what we learned.

Same cost, whole firm

We looked at where AI was going in the sales process and chose a very well-known sales tool. Everyone in the industry was using it, so it felt like a given. We went live with real ambition: capture the sales calls, the process and the playbook around them.

Along the way, we found the licensing limited access to the sales team. Everything we were capturing stayed inside that tool, and the rest of the company couldn’t use it.
We re-evaluate software at every renewal, so we took another look at the vendor and its competitors and held the vendor’s roadmap to a standard. They were progressing, just not as fast as a competitor that was much smaller and far less well known. What interested me was that the smaller vendor’s licensing let us give access to the whole firm, and it was moving faster on where AI was heading. Now the feedback from our sales calls reaches the teams that serve clients and the people who build the product. We get a full-cycle view, from a client or prospect all the way down to the engineer working on it.

Buying the biggest name had seemed like the safe course. Every vendor in the market is heading toward AI, and what separates them is how fast they get there. If one isn’t picking up the new technology, there is plenty of disruption out there, and we shouldn’t be afraid to make a change. We wanted a company that learns from its clients, and the first tool was keeping that from happening.

Today everyone across sales, client service and engineering learns from every client conversation, at the same cost.

The test only works if the reasoning behind each decision is written down where the next person can find it, which is the next piece.

Next article Write it down.

Avatar photo
Chris Renaud
Christopher Renaud is the Chief Technology Officer at Derivative Path, where he leads the development of innovative financial technology solutions. With expertise in commercial debt management, mortgage-backed securities, and enterprise solutions, he has co-founded multiple fintech startups, including Monetics, which was acquired by Derivative Path. Previously, he held leadership roles at Natixis, guiding enterprise technology initiatives. A passionate technologist, Chris excels at building high-performing teams and driving transformation through innovation. He holds a degree in Computer Engineering from Conestoga College.

Stay up to date

Sign up for our latest insights, news and events