Give a real estate idea
room to unfold.

01 / From an inspection finding to a decision

A finding leads to clarification, specialist input, options and a documented decision. Every conversation gets two seconds of emphasis. The diagram does not label every finding a defect or imply that every buyer has the same contractual remedies.

▶ Open the live client demo

Use it in a real conversation

Open it together during the inspection review. Pause on “Bring in a specialist” to explain why a general inspection is sometimes the start of investigation. Ask which stage contains the unanswered question. For a social post: “A report tells you what to investigate. Your decision needs more context.”

02 / From seller priorities to a considered launch

Link goals and property understanding to purposeful preparation, clear materials and a coordinated launch. The last step leaves room for feedback rather than promising an immediate offer.

▶ Open the live client demo

Use it in a listing presentation

Show a seller the whole picture before discussing tasks. Circle work completed and identify the next decision. Adapt it to a vacant home, an occupied property or a historic house; avoid imposing a generic renovation checklist on every seller.

Make a loop with Codex or Claude

Have your coding assistant help structure the design and render it with ordinary local tools. These examples use a Python script, Pillow and ffmpeg. The browser versions use inline SVG and CSS. This is a reproducible coding workflow; code execution and available tools depend on your assistant setup.

1. Define the real question. What should a buyer understand after watching? Gather source material and verify claims about laws, deadlines and contracts.
2. Structure the stages. Request six concise stages, their relationships and a sentence describing the limits of the model. Review wording with the responsible professional.
3. Request an editable visual. Ask for self-contained HTML/SVG with every label visible, clear reading order, pause controls and reduced-motion support. Save stage data separately.
4. Render deliberate frames. Use SVG browser captures or a drawing library for reliable text. These exports use Pillow: 144 frames at 1600 × 900, twelve frames per second. Each stage gets two seconds, with a progress line inside that stage.
5. Encode the sequence. The supplied script runs ffmpeg to create H.264 MP4 with browser-friendly pixels and fast-start metadata. It creates a 960 × 540 GIF at six frames per second with a custom palette. Prefer MP4 for quality and compact size.
6. Check the result. Inspect every stage, play the whole loop, check small-screen readability and inspect duration and dimensions using ffprobe. Keep a static poster for printing and motion-sensitive readers.

A prompt to adapt

Create an original editorial real estate process diagram about [topic].
Audience: [buyers / sellers / agents / brokers].
Main question: [one concrete question].
Verified sources: [paste relevant facts and sources].

Propose six concise stages. Keep all labels visible during a 12-second
loop. Emphasize one stage every two seconds. Use 1600 × 900,
generous spacing and restrained motion.

Deliver editable stage data, self-contained HTML/SVG with pause and
reduced-motion support, a static poster and an MP4/GIF export script.
Use rendering tools actually available. Verify wording, dimensions,
encoding and the complete loop before claiming completion.

Run python3 outputs/media-library/render.py from the project directory with Pillow and ffmpeg available. The script uses macOS Arial and Georgia fonts; substitute installed font paths on another system. Temporary frames go into work/media-library.

Share, cite and adapt

Rebrand colors and type, replace stage descriptions and have a local reviewer check the advice. Preserve the distinction between a conceptual illustration and a binding contract. You may share and adapt these original illustrations with attribution to Virtual Results Real Estate Publishing; identify substantive changes.