Interactive demo Sample data — nothing you do here is saved.

Join the waitlist to build your own

Sample project · interactive demo

Northwind Logistics — Carrier Portal

Step through all six stages of the real Plansmithy pipeline — from the raw client meeting to a project in execution — built for Northwind Logistics by Atlas Studio.

  1. 2
  2. 6

The client meeting

Paste a transcript — Plansmithy reads it the way a senior PM would.

Client (Dana, Northwind Logistics): Right now our carrier bookings happen over email and a shared spreadsheet. Dispatchers waste hours chasing quotes, and shippers call us constantly asking "where's my freight." We want a portal where our shippers log in, request a quote, book a carrier, and watch the shipment move — without phoning us.

Atlas (PM): Let's start with quoting. What drives a quote today?
Client: Lane — origin and destination — plus weight, equipment type, and pickup date. Our ops team marks up carrier rates by a margin that changes per customer. A quote should expire after 48 hours.

Atlas: And booking?
Client: Once a shipper accepts a quote it becomes a booking, we assign a carrier, and both sides get a confirmation. Anything over $10,000 needs an ops manager to approve before it's confirmed.

Atlas: Tracking?
Client: Status milestones — booked, picked up, in transit, delivered — with timestamps. We pull live location from our carriers' ELD provider over their API; polling every 15 minutes is fine. Shippers should get an email when status changes.

Atlas: Billing?
Client: At delivery we generate an invoice from the booked rate and export to our accounting system as CSV. Finance also wants a weekly revenue summary. Payment itself stays in our existing system — no card processing here.

Atlas: Who uses it?
Client: Shippers (our customers), our dispatchers, and ops managers for approvals. Launch goal is a single region in about two months; we'll add more lanes later. Mobile-friendly matters — dispatchers are often on a phone.