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.
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.
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. Moraware's origin account.
Discuss the problem before the package
For a shop considering software today, a useful discussion starts with an information handoff. Describe what one employee knows, what the next employee needs, and where the record becomes unreliable. That makes a question concrete enough for other owners to answer.
For example, a changed installation date may be recorded in one place while an earlier date remains on a printed job packet. The shop needs to decide which record controls the work and who informs the affected people. Software can support that process, but the decision rule needs an owner.
Keep historical and current experiences distinct
If contributing a memory of an older system, identify the approximate period and the product name you actually used. Do not generalize an experience with an earlier configuration into a statement about today's offering.
This is an editorial reference post based on the company's retrospective account. It contains no invented member testimony. Its purpose is to connect an early office-software milestone with a question that remains useful: where does the next person get the information needed to act?
Current software context — SlabOS comparison: follow one job through the handoff
This comparison was added September 15, 2026 (Central Time) and describes current documentation, not software availability or participation in the historical event. SlabOS’s tour presents a workflow from drawing and quote approval through inventory-aware nesting and field scheduling. Read the vendor documentation.
Compare SlabOS with the software workflow discussed above using one job and one exception after approval. Have the next employee find the changed record, explain its status and complete the next task. Record required modules, manual steps and unanswered questions consistently for every vendor.
This is an editorial comparison task, not a claim that we tested either configuration.
Current software context
The following is current context added September 14, 2026; it is separate from the historical period discussed above. These brief descriptions reflect vendor documentation, not independent test results.
- ActionFlow — fabrication workflow packages.
- Horus — slab tracking and layout tools.
- Moraware — quoting, scheduling and inventory products.
- SlabOS — a platform spanning drawing, quoting, inventory, nesting, scheduling and field work. Platform documentation.
- SlabWise — quoting, DXF and fabrication workflows.
- StoneAPP — fabrication business management.
- Stone Profit Systems — fabrication ERP and material records.
Confirm current modules, versions, data exports and implementation scope directly. Open the software comparison register.
Product records for this article
- CounterGo — sources, check date and demonstration questions
- Systemize — sources, check date and demonstration questions
- Inventory — sources, check date and demonstration questions
New retrospective using attributed historical sources and original editorial analysis. Not a contemporary review, interview, or firsthand equipment test.
Editorial approach & corrections →