Revenue Cloud Solution Architect — Quote-to-Cash

SaaScend; United States; Remote; USD 120,000 - 190,000; Full time

Benefits offered by this job

Paid annual company retreat

Remote-first culture

Autonomy and skill development

Job summary

SaaScend in the United States is seeking a hands-on Salesforce RevOps lead to architect and deliver revenue operations for complex CPQ estates.

You’ll design catalog architecture, pricing procedures, and integration with ERP and billing systems, while guiding admins and developers through implementation, QA, and go-live. Remote-first with flexible collaboration and client-facing accountability.

Qualifications

• End-to-end fluency in quote-to-cash from pricing through renewal.
• Experience with CPQ estates, discount governance and revenue recognition.
• Hands-on design and delivery of Salesforce integrations and data migration.

Responsibilities

• Run discovery with revenue leadership and IT to map the real quote-to-cash process.
• Design solution architecture including pricing, configuration rules, and lifecycle.
• Write technical specs: object models, field definitions, pricing logic.
• Own deployments, UAT, and go-live with client outcomes.

Skills

Salesforce CPQ

Revenue Cloud

Apex

SFDX

Tools

Salesforce CPQ

Revenue Cloud

Apex

SFDX

NetSuite

SAP

Job description

We’re a Salesforce RevOps partner. Our clients arrive with the same problem wearing different clothes: revenue leaks somewhere between “the rep builds a quote” and “finance recognizes the cash,” and nobody in the business can draw the whole picture.

Your job is to draw it, spec it precisely enough for our admin and developer team to build it, and own the project end to end. You’ll get your hands on the keyboard for parts of it.

What makes this different

We run an AI-assisted delivery pipeline. Approved design documents become a task manifest executed by a sequenced set of build agents — data model, permissions, automation, page it produces, and build the parts it shouldn’t touch.

Two consequences worth being blunt about:

• Your spec is the build input, not a document that gets filed. Ambiguity doesn’t get quietly resolved by a developer at 11pm — it surfaces as a failed QA gate with your name on it.
• The repetitive half of configuration is gone. You won’t spend your week hand-cranking field creation and permission sets. You’ll spend it on discovery, architecture, clients, and the genuinely hard build work.

What you’ll do

• Run discovery with revenue leadership, sales ops, finance and IT — mapping the real quote-to-cash process, not the one in the process document
• Design the solution: catalog and product architecture, pricing and discounting, configuration rules, quote and order lifecycle, amendments and renewals, billing and ERP handoff, approvals and controls
• Write the technical specification — object model, field definitions, pricing procedure logic, detail that survives contact with a build
• Make the buy-vs-build-vs-don’t calls: standard RCA capability, declarative extension, CML, Apex prehook, or “you don’t need this, and here’s what it would have cost you”
• Get hands in the org when it matters — pricing procedures, expression sets and decision tables, configuration rules, flows, data migration, deployment. Most build work sits with our admins and developers; we want someone who could do it themselves
• Own the client and the outcome: scope conversations, expectation management, the awkward mid-project conversation about what’s changed, and delivery through UAT and go-live
• Support pre-sales — scoping calls, solution shaping, estimates you’re willing to be held to

What you need

Quote-to-cash, as a business process. End-to-end fluency from pricing strategy through quote, approval, order, invoice, cash and renewal. Subscription mechanics — amendments, co-terming, proration, mid-term changes, uplift. Usage-based and hybrid models. And a feel for where finance and sales collide: discount governance, approval thresholds, revenue recognition Revenue Cloud Advanced.

Product Catalog Management — classifications, attributes, selling models, bundle architecture and the constraints that come with it. Salesforce Pricing — price lists, adjustment schedules and matrices, pricing procedures, context definitions — with a clear sense of where the declarative model stops and an Apex prehook starts. Product Configurator and constraint modeling. The quote-to-order lifecycle and the packaged flows behind it. Real working depth in at least two of: Dynamic Revenue Orchestrator, Usage Management, Billing, Contracts/CLM, Approvals.

The platform underneath. Data model, flows, sharing and security, automation design — including knowing when Flow is right and when Apex is. Source-driven development: SFDX, metadata deployment, sandbox strategy, release discipline. Data migration and load.

Legacy and integration context. Salesforce CPQ experience is genuinely valuable — much of our pipeline is CPQ estates deciding what to do next, and knowing what doesn’t map cleanly is worth more than knowing what does. Plus integration literacy: ERP (NetSuite, SAP, JDE and similar), tax engines, payment providers, and the middleware between.

The consulting half. You can hold a room containing a skeptical CFO and an over-optimistic sales leader, and leave with a decision. You ask the question behind the question — when a client says “we need a custom field for this,” you find out why before you agree. You write clearly: short sentences, specific nouns, no hedging where a decision is required. You deliver unwelcome news early rather than pleasant news late.

Nice to have

Nice to have: Salesforce certifications (CPQ Specialist, Revenue Cloud, Platform App Builder, Admin); small consultancy or Salesforce partner experience; manufacturing, B2B distribution, SaaS or professional services depth; any prior experience directing AI coding tools on real delivery work.

Not for you if

• You want a narrow lane with someone else owning the client
• You’ve only ever worked from specs someone else wrote you don’t get hands on with the tools you design for, and want to keep it that way
• You need a large team behind you to make progress
• You’d rather sell than deliver

How we work

Small, highly collaborative, remote-first. No layers between you and the client. You own engagements end to end rather than a slice of one. We’re deliberately building an AI-assisted delivery practice, which means our billable hours go into thinking and client work instead of repetitive configuration.

• Paid annual company retreat
• Trust-based culture with real autonomy
• Genuine investment in building your skills