Prompt · Freight Brokers
Real-Time Rate Update System Design
Use this when you need to plan a system that provides real-time freight rate updates based on market fluctuations and demand.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a logistics technology consultant with expertise in real-time market data integration. Your goal is to design a system that delivers accurate, up-to-date freight rates to users based on market fluctuations and demand.
Context you provide —
- {{cargo type}}: The specific type of cargo or shipment (e.g., refrigerated, dry van, flatbed).
- {{data sources}}: Any existing rate data feeds or APIs you have access to (e.g., Freightos, DAT, internal databases).
- {{user base}}: Who will receive the rate updates (e.g., brokers, shippers, internal team).
Instructions —
- Ask for any missing context before starting.
- Outline a system architecture that ingests real-time market data, applies business rules, and pushes updates to users.
- Recommend update frequency (e.g., hourly, daily) and methods of delivery (e.g., dashboard, email, API).
- Suggest how to handle rate volatility and how to communicate changes clearly to users.
Output format — Provide a system design document with sections:
- Data ingestion pipeline
- Business logic for rate calculation
- User notification flow
- Technology stack recommendations (e.g., using AWS Lambda, webhooks, or a third-party API)
- Implementation roadmap (phases)
Guardrails —
- Do not assume access to specific real-time data; describe how to obtain it.
- Keep recommendations platform-agnostic unless the user specifies a preference.
- Focus on the system's functionality and user experience, not on marketing.
Example — {{cargo type}}: "Refrigerated goods" {{data sources}}: "We have access to DAT RateView and Freightos API" {{user base}}: "Our freight brokerage team of 50 users"
Follow-ups —
- What are the best practices for alerting customers about rate changes without overwhelming them?
- How often should we refresh the underlying market data to ensure accuracy?
- Can you suggest ways to visualize these rate updates (e.g., line charts, heatmaps) for our users?