0. Public data enrichment
Optional pre-discovery step. Use it to seed the questionnaire with publicly available company signals such as ABN/entity data, website clues, estimated employee ranges, and research notes. This prototype is compliance-aware: it does not scrape LinkedIn or bypass website restrictions.
Australian entity lookup
Publicly sourced / estimated company signals
Prepared research links
Research activity
A. Customer profile
Start by identifying the customer's business type. The questionnaire branches role lists, pain points, and recommendations based on this selection.
Activities performed
Industries served
Commercial scale
Delivery and contracting model
B. Users, roles, and labour cost
Capture who actually needs authoring software versus who mostly needs access to view, review, comment, coordinate, approve, estimate, schedule, or consume information.
Role-based productivity estimate
Default roles and salary assumptions change by customer type. Salaries are editable and intended as directional Australian base salary assumptions. Overhead/super/loading is handled separately below.
C. Current technology stack
Identify Autodesk and competitor tools currently in use. This section helps estimate software spend, overlap, and potential rationalisation opportunities.
Software products currently used
Tick the products in scope, adjust seat counts and annual cost per seat. Defaults are placeholders only; use the customer's actual contract values where possible.
D. Software, hardware, and schedule cost levers
This is where the questionnaire turns the customer's tech stack into measurable savings opportunities: fewer full authoring seats for non-authors, fewer CAD-spec machines for viewers, and fewer heavy schedule seats for stakeholders who only need access.
Software access optimisation
Hardware optimisation
Scheduling / Primavera / program access optimisation
Use this for customers where many PMs, site managers, contract admins, executives, or client stakeholders require schedule visibility but do not need a full planner/scheduler authoring environment.
E. Process pain points and value drivers
Ask what the customer wants to improve. This creates the qualitative narrative behind the ROI calculation.
Pain severity
F. Rework, data loss, and competitiveness risk
Quantify issues caused by wrong versions, disconnected markups, poor handover, schedule visibility gaps, or not meeting digital tender requirements.
Wrong-version and coordination rework
Data retention and closeout
Competitive / tender requirements
G. Implementation readiness and services estimate
Estimate how much services may be required if the customer does not have internal capability. This is directional, not a quote.
Scope modules considered
H. Results and recommended Autodesk path
Directional estimate only. Replace default assumptions with the customer's actual software pricing, salary data, device costs, implementation scope, and internal Autodesk guidance before using commercially.