You already own Salesforce. You are using a fraction of it

If your firm already licenses Salesforce, the platform decision has been made and paid for. The open question is narrower than it looks: does delivery, time, cost and billing sit on the same customer record as the sale, or somewhere else.

In most firms we speak to, the answer is somewhere else. Salesforce holds the pipeline. Delivery runs in a project tool. Time sits in a timesheet app. Billing is assembled in a spreadsheet and posted to the ledger. The customer record stops at the point the deal is marked closed won.

The mistaken diagnosis

The usual reading is that Salesforce is a CRM and therefore the wrong place for delivery work. It was bought to manage sales, it is good at managing sales, and the operational side of the business needs something purpose-built.

That is a reasonable inference and it produces the wrong decision, because it treats Salesforce as a product category rather than as a data model with a governance layer already attached.

What a CRM licence actually buys you is an object model, a permission and sharing model, an identity and authentication layer, field-level audit history, an API surface, and a release and backup regime. None of those are sales features. They are platform features that any system holding your commercial record will need, and that most standalone tools have to reimplement at a lower standard.

What you have already funded

The practical consequence is that the expensive part of the platform decision is behind you.

Your administrators already know the security model. Your access reviews already cover it. Your single sign-on and multi-factor policies already apply to it. When the auditor asks who changed a rate and when, the field history is already being written. The specifics of how that governance layer works are set out on our security and governance page.

Extending that record to cover delivery, time, cost and billing does not require funding any of it a second time. It requires the objects and rules that professional services work needs, sitting on top of what is already there.

That is the shape of DAY ONE. On Salesforce; works with your Salesforce org, or available as a bundled edition if you don’t use Salesforce.

What changes when the record does not stop at the sale

The difference is concrete rather than architectural.

An engagement carries its commercial terms from the point it is quoted, so time entered against it inherits the rate and the billing rule rather than being classified by somebody later. Approval becomes a state on the record instead of an email thread. A change order attaches to the engagement it changes, priced before the work is delivered rather than after.

Work-in-progress is composed of entries that each link back to the work, the approval and the clause that permits billing them, so a question about the balance is answered by traversing the record rather than by convening the people who remember. Forecast and actual sit against the same object, which means the two numbers stop being produced by two different processes.

Integrations behave differently as well. Because the operating record stays inside the org, a connected tool reads from and writes to the same governed structure rather than establishing a parallel copy that has to be reconciled. The replace, coexist and phase patterns for that are described on our integrations page.

Where this argument does not apply

Two honest limits, and both of them matter.

If you do not use Salesforce, none of the above is an argument for you. The bundled edition exists and it is a genuinely different commercial conversation — you would be evaluating the platform on its merits and its cost, not treating it as sunk. Do not let a sunk-cost argument be sold to you as a greenfield one.

And if you already resent your Salesforce licence, extending it will not fix that. Salesforce carries real administrative weight: someone has to own the org, manage releases, keep the permission model coherent and stop the field count sprawling. A firm that has never enjoyed that overhead will not enjoy more of it. Consolidating onto one platform also concentrates risk — a single vendor relationship, a single availability profile, a single commercial negotiation. Those are legitimate reasons to decide the other way.

The argument is not that Salesforce is the right platform for everyone. It is that if you are already paying for it, the comparison you are actually making is between extending a governed record and buying a second one — and those are not the same purchase.

Where to start

The position, restated: for a firm already on Salesforce, the platform question is closed and the open question is scope of record. The counterweight stands — if the licence is a grudge rather than an asset, extending it is the wrong move, and you should say so before anyone builds a business case on top of it.

If it is an asset, the next question is how small the first slice can be while still proving the point. Our approach to that is set out on the QuickStart implementation page.