- Choose software by following a job through the shop
Turn missing job handoffs into clear requirements and a practical vendor demonstration.
- Six operating measures worth defining before building a dashboard
Six suggested measures, with the definitions that make a weekly review useful.
- Multi-location software: test the branch, the transfer, and the exception
Evaluate customer records, material transfers, and local authority across branches.
- A decade of countertop shop technology
Selected developments from 2016–2025, with a 2026 update, examined through dated records and original sources.
- Moraware in 2002: office software grew from a shop's coordination problem
Moraware's own origin account begins in 2002 and describes early software addressing estimating, scheduling, and inventory for countertop businesses. Its later product names belong to subsequent stages of that history.
- RemnantSwap in 2010: availability requires more than a listing
Moraware's retrospective account dates RemnantSwap to 2010 and describes it as a service for fabricators buying and selling stone remnants.
- CounterGo in 2012: separating a drawing-and-quoting product from the company timeline
Moraware's origin account dates CounterGo to 2012. The company's earlier beginnings do not make CounterGo a 2002 product.
- Systemize in 2018: a later product name within a longer software history
Moraware's retrospective account places the release of Systemize at the beginning of 2018. This is distinct from the company's 2002 origin and CounterGo's later development.
- Reference post: what information belongs in a countertop quote comparison?
Moraware presents CounterGo as drawing and estimating software. Comparing quoting tools becomes easier when the shop first decides what a complete quote must communicate.
- Reference post: five questions to settle before introducing shop labels
Horus describes Dashboard functions involving job information, labels, and packing lists. Before discussing label hardware or appearance, a shop should agree on what the label is supposed to help an employee identify.
- Reference post: what does available inventory mean in your shop?
Stone Profit Systems lists inventory, holds, and multiple-location functions in its ERP offering. Those categories raise a basic question for any shop evaluating inventory software: which material should staff describe as available?
- Field Notes: Software, surfaces and events (2010–2014)
A web reading list covering 2010–2014: 3 articles from this publication.
- Field Notes: The early digital shop (2000–2004)
A web reading list covering 2000–2004: 1 articles from this publication.
- Field Notes: Software, surfaces and events (2010–2014)
A web reading list covering 2010–2014: 2 articles from this publication.
- Field Notes: New generations, familiar decisions (2015–2019)
A web reading list covering 2015–2019: 1 articles from this publication.
- Moraware at TISE 2026: scanners and getting more from existing tools
The software supplier’s recap offers a useful view of inventory digitization and implementation questions.
- How to choose countertop fabrication software: a shop-first comparison
Choose software by the work it must carry from one person to the next. Establish required handoffs, demonstrate exceptions, and compare the complete operating cost before choosing a platform.
- SlabOS, Moraware and ActionFlow: compare the job handoff before the feature count
Compare SlabOS’s shared drawing and job workflow, Moraware’s separate products, and ActionFlow’s packages using the same quote, schedule and slab-allocation test.
- What countertop software really costs: a worksheet for the complete change
Compare subscription charges, setup, migration and staff time together. Keep cash savings separate from time released, and test conservative assumptions before using a payback figure.
- Slab and remnant inventory: what a dependable software record must contain
A useful inventory system connects physical identity, location, availability and job allocation. Test receiving, reservation changes and remnant creation before relying on a digital stock count.
- Moving countertop shop data: an acceptance plan before the cutover
Approve a migration by reconciling records, relationships and usable files. Preserve the source export, test a representative subset, and define rollback responsibility before moving live work.
- Opening a second countertop location: the records that must work across both
Define which decisions belong to each branch and which are shared. Test inter-branch jobs, material transfers, access and reporting before making the second location dependent on the same systems.
- CounterGo and SlabOS: follow a price change through the approved quote
A useful quoting demonstration should end with an approved revision that the next employee can identify.
- ActionFlow and SlabOS: compare package scope against the required job
ActionFlow presents multiple subscription packages and additional capabilities.
- StoneAPP and SlabOS: evaluate separately scheduled project parts
StoneGrid presents StoneAPP as business management software for fabricators.
- SlabOS evaluation: take one practice job through import, revision and export
SlabOS describes a platform spanning drawing, quoting, inventory, nesting, scheduling and field work.
- SlabWise and SlabOS: compare DXF review and production release
SlabWise describes DXF translation and fabrication workflow capabilities.
- Horus and SlabOS: compare slab records and layout boundaries
D2 Technology describes Horus as its related stone-software business, with tools for slab tracking, vein matching, estimates and 3D layouts.
- Inventory software demo: test a correction, not only a new slab
Receiving a new slab is the tidy part of an inventory demonstration.
- Role permissions: run the software pilot as an estimator, scheduler and installer
An owner’s administrator account can hide the access problems that ordinary employees will encounter.
- Stone Profit Systems and SlabOS: trace estimate, material and job records
Stone Profit Systems publishes a fabrication feature overview covering commercial and material workflows.
- Countertop Software Guide: Reading Edition 01
A web reading edition collecting the first expanded guides from this publication.
- SPEEDlabel desk review: the missing layer between a job and its individual pieces
A job can be ready on the office schedule while one backsplash is still on a polishing bench.
- SPEEDlabel and Systemize: map the integration before calling the shop paperless
SPEEDlabel’s current website explicitly identifies an integration with Moraware Systemize.
- Precision Countertops’ paperless account: why existing features can matter more than another purchase
In a 2018 interview published by Moraware, Precision Countertops’ Steve Mast described using SPEEDlabel alongside Systemize’s shop-user function.
- Granite Gallery’s published SPEEDlabel statement: read the adoption lesson behind the endorsement
SPEEDlabel publishes a testimonial attributed to Gary Gutteridge, owner of Granite Gallery in Tumwater, Washington.
- SPEEDlabel and remake reporting: keep the replacement tied to the original piece
Moraware’s July 2020 article about Geoffrey Gran and The Countertop Factory connected the development of SPEEDlabel with attention to rework and remakes.
- LT3Raptor and business software: distinguish the measurement record from the sales record
LPI’s LT-2D3D page presents LT3Raptor as a related templating platform with a cloud-based management hub.
- Prodim Factory desk review: why stand-alone software still needs a defined handoff
Prodim describes Factory as stand-alone software that can also make use of Proliner measurement data.
- Schluter countertop documentation: give each trade the same selected detail
The RONDEC-STEP product page provides drawings, product tables and installation documentation.
- Prodim Factory exports: test a receiving workflow with a deliberately awkward file
Prodim describes Factory as software connecting field, office and production.
- SlabVision images: separate customer layout approval from machine preparation
Park describes SlabVision as a slab-imaging system.
- Robo SawJet software: distinguish machine control, programming and the shop schedule
BACA’s Robo SawJet documentation names RoboCut, Robo Commander and Vein Match within its software offering.
- Tenax technical sheets: organize consumable information around the exact product
Tenax’s product pages provide access to technical and safety data.
- Reading a TISE floor plan: turn booth names into a useful supplier shortlist
TISE brings stone, tile and flooring businesses into the same event.
- Parametrix and the JET 625: where the machine program meets the office record
Donatoni identifies Parametrix among the software associated with JET 625 programming.
- Vertika and warehouse software: verify what a location link actually does
Breton’s Vertika page identifies integration with warehouse-management software as a product consideration.
- A sawjet finished cutting. Should the software mark the job complete?
A cutting cycle, a finished part and a completed customer job are different events.
- Before choosing templating software, test how you would leave it
LPI presents the LT-2D3D alongside its templating software offerings.
- SPEEDlabel and Systemize: test what happens when a transfer is repeated
SPEEDlabel documents an integration with Moraware Systemize.
- Turn an expo software promise into a claim you can actually test
TISE’s 2026 recap describes demonstrations and emerging exhibitors across the show.
- Two branches call the same adhesive different names: fix the item record
Tenax’s Glaxs cartridge page lists multiple variants.
- A piece-tracking pilot needs a stop rule as well as a launch date
SPEEDlabel’s piece-tracking proposition raises an implementation decision for the owner: what would make a pilot ready to expand?
- One piece, two printed labels: how should the handoff record explain it?
A damaged label may need to be printed again, but a second physical label does not necessarily mean a second manufactured piece.
- Two people heard different things at an expo booth. How do we reconcile the notes?
One employee returns from an expo saying a feature is included.
- Piece labels identify items; a separate relationship explains which pieces belong together
An individual identifier answers “which piece is this?” It does not necessarily explain which other pieces belong with it.
