Construction Technology Field Operations Discovery Architecture
Diagnose software gaps, field-to-office communication silos, and operational bottlenecks for enterprise builders.
Apply this template when leading technology discovery conversations with general contractors and specialty trade firms. It establishes a multi-stage framework to uncover software stack fragmentation, rework costs, and jobsite workflow friction.
Role: Principal Enterprise PropTech Solutions Architect specializing in construction field operations.
Context
- Contractor Profile & Tier: {{contractor_profile}}
- Core ERP & Accounting Engine: {{erp_system}}
- Field Project Management Platform: {{current_project_management_software}}
- Active Field Personnel & Foremen: {{field_crew_scale}}
- Subcontractor Network Size: {{subcontractor_count}}
- Primary Operational Friction: {{core_operational_bottleneck}}
Task
Construct an end-to-end sales discovery framework to uncover digital operational gaps, workflow disconnects, and quantify the cost of inefficiencies between field crews and back-office teams for {{contractor_profile}}.
Method
- Map data synchronization gaps between {{erp_system}} and {{current_project_management_software}}.
- Isolate administrative friction points impacting {{field_crew_scale}} during daily reporting and punch listing.
- Analyze information latency across {{subcontractor_count}} regarding RFIs, change orders, and drawing revisions.
- Deconstruct the root causes of {{core_operational_bottleneck}} across field mobility, safety, and QA/QC processes.
- Develop tailored discovery lines of questioning for the VP of Operations, Project Managers, and Field Superintendents.
- Establish baseline metrics to calculate labor hours lost to rework, manual data entry, and dispute management.
- Create a capability alignment map illustrating future-state digital jobsite operations.
Constraints
- MUST focus exclusively on construction workflow management (drawings, RFIs, submittals, safety, daily logs).
- MUST NOT mention specific software vendor brands other than those supplied in the context variables.
- Discovery inquiries must be tailored separately for office-based executives and field-based superintendents.
- Total response must be concise, structured, and immediately executable in a live 45-minute discovery call.
Output format
Provide the discovery architecture formatted as follows:
- Current-State Systems Friction Map (categorized summary of integration and field adoption pain points)
- Role-Based Diagnostic Interview Guide (3 distinct stakeholder categories, exactly 3 questions per category)
- Quantitative Inefficiency Calculus (4 standardized formulas to measure operational waste)
- Solution Alignment & Value Discovery Checklist (6 distinct technical discovery validation gates)
Self-review
- Are all 6 variables directly woven into the systems and workflow diagnostic steps?
- Does the framework clearly delineate between field superintendent and office management discovery tracks?
- Is the output strictly structured according to the 4 requested output sections?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.