← Back to blog

You Don't Need a CPQ Project to Price an Engagement

A prospect asks for a number by Friday. A senior consultant opens last quarter's spreadsheet, copies the tab, renames it, and starts adjusting role splits by feel. By Thursday night there's a margin calculation and a total. Nobody else at the firm could explain how that total was reached, and nobody will check it until the project runs over.

If you run a consulting practice, an agency, or an IT services team, you know this routine. You also know the obvious answer the market offers: buy a CPQ tool.

The CPQ answer was built for a different business

Configure-price-quote software grew up selling physical products. A manufacturer has a catalog, and each item has options, compatibility rules, and a price. The hard problem is making sure a sales rep can't quote a combination the factory can't build. CPQ tools are very good at that, and their rule engines are deep because that problem is deep.

A services firm doesn't have a catalog. It has a delivery plan. What you're pricing is a set of activities, the roles that do them, and the hours each role spends. The hard problem isn't invalid combinations. It's the judgment that goes into sizing the work, and that judgment usually lives with two or three senior people.

Several CPQ vendors now market to services firms, usually by treating labor as one more pricing model inside a product configurator. That can work if you already run on the CRM or ERP the tool plugs into and you have a partner ready to implement it. In our experience those rollouts are measured in quarters, not weeks. They need an admin to maintain the rules and an implementation budget before you price your first deal.

Most firms we talk to aren't in that position. They don't have a CPQ today. They have a spreadsheet that does a margin calculation, and nothing more.

What the spreadsheet actually costs

The spreadsheet itself is free. Two things make it expensive.

Your most expensive people do the estimating. An estimate takes hours to days when you build it by hand. Those are hours your billable consultants spend on work nobody pays for, and they come out of the same week as client delivery.

The knowledge never becomes an asset. When the estimate lives in one person's spreadsheet logic, you can't measure it, compare it, or improve it. Two people scope the same deal and land in different places, and there's no shared basis to say which one is right. When one of them leaves, the firm's estimating judgment walks out too.

Neither of those problems is solved by a more powerful rule engine. They're solved by moving the estimating logic out of individual heads and into a system the whole firm uses.

Time to value is the real requirement

If the goal is a defensible, priced estimate this quarter, the tool has to meet a few conditions.

• You can start without an implementation project. Sign up, set up your organization, and configure it yourself.
• It speaks your model. Roles, rates, and hours per activity, not SKUs with options.
• Your methodology is the configuration. Your rate cards, your roles, your sizing approach, and your practice's way of working, not a vendor's generic template.
• The math is the same every time. The same inputs produce the same number, so two people can scope a deal and compare their work honestly.
• You can explore options without rebuilding the estimate. Clients ask "what if we phase it?" and you should be able to answer without starting over.

How we built Scope around that

We're consultants and IT executives, and we built JungleOS Scope because we were the firm with the spreadsheet. It's a guided estimation engine for services work, and it is self-serve: you sign up and configure it yourself.

Here's what it does today:

• Each practice area carries its own methodology. Rate cards, role rates, skills, question banks, testing types, development sizing, passthroughs, and project types are all configurable. That's where your firm's judgment gets written down once instead of rebuilt on every deal.
• Estimates are deterministic. The engine is plain math and logic, with no AI guessing at the number. Each estimate reads from a frozen snapshot of your configuration, so an estimate in progress can't shift when someone edits a rate card.
• Role totals reconcile to the project total. Rounding is handled so the role hours add up exactly, without the one-hour drift that makes a client ask what else is off.
• Each deal can hold multiple scenarios. You can fork and version them to explore different approaches without losing the original.
• The estimate exports to Excel. Take it into whatever proposal process you already have.

There's no rule engine to maintain and no partner to hire before you can price your first deal.

Where to start

Pick one recent deal you estimated in a spreadsheet. Set up the roles and rates you actually used, run it through a guided estimate, and compare the number with what you sent the client. If the two match, you've captured your judgment in a system. If they don't, you've found out where it was living.

Either way, you'll know more than another spreadsheet tab would tell you.