Enterprise DNA

Instead of Command Alkon

Stop renting Command Alkon. Own your ready-mix system.

We build your version around how your plants take orders, load trucks and track test results, bring your Command Alkon customer, project, mix and truck lists across, and run it for you.

Command Alkon does not publish its prices. Dispatch, batching, quality and billing are quoted as separate subscriptions, with plant control and truck tracking connections priced on top. Bring your invoice and we compare it line by line.

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

The Command Alkon bill

A quote for each module, then the connections

There is no price list to compare against. These are the parts a ready-mix producer is usually quoted for. Check which ones are on your own invoice.

local_shipping

Dispatch

Order entry, scheduling, ticketing and delivery tracking, sold as the core subscription for each operation.

factory

Batching

Batch panel software at each plant, often quoted with the dispatch package as a bundle.

science

Quality control

Mix designs, samples and strength results, sold as its own product next to dispatch.

receipt_long

Billing and reporting

Invoicing from tickets and the performance reporting on top, part of the quote-to-cash package.

cable

Plant and truck connections

Linking batch controllers and truck tracking to dispatch is commonly scoped and priced separately from the subscription.

support_agent

Implementation and support

Setup, training and ongoing support sit alongside the licence. Ask what yours costs over three years, not one.

Your version

The records a concrete plant runs on, kept where you can ask about them

Pours

Know tomorrow before the phone rings

Every booked pour by date and start time, with the loads it will take and the customer's account status beside it.

  • check Tomorrow's pours in start order, with pump jobs marked
  • check Unconfirmed pours flagged the day before
  • check A customer on credit hold cannot have a load batched
  • check Ordered, sent, returned and placed volume for every order

Dockets

Dockets that tell you what happened on site

Each load keeps its batch, arrival and discharge times, the signature and any water added. A printed docket cannot be edited.

  • check Loads that took longer than your limit from batching to discharge
  • check Water added on site with nobody signing for it
  • check Dockets with no signature or missing times
  • check Delivered loads with no invoice yet, oldest first

Testing

Sampling and results the engineer can trust

Samples link to the load they came from, results link to the lab report, and the plant's sampling rule is checked against what it produced.

  • check Which plant is short of samples for its production
  • check Which 7 and 28 day results the lab still owes
  • check Results under grade, and results within 3 MPa of it
  • check Mean and lowest 28 day strength for every mix

Your questions

Ask what the reports never covered

Start with the checks supplied, then ask your own questions in plain English against the same records.

  • check Which customers send back the most concrete, and on which mixes
  • check How long each truck spent on site on a given day
  • check Pour confirmations and results letters drafted for review
  • check Dockets, test results and statements printed in your own brand

Make it yours

Design your own Command Alkon replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Command Alkon 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 Command Alkon 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 Ready-Mix for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Ready-Mix for Claude Code

Connected to your own database

What needs chasing before tomorrow's pours?

docket not invoiced

Record
RM100-10
Due
2026-09-01
Detail
Harbour Civil, 7.00 m3

docket not signed

Record
RM104-04
Due
2026-09-26
Detail
Harbour Civil

docket not invoiced

Record
RM105-01
Due
2026-10-21
Detail
Harbour Builders, 7.00 m3

docket not invoiced

Record
RM105-02
Due
2026-10-21
Detail
Harbour Builders, 7.00 m3

docket not invoiced

Record
RM105-03
Due
2026-10-21
Detail
Harbour Builders, 7.00 m3

docket not signed

Record
RM105-03
Due
2026-10-21
Detail
Harbour Builders

28 day result due

Record
S105
Due
2026-10-24
Detail
S40-19-80 for Harbour Civil

7 day result due

Record
S108
Due
2026-10-28
Detail
N25-19-100 for Harbour Builders

past pour still open

Record
RM103
Due
2026-10-30
Detail
4.00 m3 not sent

pour without confirmation

Record
RM101
Due
2026-11-01
Detail
Harbour Builders, Mangawhai townhouses

pour booked on credit hold

Record
RM102
Due
2026-11-02
Detail
Ridgeline Homes

Ask it anything

Ten questions for your own plant records

Each one runs against the fictional demo today. Ask the same of your own records once they are in.

