Enterprise DNA

Instead of ScopeStack

Stop renting ScopeStack. Own your service scoping system.

We build your version around how you estimate delivery work, map your ScopeStack records and run it for you. Start with the service catalogue and agree the history you need brought across.

ScopeStack displays a $12,800 credit example for 200 projects per year. It is a calculator example, with no currency code shown, rather than a quote for your business.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the bill covers

Credit spend around your service estimates

ScopeStack now charges through credits with unlimited users. Its pricing page is the source for the figures below, checked 10 November 2026. Confirm the billing currency and your own usage with the vendor.

calculate

An annual-project calculator

The published example shows 1,600 credits at $8 each, totalling $12,800. Your project volume changes the estimate.

groups

Unlimited users are included

The current credit model does not charge per seat. Ownership is the reason to switch here, rather than a seat-count comparison.

schedule

Credits have an expiry

Purchased credits expire after 12 months. Compare your real scoping pattern with the balance you commit to.

menu_book

Onboarding and advisory

The vendor lists $2,500 per 10-hour block for setup, training and workflow guidance.

link

Connections have their own price

The Integration Engine is listed at $5,000 per integration per year. Include the connections you actually need in a switching review.

description

The work behind each estimate

Services carry effort, rates and reusable wording. ScopeStack also supports approvals and documents. Decide which of these jobs your own version needs to cover.

Your own working records

From a service standard to an approved delivery scope

Service knowledge

Reuse the work you know how to deliver

Keep the catalogue in your own database and inspect the basis of every service estimate.

  • check Parent services and their subservices retain separate effort
  • check Phases and resource labels travel with the work
  • check Imported custom wording stays attached to its service
  • check Missing rates remain unknown until an estimator reviews them

Estimate review

Ask what happens when delivery takes longer

Check effort and margin together, using the assumptions your team actually made.

  • check Combine hours, quantities and reviewed hourly rates
  • check Test extra hours against the current estimate without changing it
  • check Find estimate lines that differ from the current catalogue
  • check Keep each currency separate without hidden conversion

Revision control

Keep the exact scope behind each sign-off

Freeze a revision for review and retain the evidence when the work changes.

  • check Incomplete rates, evidence and acceptance criteria block submission
  • check Unresolved assumptions have a named owner and due date
  • check Different technical and commercial reviewers approve the revision
  • check Revising the work starts a fresh approval cycle

Delivery handover

Prepare the paperwork from the same records

Draft the scope and internal handover with your business name and colours.

  • check Statements of work show the estimate and acceptance criteria
  • check Internal handovers include effort, costs and review evidence
  • check Weekly reports show late work and pending decisions
  • check Selected pricing and contact-retention checks show records to review

Make it yours

Design your own ScopeStack replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from ScopeStack. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your ScopeStack replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your ScopeStack data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real command runs on fictional service estimates. The questions below show the records behind each answer.

forum

Service Scoping for Claude Code

Connected to your own database

Which estimates need attention before we send them for review?

A-101

Item
Confirm usable backup before cutover
Owner
Morgan
Due
2026-11-07
Issue
Unresolved scope assumption

Q-101

Item
Harbour migration
Owner
Morgan
Due
2026-11-08
Issue
Incomplete price or estimate basis

Q-101

Item
Harbour migration
Owner
Morgan
Due
2026-11-08
Issue
Scope overdue

Ask it anything

Ten questions for your own scoping records

These examples combine your service standards, estimate evidence and review rules. Each can be answered from the demo records today.

chat_bubble Which scopes look priced but still have missing cost rates?
chat_bubble Which overdue estimates also have unresolved client assumptions?
chat_bubble How much margin remains after two extra delivery hours?
chat_bubble Which labour lines have drifted from their catalogue standard?
chat_bubble Which submitted revision still lacks a commercial reviewer?
chat_bubble Which service rates have not been reviewed for 90 days?
chat_bubble How much delivery effort sits in each role and phase?
chat_bubble Which estimate lines lack an acceptance criterion or evidence?
chat_bubble Who approved the previous scope revision and on what evidence?
chat_bubble Which client contacts need a retention-purpose review?

Switching

How to switch from ScopeStack

A catalogue-only switch can take one day if the export is usable and rates are reviewed, while project history needs a separate agreed mapping.

  1. 1

    Export your service catalogue

    In ScopeStack, export your Professional Services catalogue as a native CSV, including parent services, subservices and custom wording. If your account does not offer that export, export what it allows, usually CSV or Excel, and check with ScopeStack that the catalogue structure and language fields are included. List project records, signed documents, managed services, products and approvals separately because they need an agreed mapping.

  2. 2

    Load the catalogue

    Bring the CSV into the new system using its ScopeStack catalogue import. Start with the test run, which checks the rows without writing them, then review the results before doing the actual import. Parent services and subservices are matched from their source paths, and custom language is retained. The import covers the professional-services catalogue, not your full project history.

  3. 3

    Review the import results

    Check the test-run results and resolve anything they flag before loading the catalogue. Review every imported service before using it. The documented export does not provide hourly cost and sell rates, so confirm those rates rather than assuming they carried over. Agree separately how to map project history, signed documents and approvals, since the catalogue import does not bring them across.

  4. 4

    Run both systems briefly

    Keep ScopeStack available during a short overlap. Prepare one real estimate in the new system and reconcile it against the matching estimate in ScopeStack before relying on the new records. Use this check to confirm the imported service structure and reviewed rates, and to verify any other records covered by your agreed mapping. The README recommends keeping the old system until one real estimate reconciles.

  5. 5

    Switch off ScopeStack

    Once the real estimate reconciles, move your team to the new system and switch off ScopeStack. Before you do, confirm what project history, signed documents and approvals you agreed to bring across, and retain any records that are staying outside the new system. Protect exports, drafts and backups as business records. The catalogue import alone does not preserve complete project history or existing approvals.

construction

Where the real effort goes

Most of the work is not loading the catalogue. It is mapping your own fields and rules, reviewing hourly rates because the documented export does not include them, and deciding which history to bring. Project lists, signed documents and approvals need an agreed mapping, rather than a direct catalogue import. If Enterprise DNA installs and runs it for you, they do this mapping and bring across the agreed ScopeStack records.

Not ready for a call?

Get your ScopeStack switch plan by email

We will send you the step-by-step plan for moving your business off ScopeStack, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version or have us build yours

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and review the sample scopes
  3. 3 Export your ScopeStack service CSV and test the import before writing
  4. 4 Review rates and wording, reconcile one estimate and set your private backups
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your service definitions, estimate fields and review rules
  • check Your ScopeStack exports mapped and reconciled against the source
  • check A web front end and connections designed for the team using it
  • check A different technical foundation when your business needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with reviewed access and private backups
  • check Service imports, weekly reviews and document preparation operated for you
  • check Rules and reports maintained as your delivery work changes
  • check Run through Omni by Enterprise DNA alongside your other systems
Book a 30-minute review

Questions

Instead of ScopeStack, answered

Does the free version replace every part of ScopeStack? expand_more

It covers professional-service labour estimates, reusable service work breakdowns, assumptions and revision review. Start there. We scope managed services, products, signatures, screens and business-system connections around what your team needs in its custom version.

Can we bring our service library and project history across? expand_more

The free version imports the documented professional-service CSV, including parent services, subservices and custom wording. Hourly rates need review before use. Project history, signed documents and existing approvals need an agreed mapping. We reconcile those records with you before a full switch.

Will our old approvals survive a changed estimate? expand_more

Previous approvals remain in the history beside the submitted snapshot. A revised estimate starts a new review cycle. The technical and commercial reviewers must differ from each other and from the recorded scope owner. Shared access needs individual identity and permission controls.

How do we compare the cost fairly? expand_more

Compare your actual ScopeStack usage and connections with running your own system. The vendor includes unlimited users, so this is not a per-seat saving claim. Hosting, an agent subscription and maintenance remain operating costs. Enterprise DNA agrees one setup fee and a retainer for the version we build and run.

Can we use our own approval rules and branded documents? expand_more

Yes. Change your margin policy, acceptance fields and service wording, then generate the statement of work and delivery handover in your brand. The free version creates drafts for a person to review. We build the screens and approval connections your team needs.

Bring one service estimate to a 30-minute call with Sam

Show how your team builds a scope, what reviewers need and which ScopeStack records you want to keep. We will work through the version Enterprise DNA can build and run for you.

Book a 30-minute call Get the free version

Service Scoping for Claude Code is free and open source, published by Enterprise DNA.

Done paying for ScopeStack?

Get your version built