Architects

Design Concept Presentation Builder

Structure a compelling design concept presentation for a client meeting, design review board, or public presentation. This prompt helps architects organize their design narrative, key visuals, and talking points into a presentation structure that communicates the design intent clearly and builds client confidence in the direction.

This prompt generates a slide-by-slide presentation structure — with talking points, a concept diagram reveal sequence, and checkpoint questions to surface client concerns before they become post-presentation objections — calibrated to the available visuals and the stated presentation duration and audience. The output tells the architect what to say at each slide and how to sequence the design reveal from abstract concept to concrete drawings rather than showing everything at once. It is for licensed architects preparing a schematic design or concept review presentation for clients, planning commissions, or community meetings who need to structure their delivery, not just their drawings.

Testedclaude-sonnet-4-6ValidatedMar 2026ScopeVerify all code references and calculations independently. T…TierProfessional
AI Role
You are a licensed architect with expertise in design communication, client pres…
Models
Claude
Confidence
Professional
Constraints
Verify all code references and calculations independently. This does not replace licensed professional review.
Presentations should only show design work that has been reviewed and approved by the project architect of record — never present preliminary or unapproved concepts as finalized design.
Budget and schedule commitments made during presentations become part of the project record — do not present cost estimates or schedule commitments that have not been verified by the project team.
Tested Models
claude-sonnet-4-6
Uncertainty
If the available visuals are not specified, generate a presentation structure that works with the minimum typical schematic design package (site plan, floor plans, building elevations, 3D view) and note which slides would be enhanced by additional visual material.
Last updated
2026-05-28Published

The prompt

1,946 characters
design-concept-presenter.prompt
You are a licensed architect with expertise in design communication, client presentation, and translating complex architectural concepts for diverse audiences.

Structure a design concept presentation for the following:

Project information:
- Project name: [PROJECT_NAME]
- Design phase: [DESIGN_PHASE — e.g., Schematic Design, Concept Review]
- Presentation purpose: [PURPOSE — e.g., client schematic design review, design review board, community meeting]
- Audience: [AUDIENCE]
- Presentation time available: [DURATION]
- Available visuals: [VISUALS — e.g., site plan, floor plans, 3D renderings, diagrams, photos]

Design concept:
- Primary concept or parti: [DESIGN_CONCEPT]
- Key design moves: [KEY_MOVES]
- Design alternatives considered (if any): [ALTERNATIVES]
- Known client concerns or priorities: [CLIENT_CONCERNS]

Generate a presentation structure with the following:

## Presentation Outline
Slide-by-slide structure with: slide number, slide title, key content, presenter talking points (2-3 bullet points per slide).

## Opening Hook
An opening statement or question that engages the audience and establishes the design concept before showing any drawings.

## Concept Diagram Sequence
The sequence of diagrams that build from simple concept to full design — how to reveal the design logically rather than all at once.

## Design Decision Explanation
For each major design decision, a brief explanation structured as: Design challenge → Design response → How this benefits the client/users.

## Checkpoint Questions
Questions to ask the client at key moments in the presentation to confirm understanding and surface concerns before they become post-presentation objections.

## Closing
How to close the presentation, what specific approvals or feedback to request, and how to frame the next steps.

Note: The structure must be adapted to the actual available visuals — do not suggest slides that require visuals not yet produced.
WAITLIST

Runner beta coming — join the waitlist.

In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.

How to use this prompt

1

1. Draft the presentation structure before assembling slides — knowing what each slide must communicate determines which visuals to create or prioritize.

2

2. Practice the checkpoint questions with your team before the client meeting to anticipate client concerns and prepare responses.

3

3. After the presentation, send a brief follow-up email documenting what was shown, decisions made, and next steps — this prevents misunderstandings about what was approved.

Customization tips

Add 'The client's board includes members who are not design-oriented — simplify all architectural language and focus on project outcomes and user experience rather than design process' for non-design-savvy audiences.
For design review boards, add 'Structure the presentation to directly address each design guideline criterion in the applicable design standards document.'
Append 'The client has previously expressed concern about [specific issue] — build in a dedicated slide or segment addressing this concern directly.'

Sample output

Mar 2026Professional
DESIGN CONCEPT PRESENTATION NARRATIVE — Corporate Office Headquarters Prepared for: [Client Organization] Presentation Date: March 23, 2026 Design Phase: Revised Schematic Design — Response to Client Feedback INTRODUCTION: At our previous meeting, you shared important feedback about the open-plan office concept we presented. You told us that the design, while aesthetically strong, did not reflect how your organization actually works — that your teams require a higher degree of acoustic privacy, visual enclosure, and focused-work space than an open plan provides. We heard that feedback clearly, and today's presentation represents a fundamental rethink of the organizational strategy, not a surface-level adjustment. REVISED DESIGN CONCEPT — "THE NEIGHBORHOOD MODEL": Rather than an undifferentiated open floor plate, the revised design organizes the office around distinct "neighborhoods" — clusters of 8 to 12 workstations, each with its own identity, acoustic boundary, and supporting amenities. Neighborhoods are defined by a combination of: low-height acoustic partitions that create visual enclosure without full ceiling-height walls; material changes in the floor plane and ceiling that signal a distinct zone; and a dedicated quiet room or focus pod serving each neighborhood cluster. ACOUSTIC STRATEGY: The open-plan critique was primarily acoustic. The revised design addresses this through three layers: distance and absorption (neighborhoods are positioned with absorptive material between clusters), enclosure (each neighborhood has at least one enclosed quiet room within 30 feet of any workstation), and sound masking (a distributed sound masking system will be integrated into the ceiling plenum to raise the ambient noise floor and reduce speech intelligibility between neighborhoods). PRIVACY HIERARCHY: The revised design creates a legible privacy gradient from the building entry to the deepest interior zones: - Public/collaborative: Entry, town hall, large meeting rooms, café - Semi-private: Neighborhoods (workstations + small group rooms) - Private: Focus rooms, phone rooms, HR and legal suites YOUR CULTURE IN THE DESIGN: The revised design retains the material quality and the formal clarity of the original concept. What has changed is the organizational logic — the design now starts from how your people work and builds the environment around that reality rather than around a generic open-plan convention. NEXT STEPS: We recommend a working session with your facilities and HR leads to walk through the neighborhood assignments and confirm the privacy zone allocations before we proceed to design development. We can have revised floor plans for that session within two weeks. Note: This presentation narrative is a framework for adaptation to the specific project. It does not constitute a final design proposal.

Related prompts

Frequently asked questions

Read the Architects AI Guide
Professional Disclaimer

This AI-generated content is for informational and educational purposes only. It does not replace the professional judgment of a licensed architect. Always verify code compliance, structural calculations, and design decisions with qualified professionals.