chat_bubble Which pours tomorrow are still not confirmed, and who is on credit hold?
chat_bubble Which plant is short of test samples for what it produced in the last 90 days?
chat_bubble Which 28 day results does the lab still owe us, and how late are they?
chat_bubble Which mixes came in under grade or within 3 MPa of it?
chat_bubble Which loads took more than 90 minutes from batching to discharge?
chat_bubble Where was water added on site with nobody signing for it?
chat_bubble Which customers send back the most concrete, and on which mixes?
chat_bubble How long did each truck spend on site on a given day?
chat_bubble Which delivered loads have no invoice yet?
chat_bubble How is each mix performing at 28 days against its grade?

Switching

How to switch from Command Alkon

A move usually involves exporting your core lists, mapping your headings, checking the records, and running both systems side by side before you switch.

  1. 1

    Export your core lists

    Export your customer, project, mix and truck lists from Command Alkon list reports as CSV files. Report headings vary between installs, so keep the original exports for mapping. Past orders and tickets need separate checking against your invoices. Decide which history you want to bring across, and agree that before loading it.

  2. 2

    Test the import

    Load the customer, project, mix and truck lists using the import's test run first. This gives you a chance to map your report headings before bringing the records into the new database. Compare the counts from the test with the lists you exported, and make sure the mapping reflects the names and fields your business uses.

  3. 3

    Review what it flags

    Review anything the test run flags and resolve the mapping issues before loading the records. Check the imported customer, project, mix and truck counts against your exports. For past orders and tickets, compare the records with your invoices and confirm which history you agreed to bring across. Do not treat the list import as a check of historical order data.

  4. 4

    Run both systems briefly

    Keep Command Alkon running while you use the new database for a short period. Compare the records and the work your team handles in each system, including orders, dockets and test results. Use this time to catch missing information or rules that need changing before the new system becomes the one your team relies on.

  5. 5

    Switch off Command Alkon

    Once you have checked the records and your team is ready to work from the new system, plan the switch with the people who use it. Confirm what will happen to any Command Alkon functions you still depend on, including live dispatch, batch control or truck tracking connections. Only switch off Command Alkon when those dependencies are addressed.

construction

Where the real effort goes

The main work is usually mapping your own report headings, fields and business rules, then deciding how much past order and ticket history to bring across and checking it against invoices. The core customer, project, mix and truck lists have a test run. If you have Enterprise DNA install and run it for you, they handle the migration and mapping work.

Not ready for a call?

Get your Command Alkon switch plan by email

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

Pick who builds it and who runs it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, then run npm install, npm test and npm run demo
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor and type /pour-day
  3. 3 Run /import with a dry run on your Command Alkon list exports
  4. 4 Set your sampling rates and discharge limit with /customise, then point it at your own database
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your mixes, pricing, cartage and short load charges
  • check Your Command Alkon customers, projects, mixes and trucks brought across, with the order history we agree
  • check A dispatch board and driver screens on the web if your team wants them
  • check Connections to your batch panel, truck tracking and accounts where they matter
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 Your dispatch office and plant engineer asking it questions in plain English
  • check Backups, access and changes handled with your team
  • check A morning pour plan and a Monday review written for you
Book a call with Sam

Questions

Instead of Command Alkon, answered

Can this replace the dispatch board my team watches all day? expand_more

The free version keeps the pour schedule, loads and dockets, and answers questions about them. It does not show trucks moving on a live board. If your dispatchers need one, Enterprise DNA builds it on top of your records as part of your version.

What about our batch panels and truck tracking? expand_more

The free version records batch, arrival and discharge times when someone enters them. Connecting your batch controllers and truck tracking so the times arrive on their own is custom work we scope with you, plant by plant.

How do we get our records out of Command Alkon? expand_more

Customer, project, mix and truck lists come across from spreadsheet exports in one step, with a test run first. Report headings differ between installs, so we map yours. Past orders and tickets need checking against your invoices, and we bring across the history you agree.

Does it keep us right with our plant audit and the concrete standards? expand_more

It checks your records: samples against production, results that are late or under grade, dockets missing times or signatures. Your plant engineer still runs the strength assessment and your audit. Every check names the standard it comes from and the limits are yours to set.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for running and changing it. There are no seats or plant licences in the free version. Hosting and agent subscriptions have their own costs, and we put the full cost next to your Command Alkon invoice before you decide.

Bring your Command Alkon invoice and tomorrow's pour sheet

Spend 30 minutes with Sam. Show us what you pay, how a pour goes from the phone to the truck, and what the plant engineer chases every week. We will show you what your own version looks like and what it takes to run.

Ready-Mix for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Command Alkon?

Get your version built