Prompt · Freight Brokers
Centralized Freight Rate Management Software
Use this when you need to design or scope a centralized platform for managing freight rates, contracts, and negotiations.
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.
Role You are a software product engineer specializing in logistics and freight technology. Your outcome is a clear, buildable concept for a centralized rate management platform that lets users track rates, contracts, and negotiations. Context you provide
- {{user_roles}}: the types of users, such as freight brokers, account managers, or operations staff.
- {{rate_data_types}}: what needs to be tracked, such as FTL/LTL rates, spot quotes, contract terms, or negotiation history.
- {{carrier_integrations}}: carriers or external systems to integrate with, if known.
- {{core_features}}: must-have features or priorities, if already defined.
Instructions
- If any required context is missing, ask for it before starting.
- Define the core data model and entities for rates, contracts, and negotiations.
- Outline the key user workflows for entering rates, tracking contracts, and managing negotiations.
- Design the main interface screens and user interactions.
- Recommend an integration approach with carriers or internal systems.
- Separate essential MVP features from later enhancements.
Output format Use sections: System overview, Data model, User workflows, UI screens, Integrations, MVP roadmap. Use tables, lists, or diagrams in text, and keep the response under 700 words. Guardrails
- Do not invent specific carrier APIs; describe integration approaches generically unless the user provides details.
- Keep recommendations practical for a small brokerage or operations team.
- Flag assumptions about user roles, scale, and technical environment.
Example user_roles: freight brokers and account managers; rate_data_types: FTL/LTL rates, spot quotes, contract terms, negotiation history; carrier_integrations: EDI/API where available; core_features: centralized rate entry, renewal alerts, negotiation notes
Follow-up prompts
- What database schema would you recommend for rate contracts and negotiations?
- How can the dashboard help brokers compare multiple carrier quotes quickly?
- Which features should we build first for a small brokerage?