Most procurement advice assumes a dedicated buyer, or a small procurement team whose whole job is sourcing. At a 10–200 person manufacturer, that's rarely the reality. Purchasing is usually one of several responsibilities held by an ops manager, a production supervisor, or — at the smaller end — the owner, squeezed in between everything else that needs doing that day. Advice built for a dedicated buyer's full attention doesn't translate cleanly.
The actual constraint isn't skill, it's attention
Nobody handling purchasing part-time is bad at it. The problem is that RFQ tracking, chasing quotes, and comparing suppliers all take sustained attention to do well, and sustained attention is exactly what's scarce when purchasing is squeezed between production issues, customer calls, and everything else on someone's plate. The RFQ that sits unfollowed-up for four extra days usually isn't neglect — it's that something more urgent came up, twice, before anyone got back to it.
What actually helps at this scale
Reduce the number of times a task needs active attention. The expensive part of part-time purchasing isn't any single step — it's context-switching back into the RFQ tracker after being pulled away for two days. Anything that lets someone glance at status without reconstructing where things stood reduces the real cost of the interruption-heavy way this job actually gets done.
Make status visible to more than one person. If purchasing is genuinely part-time for one person, it's often ALSO informally backstopped by whoever's around when something's urgent — a coworker covering while the usual person is on the shop floor. That only works if RFQ status is visible to more than the person who happens to own it that week, which an inbox or a personal spreadsheet usually isn't.
Don't build a process that assumes full-time attention. A lot of procurement best practice — daily status reviews, formal supplier scorecards, structured approval chains — is designed for someone whose whole job is this. Importing that wholesale into a part-time role just creates process debt nobody has time to maintain. The right process here is the minimum structure that keeps RFQs from getting lost, not the most thorough one available.
The realistic goal: nothing falls through, not everything is optimal
For a dedicated procurement team, the goal might be squeezing the last few percent out of every sourcing decision. For someone doing purchasing alongside three other responsibilities, the realistic goal is simpler: no RFQ silently goes stale, no supplier gets forgotten mid-quote, and comparing what came back doesn't require an afternoon nobody has. That's a lower bar than "optimal," and it's also the bar that actually matters most at this scale — the cost of a slightly suboptimal award is usually smaller than the cost of a dropped RFQ nobody noticed.
That's specifically what RFQTrace is built around — a system that holds RFQ status visibly, for anyone on the team, so purchasing being a part-time job doesn't mean it's an unmanaged one. Start a free 60-day pilot — five minutes to set up, built for exactly this kind of squeezed-in purchasing role, not a dedicated procurement department that doesn't exist at your shop yet.