Superintelligence Prep for Countertop Fabricators: Templates and Slabs

An AI agent for a countertop fabricator is a bounded assistant that keeps template appointments, slab inventory notes and install dates in one shared job record, checks that they agree, and sends any conflict to a person who can decide. It does not measure kitchens, cut stone or set prices. Its value is in catching the mismatch between what was measured, which slab is actually reserved and when a crew is booked, before those facts reach the saw.

Key takeaways

• A template is the most expensive point to get wrong, so its record deserves the most structure.
• Slab inventory notes should show reservations and veining direction, not only what sits on the rack.
• Install dates depend on a verified template and a reserved slab, so the agent should check both before proposing a window.
• Give the agent read access and draft rights, and keep quotes, remakes and customer promises with staff.
• Choose one job type and one success criterion that you can observe within a few weeks.

Why template appointments decide whether a slab is cut once

A template is the field measurement the fabricator cuts from, so an error there does not stay small. Cabinets that are out of level, walls that bow, a sink cutout measured before the sink model was confirmed, or a seam placed over a range can all look correct on paper and fail on install day. Once a slab has been cut to the wrong dimension, the remedy is usually a new slab, a new lead time and a difficult conversation with the customer.

Most of these problems were visible at the template appointment, but only to the person standing in the kitchen. The information often lives in a handwritten note, a phone photo or the technician's memory. An operations agent does not replace that technician. Its job is to make sure the questions raised on site are written down, linked to the right job and resolved before material is committed.

What a template appointment record should hold

A record that a scheduler or an agent can act on needs more than a date and an address. At minimum it should capture the following, in fields that stay the same from job to job:

• Site access notes, with any access credentials kept in your secure system rather than in free text.
• Whether cabinets are installed, since measurements taken before cabinet installation often change.
• The appliance models and dimensions confirmed with the customer, with the source of each confirmation.
• Sink, faucet and cutout details, including whether the sink has been chosen and delivered.
• A sketch or photo reference showing seam locations and edge profiles agreed on site.
• Open questions, each with an owner and a status.
• The technician who took the measurements and the time of the appointment.

Write open questions as explicit items. A note that says "check outlet location" is easy to lose. An open item with an owner and a status is something an agent can see, remind someone about, and refuse to mark as complete while it remains unresolved.

How to write slab inventory notes a scheduler can trust

Slab notes usually fail when they describe the stone but not the commitments. A yard list that shows a lot as available tells a scheduler nothing about whether that lot is reserved for a kitchen that has not signed yet, or whether a remnant is large enough for the island on a job already in the queue. Useful notes separate physical facts from commitments.

Physical facts include the supplier lot reference, overall dimensions as received, any damage noted at receipt with a photo, the veining direction and color variation seen in the yard, and the storage location. Commitments include the job reference holding the slab, the hold status (quoted, approved or cut), the date of the hold, and whether the piece is a full slab or a remnant.

Illustrative scenario: A shop quotes two kitchens from the same material lot. The notes show that one job has approved and reserved the slab, while the second kitchen is still a quote, yet the scheduler has been treating the same lot as available for it. Without a reservation field, the second install could be promised for a date the shop cannot supply. An agent watching the record flags the conflict, and the owner decides whether to order a second lot or revise the quote.

A step-by-step plan for the first workflow

Start with one job type, usually a standard kitchen with a single sink and a straightforward layout. Then work through these steps in order:

• Map the stages a job passes through, from quote and template booking to installation and final walkthrough, and name the state each stage leaves in the record.
• Write the template fields and the slab fields as one checklist that the team agrees on before any automation begins.
• Define which states block a scheduling action, such as a template that is not verified or a slab that is not reserved.
• Decide who may change each field. Technicians update measurements, the scheduler updates dates, and the owner approves any change to a commitment.
• Set one observable success criterion, for example fewer install dates moved because a measurement or slab question surfaced late.
• Run the workflow with a person reviewing every proposed action for several weeks, then reduce review only for action types that have been consistently correct.

The order matters. Teams that connect an agent first and write the fields later end up with a tool that moves unreliable information faster.

Install scheduling: what the agent may propose and what staff must approve

Install scheduling is where a good record turns into a promise to a customer. The boundary should be written down before the agent is connected to a calendar, and it should be narrow at the start.

• The agent may propose an install window once the template is verified, the slab is reserved and a crew is free.
• The agent may draft a customer reminder using wording the owner has approved.
• The agent may flag a conflict when two jobs compete for the same lot, the same crew or the same access window.
• The agent may not confirm a date while any blocking question remains open.
• The agent may not change a sink model, approve a seam move or decide that a remnant is acceptable for a job.
• The agent may not promise remake timelines or quote changes, since those depend on supplier and pricing decisions made by people.

Permissions should follow least privilege. The agent should hold only the scopes it needs for the calendar and the job record, and every action should be attributable in a log. The [OWASP Authorization Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html) describes checking authorization on every request rather than once at setup, which suits a tool that touches customer commitments. Holding a visit open until its blocking questions are closed follows the same logic used in plumbing dispatch and callbacks.

How Be Human runs this as managed operations

A first Be Human engagement for a fabrication shop would define one role, usually a scheduling and records agent for a single job type, along with the template and slab fields it reads and writes, the approval boundaries described above and a success criterion the owner can observe. Managed operations then cover what changes over time: monitoring of proposed actions against what staff actually changed, recurring evaluations against real job records, permission review whenever a new tool is connected, and controlled updates when a field or rule needs to move. The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) offers a useful structure for organizing these reviews around governance, measurement and response. Take the free Be Human AI diagnostic to find the first task worth handing to an agent in your shop.

Frequently asked questions

Can an AI agent measure a countertop template for us? No. The agent does not measure, cut or inspect a kitchen. It keeps the template record complete, checks it against the slab and the schedule, and asks a person to resolve any open measurement question before an install date is proposed.

Do we need to replace our current fabrication or job software? Usually not at the start. In most shops the first step is a shared, structured record that the agent can read and write through approved access. Whether that record lives in an existing system or a new one is a decision to make after the workflow is clear.

How do we know the agent is helping? Measure one thing you already track, such as install dates moved after the fact, remakes traced to a missed measurement, or jobs that reached the saw with an unresolved question. Compare those counts over several weeks, and review the agent's proposed actions alongside the outcomes they produced.

Is customer data safe with an agent? The agent should see only the fields it needs, such as address details for scheduling, and never payment data it does not require. Access should be logged, reviewed regularly and removed when a role changes. Depending on where your customers are, privacy rules such as Brazil's LGPD may apply, so that review belongs in the first engagement.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.