Engagements and pricing

Fixed-fee engagements matched to the size of the problem.

Rooted Rocket offers three separate project sizes. They are not required stages and their prices are not added together.

Three clear project options

Choose by the size of the problem.

Each engagement produces a working result. The difference is the operating boundary: one improvement, one core function or one system spanning multiple departments.

Scope, communication and payment

Know exactly what you are buying.

Before signing, the proposal defines the result, timeline, meeting count, client responsibilities, exclusions and acceptance standard.

01 · Focused Improvement Sprint

One contained improvement.

$10,000

Four weeks

Payment schedule100% due at signingNo ongoing retainer is required.
Discuss a Focused Sprint

Good fit for

  • Automating one repetitive workflow or recurring report
  • Implementing one intake, routing or approval system
  • Cleaning up one internal process with a clear start and finish
  • Improving one dashboard or configuring one existing tool

What is included

  • Confirmed problem, scope boundary and success measure
  • Focused discovery and current-state review
  • Approved future-state workflow or tool design
  • In-scope implementation, testing and documentation
  • Final walkthrough, training and handoff

Communication commitment

  • One 60-minute kickoff meeting
  • One 60-minute progress meeting each week
  • Up to two stakeholder or working sessions
  • One final walkthrough and handoff meeting
  • Weekly written progress updates
  • Email responses within one business day

Maximum: eight scheduled meetings.

02 · Core Function Rebuild

One major business function.

$15,000 to $35,000

Eight to twelve weeks

Payment schedule50% at signing · 25% after solution approval · 25% before final handoffNo ongoing retainer is required.
Discuss a Core Rebuild

Good fit for

  • Rebuilding how the sales department operates
  • Repairing a CRM shared by sales and customer success
  • Redesigning customer onboarding from contract through implementation
  • Rebuilding forecasting, pipeline management and sales reporting

What is included

  • Confirmed function boundary and success measures
  • Information gathering with leaders and everyday users
  • Current-state map, constraint diagnosis and future-state design
  • Defined workflows, ownership, decision rights, data and tool behavior
  • In-scope configuration, automation or integration work
  • Testing, documentation, training and final handoff

Communication commitment

  • One 60-minute kickoff meeting
  • One 60-minute progress meeting each week
  • Up to six stakeholder, design or decision meetings
  • One solution-approval meeting
  • Up to two training and handoff meetings
  • Weekly written updates and one-business-day email response

The exact meeting count is established in writing before work begins.

03 · Cross-Functional System Build

One system across multiple departments.

$40,000 to $60,000

Twelve to sixteen weeks

Payment schedule40% at signing · 20% after solution approval · 20% at the implementation midpoint · 20% before final handoffNo ongoing retainer is required.
Discuss a Cross-Functional Build

Good fit for

  • Connecting marketing, sales, implementation and customer success
  • Building one complete lead-to-customer operating system
  • Connecting sales forecasts with delivery capacity and finance
  • Creating shared definitions, reporting, ownership and automation across departments

What is included

  • Confirmed cross-functional boundary, result and acceptance measures
  • Information gathering across approved departments and user roles
  • End-to-end current-state map and future-state architecture
  • Shared definitions, ownership, decision rights, workflow and exception rules
  • In-scope configuration, reporting, routing, automation and integrations
  • Cross-functional testing, training, documentation and handoff

Communication commitment

  • One 60-minute executive kickoff meeting
  • One 60-minute leadership progress meeting each week
  • Up to ten cross-functional working or decision meetings
  • Up to three training and adoption sessions
  • One final executive acceptance and handoff meeting
  • Weekly written updates and one-business-day email response

Departments, participants and the exact meeting count are established in writing before work begins.

Clear boundaries protect the result

No vague promises. No surprise scope.

Rooted Rocket defines what “done” means before the project starts.

ScopeEvery proposal defines the result, system boundary, sponsor, departments, tools, deliverables, exclusions and acceptance tests.
UpdatesEvery client receives a weekly written update covering what was completed, what happens next, upcoming decisions and risks to timing.
MeetingsMeeting purpose, frequency and maximum allowance are written into the engagement plan. Unlimited calls and unrelated requests are not included.
Client roleThe client names one decision-maker, provides required access and information, and returns feedback within the agreed timeframe.
Access and dataRooted Rocket requests the minimum access required for the approved scope. Sensitive systems, data handling, security expectations and removal of access are agreed before discovery or implementation.
Third-party costsSoftware licenses, usage fees, implementation partners and other third-party costs are excluded unless the signed proposal explicitly includes them.
ChangesAdditional departments, systems, deliverables or meetings require written approval on price and timing before work begins.
HandoffCompletion includes the implemented system, supporting documentation, training and a defined handoff. Continued support is scoped separately.
Engagements and pricing

You do not need to choose an option before the first conversation.

Describe the visible problem. Rooted Rocket will recommend the smallest scope capable of producing a coherent working result.