Try Tomstok on what you actually need to build.

A scoped shadow production pilot gives sales, production and IT a shared basis for deciding. Your current solution continues to control actual production.

  1. Choose a product scope that asks the right questions

    Start with an agreed range and selected orders. Include a typical order, a demanding variant and a combination your specialists know must be rejected. Agree who will assess buildability.

    The purpose is to test Tomstok against your product knowledge and workflows. We agree up front which capabilities the pilot covers.

  2. Establish data, rules and the comparison basis

    We bring your approved dimensions, materials, article references, joints and product rules together as the pilot’s shared reference. Units, rates and waste assumptions provide a clear basis for comparing calculations and explaining differences.

    Your sales and production teams agree which results to compare. IT clarifies the data environment, access and any integrations. Agreed capabilities and assumptions are documented so everyone knows what the pilot examines.

  3. Run the same order through two separate paths

    Use the same agreed inputs in Tomstok and your existing solution. In Tomstok, examine choices, constraints, visualisation and the calculation outputs included in the pilot scope.

    Your existing solution continues to control real production. Tomstok’s outputs are used for comparison and technical assessment. That creates room to investigate differences before deciding on a changed workflow.

    How it connects Same input. Two roles in the pilot.
    Agreed orders and product data

    Same inputs and known assumptions.

    1. Your existing solution

      Supplies the reference basis and controls actual production.

    2. Tomstok

      Calculates within the pilot scope for technical comparison.

    Compare → explain differences → decide the next step.

  4. Explain differences before judging the result

    Compare components, quantities, glass sizes, cut dimensions and operations, for example. A difference may come from another product choice, article, unit or rule. It may also reveal a gap in one of the foundations.

    Compare cost and selling price separately where the data and capabilities allow it. Record both results and open questions. Missing rates and incomplete calculations remain visible as open items in the comparison.

  5. Use actual records where they exist

    If useful labour and material records exist for the selected orders, they can inform the assessment of estimated costs. Agree how records connect to an order, batch or operation, and make data gaps visible.

    Explore actual costing
  6. Finish with a basis for the next decision

    Bring together the tested configurations, results, causes of known differences and remaining questions. Distinguish product data corrections, missing capabilities and changes to your own process.

    The next step might be more variants, a wider range or a bounded integration. The decision should rest on what the pilot actually examined and an agreement on what remains before expanding.

Define your first comparison.

Bring a typical order and a challenging option. We’ll discuss which inputs and results are worth comparing.