Before FinancialForce was a company, it was a product looking for oxygen. Coda 2go had put accounting software on Salesforce's Force.com platform at a moment when finance departments still treated the cloud like an unlocked filing cabinet. The technology was early. The commercial evidence was less impressive. An InformationWeek report at the 2009 launch observed that, after two years, Coda 2go could point to only one customer success story on its website.
This is where the story gets useful. FinancialForce was not invented in a garage by people who had never closed a ledger. It combined Coda's decades of accounting experience with Salesforce's platform, money, support machinery, and distribution. Unit4, which owned Coda, took the majority position; Salesforce became the minority investor. Coda chief Jeremy Roche ran the new venture, while product leader Deb Ashton helped build the company and remains a founder at Certinia today.
Their pitch could fit on a napkin: put the back office on the same cloud as the front office. A salesperson closes an opportunity. A delivery team staffs the work. Consultants submit time and expenses. Finance bills the customer and recognizes revenue. In the usual software stack, each handoff crosses a database, an integration, or somebody's heroic spreadsheet. FinancialForce kept the customer record in Salesforce and built the operational chain beside it.
The integration that never had to exist
The best way to understand FinancialForce is as an integration problem removed at the foundation. NetSuite, Microsoft Dynamics, Sage Intacct, Oracle, SAP, and a fleet of specialist PSA tools can all exchange data with Salesforce. Certinia's claim is different: its applications are native to the Salesforce platform. The data model, permissions, reporting, workflow tools, and user interface live in the same neighborhood.
That distinction matters most to services businesses. Their inventory walks out of the office every evening. Profit depends on assigning the right person, at the right rate, to the right project, then turning approved work into an invoice before the month becomes ancient history. Professional Services Cloud handles resource planning, projects, time, expenses, utilization, and project economics. Financial Management Cloud covers accounting, billing, revenue recognition, cash, and reporting. Customer Success Cloud adds health scores, playbooks, and renewal orchestration. Services Estimator carries opportunity data into scopes and delivery plans.
The payoff appears in unglamorous numbers. Clearsulting says it cut its billing cycle by six days, reduced month-end close from 12 days to five, and saved three hours a week on data gathering. Siemens Digital Industries Software uses the system for roughly 450 new delivery projects and 7,000 resource requests each month. These are not viral-product statistics. They are finance-and-operations statistics - exactly where a serious PSA earns its keep.
“The back office actually has to become part of the front office.”Jeremy Roche, founding CEO, speaking in 2015
The name worked until it became a blindfold
FinancialForce was an excellent 2009 name. It explained finance on Force.com and borrowed the halo of its platform partner. It was also a shrinking description of the company by 2023. PSA had become central. The suite now included customer success, services estimation, and financial planning. Calling all of that FinancialForce was like calling an airport a runway.
So the company became Certinia in May 2023. Then-CEO Scott Brown was unusually plain about the trigger: the old name described the original ERP intent, not what the company did anymore. Certinia, drawn from “certainty,” promised one view of the services business from opportunity to renewal. It was a positioning change, not a platform divorce. Salesforce stayed in the architecture and on the cap table.
The timing helped. Two months later, Haveli Investments and General Atlantic agreed to acquire Certinia from Advent International and TCV. Reuters reported the transaction at nearly $1 billion including debt, though the parties did not disclose terms. Salesforce rolled over its stake. Former SAP North America president DJ Paoni became CEO in October. TA Associates invested in late 2024, while Haveli kept control.
What changed minds was not a dramatic product failure. It was category mismatch. The first wrapper, Coda 2go, had too little commercial momentum. The second wrapper, FinancialForce, helped explain and distribute the product. Eventually it hid the expansion. The lesson is not “rebrand every decade.” It is to rename only when the old promise makes buyers systematically misunderstand the new product.
What it costs when the quote has no price
Certinia does not publish standard list pricing. That is normal enterprise-software behavior and terrible budgeting theater. The original Coda 2go was refreshingly specific at $125 per user per month in 2009. Current third-party estimates put Certinia broadly around $100 to $350 per user per month, depending on modules and access. A UK public-sector listing for Professional Services Cloud showed a very wide £300 to £2,628 per user per year.
The check has four lines, not one
Market guides estimate implementation from tens of thousands of dollars to $500,000 or more for complex deployments, typically over several months. Treat that range as a warning label, not a quote. A global, multi-entity finance rollout bears little resemblance to adding PSA for one 50-person consulting group. Training is material too: Certinia's 2025 academy catalog listed one eight-hour accounting administration course at $1,800 per person.
The first thing likely to fail is not the general ledger. It is adoption at the edges: late timecards, vague skills data, inconsistent project templates, or a sales team that closes deals without delivery-ready scope. One administrator described permission problems during implementation; others in Salesforce communities call the product capable but complex. Those reports are anecdotal, yet they match the structural risk. A shared system amplifies shared discipline. It also amplifies shared mess.
Now the database wants to do the work
In April 2026 Certinia launched Veda, an AI operations engine for services. Its agents can suggest staffing, replace a resource mid-project, surface account risk, assist project managers, and act across customer-success and finance workflows. The company says the system is rules-bound where money and governance demand precision, and generative where drafting saves time. Pricing combines per-user fees with usage-based consumption.
The interesting part is not that Certinia added AI. Every enterprise vendor has added AI. The interesting part is whether seventeen years of project, staffing, billing, and customer data gives those agents enough context to act usefully. Certinia made that bet more explicit in July by acquiring Moonnox, which captures unstructured work from tools such as Google Workspace, Microsoft 365, Jira, Confluence, and Zoom. One joint customer said a Moonnox agent reduced solution-architecture drafting from about 80 hours to under 20.
There is a catch sitting in plain sight. AI cannot rescue fragmented ownership, dirty project data, or fantasy resource forecasts. Certinia itself says context is the foundation. Veda works best where the underlying platform is already trusted and routinely maintained. Otherwise, an agent merely reaches the wrong conclusion faster and with better punctuation.
It fits
A mid-market or global services organization already runs Salesforce, bills complex work, needs multi-team visibility, and can support a disciplined implementation.
It strains
A small team wants lightweight project tracking, lives outside Salesforce, has simple billing, or lacks administrators to own data and process design.
The copyable part is the sequence
Founders cannot copy FinancialForce by appending “Force” to a noun. They can copy the order of operations. Start beside a dominant system rather than across town from it. Pick a costly handoff that customers already repair with exports and reconciliation. Use the platform's identity, permissions, reporting, and route to market. Expand along the customer's workflow, not into random adjacent categories. Keep the architecture when it works. Change the story when the story becomes a constraint.
The FinancialForce field guide
- Find the departmental border where data gets retyped and money gets delayed.
- Build on the system customers already trust, but price the dependency honestly.
- Sell an operating result - faster billing, better utilization, shorter close - instead of a prettier dashboard.
- Expand only where the same record and buyer create a real advantage.
- Do not add agents until the underlying data can survive an audit and a Monday morning.
The conditions where this does not work are equally clear. Platform-native strategy is weaker when customers are not loyal to the platform, when a dominant vendor becomes a hostile landlord, or when the workload needs capabilities the host was never designed to handle. Certinia is not a manufacturing ERP. It is not a bargain project tracker. It is not an escape from Salesforce complexity.
What it is, after two names and several ownership chapters, is a long-running argument that services companies should stop splitting the customer into departmental versions. FinancialForce made that argument with accounting. Certinia now makes it with an entire services lifecycle and a small army of agents. The name changed because the argument got bigger.