Update Salesforce Revenue Cloud is now Agentforce Revenue Management. Same platform — now with AI agents on every workflow. Learn more →
The Method

We only take engagements we know we can win.

That's not a marketing line — it's how we protect our track record. Before we scope, we make sure we understand. If we can't define a clear path to success, we say so.

Non-negotiables

Four commitments on every engagement.

01
Don't start what we can't finish

On time and on the agreed scope.

02
What's in, what's out

Before work starts. Not after.

03
Escalate early

Problems surface the day we see them.

04
Build to leave

Your team owns the system after we go.

§ 02 — The process

Four phases.
Zero surprises.

Every engagement follows the same structure. The timeline varies; the process doesn't.

/ 01 · 1–2 wks

Discovery

Structured 2–3 sessions into current state — systems, data, processes, goals. We ask hard questions, document findings, and leave with a clear picture of what to build — including any supporting Salesforce work (Sales Cloud, Service Cloud, Data Cloud, Flow, integrations) the revenue program needs to actually land.

/ 02 · 3–5 days

Scope agreement

A detailed scope: what's in, what's out, what we need from you, success metrics. You review it, we align, we both sign. Fixed fee is locked here.

/ 03 · 4–8 wks

Fixed-fee delivery

We build. Weekly check-ins, async Slack updates. No surprises about budget or timeline — you see the same progress metrics we do, every week through go-live.

/ 04 · 30 days

Hypercare

30 days post go-live. Priority response. User adoption tracking. Admin handoff. We don't disappear after launch — we stay until it's stable and your team owns it.

§ 03 — Fixed-fee model

What fixed-fee
actually means.

Fixed-fee is only valuable if the scope is clear. Here's exactly what is — and isn't — included in every engagement.

Included

In the price

  • Everything in the signed scope — no exceptions
  • All configuration, testing, deployment
  • UAT support and bug fixes
  • Admin documentation and training
  • 30-day hypercare
  • Weekly status calls
Not included

Out of scope

  • ×Scope changes after sign-off (quoted separately)
  • ×Third-party licenses (Salesforce, Spiff, etc.)
  • ×Custom dev outside the signed scope (RLM, Spiff, or adjacent Salesforce work)
  • ×Ongoing managed services after hypercare
  • ×Generalist Salesforce programs unrelated to the revenue lifecycle
§ 04 — What we need

Three things from you.
Non-negotiable.

We move fast. To do that, we need a few things from your side on day one. Most projects that slip do so because of one of these three things — not because of us.

/ 01

An exec sponsor

One person with decision-making authority who can approve scope, unblock access, and align internal stakeholders. Not a committee.

/ 02

System access

Admin-level access to your Salesforce org, sandbox, and any connected systems — before day one. Security reviews that drag for weeks delay go-live.

/ 03

A 2-hour kickoff

Exec sponsor, RevOps lead, data owner. Two hours up front saves two weeks at the end. We come prepared. You come ready to decide.

§ 05 — Begin

Ready to scope
something?

Tell us what you're working with. We'll tell you whether it's a fit — and if it is, exactly how we'd approach it.

// session30 min
// cost$0
// hostAtul Singh
// outcomescope + fee
Book 30 min →