Last week on the forum, members engaged in various lively discussions ranging from practical purchasing advice to strategic career insights. A recurring theme was the growing prevalence of remote buyer roles, as highlighted in two separate job threads. Additionally, there was considerable interest in the practicalities of choosing the right technology for large teams and the nuances of sourcing entertainment options for corporate events.
This Week’s Hot Topics
Remote buyer roles are becoming more common, and our latest job thread highlights this trend. It’s a crucial read if you’re considering a remote position or looking to understand the market shift.
Choosing the right laptops for a 60-person development team can be a daunting task. This thread delves into the decision-making process, weighing performance against cost and compatibility.
The rise of remote roles is a hot topic, and last week’s job thread also touched on this. It’s an insightful look at the changing landscape of buyer positions.
Looking forward to another week of engaging discussions. Your contributions make this community thrive. Until next time, stay curious and keep sharing.
We moved half our buyer team remote last week and the only thing that kept it sane was a shared RFQ board in Airtable plus a daily 15 min overlap window — otherwise handoffs got messy. For MOQs, we set a simple rule in the template: if MOQ savings is under 8% vs holding cost, we skip it; , endless debates vanished. @MayaB the one caveat is Airtable slows past about 50k rows, so we archive quarterly to keep it snappy.
We switched to an “async decision log” in Notion linked to each RFQ/PO, which made remote handoffs much cleaner. Daily overlap is nice, but time zones don’t always play ball, so we add quick Loom handoff videos (https://www.loom.com) and a 2-hour SLA on Slack pings to avoid the procurement telephone game.
Small tweak that helped us: for complex RFQs we drop a 90-second Loom recap and pin it to the RFQ/PO so the next buyer gets the “why” without a meeting; we pair that with a strict “one owner per RFQ” rule so async doesn’t turn into a relay race with no baton, @victoria_you32. Caveat: video is for context only — final decisions still live in the record or it gets messy.