SiliconANGLE theCUBE Sep 18, 2026
With Mike Piehl, CEO of Platinum River Innovations
Platinum River Innovations has moved its Salesforce implementation work onto fixed-bid contracts, and Mike Piehl said that when clients are given the choice, the finance side of the decision picks fixed about 95% of the time.
For most of his two decades in consulting that would have been the contract to avoid, because the firm absorbs whatever goes wrong between signature and go-live.
"we would have run from a fixed bid project like the plague"
Piehl runs a Salesforce consultancy for financial services clients, concentrated in insurance and wealth management, whose consultants have 20 to 25 years in those industries. He brought Certinia into the business a year ago and has since rebuilt the firm's contracts, its tool mix and its internal incentive plans around AI.
The full interview is covered here so you can skip it.
Here are the 13 arguments that matter.
Key Takeaways
The contracting model changed before the tools did, to make room for everything after it
Some projects now cost 80 to 90% of what the same work cost two years ago, on his account
The kickoff meeting is now followed immediately by a custom prototype, which he says removes the largest risk in a project
Fewer hours per project but more projects is why his headcount need is rising rather than falling
Fixed bid transfers the risk to the consultancy, which is the point, and it is what he says converts new clients
True outcome-based pricing fails on legal grounds, not technical ones, because it makes the consultancy something like an equity holder
Hourly contractors will not adopt the tools, because speed cuts their own billing
A cross-sell task that took weeks ran in about five minutes on his telling
Offshore hourly labor is the cost base he expects AI to undercut, at $20 to $30 for the same job
He expects market share to move to smaller firms, because the large ones cannot restructure
1. Who Platinum River Serves
The firm implements Salesforce for financial services companies, with a concentration in insurance and wealth management.
The business in his own words
So we are a Salesforce implementation professional services organization and we focus on business outcomes and consulting in and around the Salesforce ecosystem
Mike Piehl
Most of his consultants came out of the industries they now sell into, with 20 to 25 years of experience between working in them and consulting to them.
Certinia came in a year ago
We brought Certinia into our business about a year ago
Mike Piehl
The first use was continuity: meeting transcripts from the sales process feeding a knowledge graph around the client, carried through the project management layer so the delivery team knows what was promised before the contract was signed. The relationship widened from there, and he said the effect on the business has been large.
2. Three Moves In 12 Months
The AI transformation started about 12 months before the interview, and Piehl described it as three changes in a deliberate order. Contracts came first.
Contracting had to change before anything else
The first piece is we changed our contracting model with our clients because we need to make head space with how we work with our clients first.
Mike Piehl
Tools came second, with some substitutions along the way. The method he described is to pull requirements out of the recorded conversation rather than writing documentation, then generate the requirements, generate the code, deploy, test for quality and move on.
The cost fell and the margin rose
So we've had a number of projects that we've done where it's about 80 to 90% of what the cost would have been two years ago.
Mike Piehl
Internal cost came down, margins went up, and he said the firm can now take projects that used to be impossible because the client price would have been prohibitive.
The third change was compensation, and it is the one most firms have not made.
Hourly incentives break under AI
And if you think about having AI provide more productivity, the hour count falls
Mike Piehl
The traditional professional services model pays by the hour, so productivity gains cut the very number the firm bills on. He said the incentive plans had to be rewritten to keep adding client value while the hour count falls.
3. A Prototype At Kickoff
Asked what is materially different for a client, Piehl named price first and speed second. The methodology change is that a custom-built prototype now follows the kickoff meeting immediately, built from the client's requirements.
The old sequence, which he laid out step by step, was to sign a contract, wait four to six weeks for staffing, hold a kickoff, run three to four weeks of discovery, build for a couple of months, then test and go live. The client saw nothing until the end.
The risk that prototype removes
Usability risk is one of the largest risks in projects.
Mike Piehl
When the client cannot see the work until the end, any change is a large change order and the release date moves. Putting a prototype in front of them in the first week is what he says takes that risk out.
4. Clients Spend The Savings
The lower price on the original scope does not stay a saving. Piehl said clients come back and add services once they see what the budget now buys: on-site training where they would previously have accepted a virtual session, adoption services, and a plan for what happens after launch.
He also described a better handover from project work into managed services, which he attributed to the same arithmetic — the same budget now covers more.
5. The Labor Demand Paradox
The host raised the standard fear about AI and jobs. Piehl's position is that his own firm needs more people, not fewer, and he separated the two effects to explain why.
Per project, the hours fall
So, what we're seeing in practice is that the labor demand on an individual project is coming down, which normally would mean you need fewer people.
Mike Piehl
In aggregate, demand rises
So, more projects coming in and the net effect is we need more people.
Mike Piehl
The mechanism is price: lower price points and higher delivered value bring in more client demand, and more projects need more staff even when each one needs fewer hours.
6. Why He Took Fixed Bid
Fixed bid was the first change the firm made, and it inverts who carries the risk. In his 20-odd years in consulting, a fixed-bid project meant the firm absorbed anything unexpected, which is why nobody wanted one.
The productivity gains changed the calculation, because they create room to make adjustments and experiment with tools without the client paying for it.
The consultancy now carries the risk
So we're underwriting that risk not having the client take on that risk and so that was one of the big adjustments we made at the beginning.
Mike Piehl
He said taking the uncertainty away is part of what converts new clients.
7. Why Not Outcome-Based
Asked whether outcome-based bids are the same idea, Piehl said no, and his objection is contractual rather than technical. His example was a Salesforce project meant to grow sales 10% at a firm doing millions in revenue, paid as a cut of that growth.
Payment tied to results makes you a shareholder
means that you're basically taking on almost like an equity partner because there'd have to be reporting requirements into the future for whatever the payment terms are.
Mike Piehl
And that is a different kind of contract
I think it's more of a legal issue
Mike Piehl
Taking a percentage of a client's sales or profit three or four years out, he said, puts the relationship at a legal bar that a fixed price for a defined scope does not. Fixed bid lets the firm promise the outcome it actually controls: the project, not the client's business results.
8. The 1099 Problem
There is friction inside the model, and Piehl was direct about where. Salaried staff are aligned with fixed-bid work because their pay does not depend on hours. Contractors are not.
Hourly pay works against tool adoption
if we have somebody that's coming in that gets paid by the hour they're less likely to use the tools because it makes them faster
Mike Piehl
He said the firm has seen an adoption problem with most of its contract resources for exactly that reason, unless they can be put on several projects at once.
9. Certainty For Project Teams
Certainty is the theme Certinia sells on, and Piehl said it applies at two levels in his firm. In pricing, it means quoting a fixed bid while knowing the margin. In delivery, it means the project team can ask the system what was agreed.
The scope question, answered by an agent
So being able to go into Certinia and ask a question like hey was anything discussed in the scoping meeting that's out of scope and have the agent right away come back and say yeah this is out of scope
Mike Piehl
The same applies in reverse, where someone does not remember a topic from the kickoff and wants to know where in the pre-sale process it came up.
What is next is plumbing. The firm is building out agent customization inside Certinia and the platforms around it.
Connected with MCP servers
We're also using some MCP servers to connect them.
Mike Piehl
The target is conversation to code
So we can go through and take requirements and pre-sale conversation turn that directly into requirements user stories and then generate the code for that prototype straight through.
Mike Piehl
That runs on projects today with some manual steps in the middle, and he expects to have it clean by the end of the year. The part he said he is waiting on is the vendor's roadmap: the back end that handles his services automation and invoicing is disconnected from the front, and connecting it would give him one view across the stack. That is where his own process is still manual.
10. Where The Agent Belongs
On governance, Piehl said the firm has run several Salesforce AI workshops with clients, and that the recurring question is how to use two large investments together — an enterprise Salesforce agreement on one side and an enterprise AI account on the other. He said the firm is expanding its relationship with Anthropic so it can offer capability on both.
The workshops surface use cases that were not previously possible. His example was pulling the top 10 accounts in a market, asking what to cross-sell and upsell based on purchase history, and drafting the email or call script to do it.
Weeks of work, run in minutes
That sort of engagement or effort would have taken weeks in the past and now turning on Salesforce co-worker I've seen that go through and inside of about five minutes
Mike Piehl
The governance question he cares about is which tool gets which job. Bringing Salesforce data into Claude gives a chat interface that can do things the CRM cannot, such as finding look-alikes or merging data from several systems into one answer, but it remains a text interface. In business-to-business sales the work happens on a record: the account page, the opportunity, the products, or a claim being checked for fraud. He said the AI has to be where the user already is.
Clients ask for Claude because it is the new thing, he said; when he digs into where the work actually happens, the answer is Salesforce. Deciding where to put which agent is the governance work he says is genuinely differentiated, because the rest of the category has been commoditized by Salesforce's own investment in its trust layer.
11. What Lands In Q4
The recent announcement he ties this to was a couple of weeks old at the time of the interview, and he said demand for it is already real.
Clients are asking how to turn it on
We have multiple clients that have asked us for how to get Cloud Force turned on and active discussions with getting engagements going with them.
Mike Piehl
He put the timing at calendar Q4 and described two directions of travel. The first is client-built capability reaching CRM data.
Skills built outside, run on Salesforce data
But we have clients that have gone through and have built out skills in Claude
Mike Piehl
The second is the reverse: a user who wants to stay in Salesforce because that is where the job happens, connected outward to trigger integrations and workflows in other systems. He expects both in the same quarter.
12. The CFO Picks Fixed
Asked whether fixed bid is durable or a moment, Piehl gave a number. He said the firm meets clients where they are, and then described what happens when the choice is put to them.
The finance side decides, and it decides quickly
probably 95% of the time as soon as we ask would you rather be time and materials or fixed bid, the CFO portion of the decision-making process will say fixed.
Mike Piehl
The other 5%, he said, is almost always someone with a bad personal history. He described a conversation six months earlier with a client who had worked in home renovation as a teenager.
Why one client will not sign a fixed bid
He said every time we opened up a wall, we'd find something.
Mike Piehl
The assumption behind that objection is that a fixed price simply prices in every contingency. Piehl's answer is that a firm doing so prices itself out of the market, so competition holds the padding down.
13. Smaller Bites, Faster Value
Fixed bid used to mean one large release, and the firm has deliberately broken that pattern.
The old shape of a fixed-price project
Used to be fixed bid was like a monolithic approach
Mike Piehl
Why the sequencing matters economically
As soon as your feature's in prod, you get value from it.
Mike Piehl
The approach is a minimum viable product first, with anything beyond it handled as a change order — initiated by the client, with an expected price and schedule effect, rather than discovered by the consultancy late in the build.
The client can see where the money goes
but clients in control and they have clear line of sight to where all their money's going.
Mike Piehl
And the relationship is easier
And so we've had a lot lower friction with our clients that are in the fixed bid model than the ones that came over with us from TNM.
Mike Piehl
Bonus Insights
Piehl's competitive argument is that the large consultancies cannot follow him.
The big firms cannot restructure
larger competitors have so much organizational inertia
Mike Piehl
Their model, he said, is built on high-volume, low-value work delivered offshore to make the economics work. The task he used as an example is two weeks of one person's time that now takes a couple of hours.
What the same task costs now
you can get that same job done in maybe 20 to $30
Mike Piehl
Set against an offshore hourly rate, he called that a big flip, and said he expects his firm's market share to expand quickly over the next couple of years.
Clients are compressing their own timelines
So being able to do things in six months that would have taken two years
Mike Piehl
Clients taking up these capabilities are hitting their own outcomes sooner than they had planned for, he said, which is a separate effect from the price coming down.
The host's own thesis
The host argued that professional services is the industry to watch to understand where enterprise AI is going, because it is leading, and said this conversation had been about economic value rather than technology. He also observed that the pace is faster than the shifts to cloud and to client-server, and described Salesforce as becoming increasingly headless — a back end whose functions are reached through agents rather than through its own screens.
Piehl's bottom line is that AI in consulting shows up first in the contract rather than in the code: price the outcome, carry the delivery risk, and the demand that follows needs more people rather than fewer.
Products, Companies & Tools Mentioned
Certinia (Brought in a year ago to carry sales-process transcripts into project management, and the system his teams query about what was agreed in scoping)
Salesforce (The platform his firm implements, and whose trust layer he says has commoditized most of the AI governance category)
Platinum River Innovations (His firm: Salesforce implementation for insurance and wealth management, now on fixed-bid contracts with rewritten internal incentives)
Anthropic and Claude (The relationship he is expanding, and the chat interface where clients have built skills that he expects to reach Salesforce data in Q4)
Cursor (Named as part of the tool mix the firm assembled alongside its Salesforce and Certinia work)
Watch the full episode:
More Mike Piehl interviews and podcast appearances
If this was worth your time, send it to someone closer to the industry than you are.
Get the latest market chatter as it happens: