Enterprise DNA

Instead of Scoro

Stop renting Scoro. Own your agency operations.

We build your version around how your agency prices and delivers work, map your Scoro records and run it for you through Omni by Enterprise DNA. Start with the operating decisions your team makes every week.

Scoro displays End-to-end at AUD 85.50 per user per month. Your bill depends on your users, chosen apps and extras.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

One agency, a growing software bill

Scoro combines work, delivery and finance. Compare the parts you use with a system built around your own operating rules.

groups

A price for each user

The displayed End-to-end price is AUD 85.50 per user per month. The number of people using it affects the recurring bill.

view_module

Apps chosen around the workflow

Scoro prices combinations of core apps. Decide which parts of your workflow belong in your own system.

assignment

Project and retainer oversight

Delivery planning and retainer management are part of Scoro. Your version starts with the period, allowance and scope you agreed with each client.

payments

Commercial reporting

Scoro includes financial reporting. In your version, you can inspect and change the calculations behind the weekly contribution review.

extension

Extras beyond the core

Scoro lists extras such as its customer portal and change request log as paid add-ons. Agree which of these your agency needs before choosing the scope of your build.

move_up

The work of moving records

Scoro work reports export to CSV. Match the exported work to your projects and people, then reconcile it before switching.

Your weekly operating decisions

Keep the records. Set your own rules.

Project contribution

See the cost still to come

A fee can look healthy until the unfinished work is counted. Put recorded labour, expenses and the remaining task estimate beside that fee.

  • check Agreed fees include approved scope changes only
  • check Historical time keeps the rate recorded with it
  • check Remaining task effort uses the assigned person's current cost rate
  • check Contribution stays separate by currency, before tax and overhead

Scope control

Get extra work agreed in writing

Give requested changes their own queue. A request does not increase the fee just because someone typed it into the system.

  • check Track each request with its fee and hours
  • check Require an evidence reference and a different named reviewer to approve it
  • check Keep pending fees outside the agreed budget
  • check Draft a scope approval request from the current record

Retainers and people

Check the allowance and the week ahead

Bring the client promise and the staff plan to the same meeting. See exhausted allowances alongside people booked beyond their available time.

  • check Keep each retainer period separate
  • check Refuse completed work outside its retainer period
  • check Subtract recorded leave before calculating free capacity
  • check Replace weekly allocations and regenerate the meeting report

Billing preparation

Show what is ready for review

Prepare the evidence behind billing without treating every logged hour as a new invoice. Keep the accounting decision with your team.

  • check Separate reviewed billable work from entries still needing approval
  • check Show unbilled effort by project and currency
  • check Record an external invoice reference only with supporting evidence
  • check Produce project status sheets, retainer statements and billing worksheets in your branding

Make it yours

Design your own Scoro replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Scoro 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 Scoro data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Agency Operations for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Agency Operations for Claude Code

Connected to your own database

What is left from each fee after the work still to come?

HAR-01

Rrency ag
NZD
Reed_fee la
3000.00
Bor_cost ex
1650.00
Pense_cost fo
0
Recast_cost fo
1800.00
Recast_contribution pe
1200.00
Nding_fee
0

HAR-02

Rrency ag
AUD
Reed_fee la
9000.00
Bor_cost ex
200.00
Pense_cost fo
0
Recast_cost fo
1200.00
Recast_contribution pe
7800.00
Nding_fee
0

KAU-01

Rrency ag
NZD
Reed_fee la
5000.00
Bor_cost ex
2550.00
Pense_cost fo
900.00
Recast_cost fo
6150.00
Recast_contribution pe
-1150.00
Nding_fee
1200.00

Ask it anything

Ten questions to bring to your weekly meeting

These are working questions the free version answers today. Scoro also offers detailed reporting and conversational access. Owning this version lets you change the records and calculations to fit your agency.

chat_bubble Which projects combine late tasks and unapproved scope?
chat_bubble What contribution remains after recorded costs and estimated remaining work?
chat_bubble How much requested scope is still outside the agreed fee?
chat_bubble Which budgets are exceeded by completed and remaining hours together?
chat_bubble Which retainer periods have used more than their allowance?
chat_bubble Who is overbooked after their recorded leave is deducted?
chat_bubble What reviewed work has no accounting invoice reference?
chat_bubble Which expenses have no source-document reference?
chat_bubble Which active projects have had no recorded work for fourteen days?
chat_bubble Who changed a project's scope or delivery records, and what was logged?

Switching

How to switch from Scoro

A move usually involves exporting completed work, mapping it to your projects and people, checking the imported records, and deciding what history needs separate migration.

  1. 1

    Export completed work

    Use Scoro's work-report CSV export to get the completed work you want to bring across. Export the records needed to match work to your configured projects and people, and include stable record identifiers and rate information where available. Export options can depend on your account, so check with Scoro if you cannot find the work-report export or the fields you need.

  2. 2

    Map and load the records

    Configure your clients, projects, people and rates before loading the work. Map the columns in the Scoro report to the fields used by the new database. The supported import brings completed work into configured projects and people, not your whole account. If your import process offers a test run, use it before loading the full report.

  3. 3

    Review import warnings

    Check every warning or item the import marks for review. Confirm that records match the right projects and people, and check rates and stable record identifiers before relying on the imported history. Resolve mapping problems and reconcile the records that need attention. The import does not silently recreate the rest of your Scoro account.

  4. 4

    Run both systems together

    Keep Scoro and the new database in use side by side for a short period. Compare completed work, project and people matches, rates, and the reports your team relies on. Record anything that does not reconcile, correct the mapping or agree how to handle it, and confirm the new process is usable before you stop entering work in Scoro.

  5. 5

    Switch off Scoro

    Switch off Scoro only after you have checked the imported work and agreed how your team will use the new system. Before you stop using Scoro, decide how you will retain access to records that were not brought across. Approvals, attachments and accounting history need separate migration work, as do other records outside the work-report export.

construction

Where the real effort goes

Most of the work is mapping your fields, rates and operating rules, then deciding how much history to bring across. Completed work can come through the mapped work-report import. Budgets, tasks, invoices, approvals, attachments and accounting history need separate migration work. If you have Enterprise DNA run the system, they scope and reconcile the migration with you.

Not ready for a call?

Get your Scoro switch plan by email

We will send you the step-by-step plan for moving your business off Scoro, 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

Choose how much you want to run yourself

Open source

Do it yourself

Free

  1. 1 Download Agency Operations for Claude Code from GitHub
  2. 2 Run npm run demo and open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for the weekly review and try the fictional agency records
  4. 4 Configure your projects and rates, map your Scoro CSV work report and test the import
Get it on GitHub

Built around your business

We customise it

Your version, scoped with you

  • check Your project fields, scope approvals and retainer rules
  • check Your Scoro records mapped and reconciled with your team
  • check A web front end or different stack when your team needs it
  • check A setup fee agreed around the work, with ongoing support scoped separately
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated inside Omni by Enterprise DNA
  • check Connected to the accounting and other systems agreed in your scope
  • check Your records, backups and operating checks managed for you
  • check Reports and workflows maintained as your agency changes
Book a discovery call

Questions

Instead of Scoro, answered

Scoro already reports on project profit. Why change? expand_more

Scoro does offer financial reporting and conversational access. The reason to change is ownership and fit: your own database, your own definitions of scope and contribution, and reports you can change. Compare the workflows you actually use before deciding.

Can we bring our Scoro history across? expand_more

The free version imports completed work from a mapped work-report export into configured projects and people. Check the rates and stable record identifiers first. Approvals, attachments and accounting history need separate migration work. Enterprise DNA scopes and reconciles those records with you.

Will the retainer report automatically bill extra hours? expand_more

No. It shows the period allowance and recorded usage. A fixed fee or retainer can have different billing terms from the value of the hours spent. Your team reviews the contract and raises the invoice in its accounting system.

Can the team have a browser workspace and a timer? expand_more

Enterprise DNA can build the web workspace and time-entry connections your agency needs as part of your version. Agree those requirements alongside staff permissions and the way people plan their week.

What do we pay Enterprise DNA, and who owns the records? expand_more

You own the database and the open-source base. We agree the setup fee around your migration and customisation, then a retainer when we operate it for you. Hosting and agent usage also have costs. There is no fixed Enterprise DNA price on this page.

Bring the Scoro bill and the weekly meeting agenda

Spend 30 minutes with Sam. Show him the workflows your agency uses, the records you need to keep and the decisions your reports leave open. Together you can scope the version your business needs.

Agency Operations for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Scoro?

Get your version built