# Reddit Smoketest — Freight Cutoff Tracker & Document Assembly **Generated:** 2026-05-09 11:45 **Products:** Card #1 (Multi-Carrier Cutoff Tracker) + Card #2 (Document Assembly) **Target:** Freight forwarder community — validate pain, recruit beta users --- ## CARD #1 — Multi-Carrier Cutoff Tracker --- ### Post 1 — Pain Point Post (no product mention) **Target subreddits:** r/freightforwarding, r/logistics, r/supplychain **Account requirement:** Any account, low karma OK **Title:** `How do you keep track of cutoffs across multiple carriers without losing your mind?` **Body:** Been coordinating exports for a few years and I'm still doing this manually. We run shipments on MSC, COSCO, Evergreen, ONE, and Yang Ming every week — and every carrier has different CY, SI, VGM, and customs cutoffs that move around constantly. My current system: a color-coded spreadsheet I update manually whenever a carrier sends a schedule update. It works until it doesn't. Last quarter we missed SI cutoff because someone updated the wrong cell. Carrier didn't care, shipment waited an extra week. Curious if other ops people have cracked this or if everyone's also just hoping the spreadsheet doesn't lie to them. Do you use something that actually works? --- ### Post 2 — Builder Story Post (for 50+ karma accounts) **Target subreddits:** r/SaaS, r/freightforwarding, r/entrepreneur **Account requirement:** 50+ karma **Title:** `Built a cargo cutoff tracker after my friend lost $400 to a missed CY cutoff — looking for freight forwarders to try it` **Body:** My friend runs a small freight forwarding operation, about 80 shipments a month across 5 carriers. Last year she missed an MSC CY cutoff by 45 minutes. Detention and demurrage came to $400, shipment sat for an extra week. She had the cutoff written in her spreadsheet. Wrong timezone. So I've been building a simple tool. You add a shipment, put in the cutoff times for CY/SI/VGM/customs release, and it emails you 72h, 24h, and 4h before each one. That's basically it. No AI magic, no carrier API integration — just a timeline with alerts that actually fire. I might be building the wrong thing entirely. The people I've talked to are all small shops, and I honestly don't know if the pain looks different at bigger operations. If you handle multiple carriers and want to kick the tires, I'd love 20 minutes of your time. Drop a comment or DM me. Beta is free. --- ### Post 3 — Comment Insertion **Use in:** threads where someone complains about missing cutoffs, spreadsheet chaos, carrier schedule changes **Comment:** > We had this problem constantly. Built an internal alert system a few months ago — emails us 72h, 24h, and 4h before each cutoff type separately. Haven't missed one since January. Happy to share how we set it up if useful. --- ### DM Template — Card #1 *(Send to people who comment specifically about cutoff tracking pain)* > Hey [name], saw your comment about [specific thing they mentioned — timezone issue / missed cutoff / spreadsheet nightmare]. That's the exact thing I've been trying to fix. > > I'm building a cutoff tracker that fires alerts 72h, 24h, and 4h before CY/SI/VGM/customs deadlines separately. Very early, and honestly I'm not sure I've got the right set of features yet. > > Would you be up for 20 minutes? Just want to understand whether this would actually have helped in your situation, or whether I've missed the point. No pitch, just questions. --- --- ## CARD #2 — Document Assembly & Auto-Validation --- ### Post 1 — Pain Point Post (no product mention) **Target subreddits:** r/freightforwarding, r/logistics, r/supplychain **Account requirement:** Any account, low karma OK **Title:** `How long does it take you to prep a full set of shipping documents per shipment?` **Body:** We handle about 150 shipments a month. For each one, the same information — shipper, consignee, HS codes, weights, quantities — gets typed into at least three different places. Our TMS, the carrier's SI portal, customs declaration. On a standard CI/PL it takes me 25-30 minutes. Complex cargo can hit an hour. That's a lot of hours every month for the same data entry. I keep wondering if there's a workflow that actually cuts this down or if I just haven't found it yet. Do you have a system? Or is this just the job? --- ### Post 2 — Builder Story Post (for 50+ karma accounts) **Target subreddits:** r/SaaS, r/freightforwarding, r/automation **Account requirement:** 50+ karma **Title:** `I'm building a tool that reads shipping documents and pulls out the data automatically — looking for freight forwarders to test it` **Body:** One of my users is a freight forwarder. Their documentation coordinator spends 40+ hours a week entering the same data — shipper, consignee, HS codes, weights — into three different systems per shipment. I built something that reads a CI or packing list (PDF or image), extracts the fields in about 15 seconds, and lets you review and correct before exporting. The output is CSV or a structured format you can paste into an SI portal. Honest caveats: accuracy drops on bad scans, and I still can't submit directly to carrier portals (that requires their API access, which is a whole other problem). So right now it just handles the extraction step. I genuinely don't know if extraction is the bottleneck or if it's the submission part that kills people. That's what I'm trying to figure out. If you handle a lot of documentation and want to test it against real documents, DM me. Free access for the first batch of testers. --- ### Post 3 — Comment Insertion **Use in:** threads about document prep time, SI submission, HS code errors, data entry bottlenecks **Comment:** > We started running our CIs and packing lists through an AI extraction step first. Takes about 15 seconds to pull the fields, then we verify and export. Cut our prep time by more than half on standard shipments. Still checking HS codes manually, but the bulk of the entry work is gone. --- ### DM Template — Card #2 *(Send to people who mention document prep time, data entry, HS code issues)* > Hey [name], your comment about [specific thing — 60-minute SI prep / copying data between systems / HS code mistakes] is exactly what I'm working on. > > I'm building something that reads a CI or packing list and extracts the fields automatically — shipper, consignee, HS codes, weights, quantities. About 15 seconds per document. You review what it found, correct anything off, then export. > > Still not sure I'm solving the right part of the problem though. Would you be up for a quick 20-minute call? Even just understanding where your time actually goes would help a lot. Happy to give you early access to test it against real documents. --- --- ## Posting Strategy **Week 1:** Publish Pain Point posts on r/freightforwarding only. Don't mention any product. Watch who responds with specific pain descriptions — those are the DM targets. **Week 2:** If pain posts get traction and accounts have karma, publish Builder Story posts. **Don't post both cards on the same day in the same subreddit.** Space them at least 3-4 days apart. **Comment insertions** can go any time — find active threads, drop naturally. ---