01Flooring request intake
The intake should preserve the property, rooms, access, occupancy, existing surface, product status, requested timing, customer-supplied photos or dimensions, and questions requiring review. It must distinguish a lead from confirmed installation scope.
Test it: Call with an incomplete three-room request, change the product status, and confirm the correct customer and job record, notification, assignment, and human handoff.
02Measure and estimate handoff
The measured record should stay connected to the estimate without pretending that software verified the dimensions, waste factor, pattern, layout, product suitability, or price. Check version history, assumptions, exclusions, taxes, and approval.
Test it: Enter team-verified quantities, revise one room and one allowance, send the estimate, record approval, and compare the accepted version with the job.
03Multi-day scheduling
Flooring scheduling software should represent measure, preparation, installation days, callbacks, and dependencies clearly. A calendar entry alone does not prove crew capacity, product readiness, automatic routing, or project control.
Test it: Schedule a two-day occupied installation, insert a repair request, delay product readiness, and confirm every assignment, customer commitment, and downstream change.
04Field record and scope change
Installers need the current approved scope and a controlled path for subfloor, transition, removal, trim, damage, or access findings. Confirm permissions, timestamps, photos, customer approval, and invoice impact.
Test it: Add an unexpected leveling condition from a phone, attach photos, request a reviewed change, approve it, and verify the final invoice without overwriting the original scope.
05Customer communication and AI phone
If an AI receptionist is part of the purchase, define allowed questions, booking rules, business hours, service area, unsupported work, estimates, emergencies, human escalation, consent, retention, and usage charges.
Test it: Call with a routine measure request, unknown square footage, product delay, unsupported commercial project, price demand, reschedule, and transfer request; inspect records, offered times, handoff, transcript, and credits.
06Specialist-system boundary
List every takeoff, floor-plan, laser measure, layout, estimating, catalog, inventory, purchase order, roll or dye-lot, warehouse, cutting, fabrication, retail, commission, and accounting function required. General FSM should not be assumed to replace them.
Test it: Trace one project through every current specialist tool and mark the system of record, identifier, import, export, reconciliation, failure, and manual handoff.
07Mobile, offline, and permissions
A mobile app listing does not establish full offline operation. Define which roles can see customer details, prices, notes, photos, estimates, invoices, payments, and schedule changes, plus what must work without a connection.
Test it: Run the measure and field-update steps on the real device and connection, remove connectivity, change a permission, reconnect, and inspect synchronization and audit behavior.
08Twelve-month cost and exit
Compare users, jobs, AI credits, phone number, calls, messages, payments, add-ons, migration, training, support, accounting, storage, taxes, renewal, internal labor, parallel operation, export, retention, and cancellation.
Test it: Calculate low, expected, and busy-month use for one year, then export a project with customers, notes, appointments, documents, photos, invoices, and payment references before signing.