A two-week pilot that ends in late May is not the end of the conversation. It is the start of the math finance will use all summer. Research Triangle employers run lab-adjacent schedules, hybrid anchors, and client weeks that make week one look nothing like week two. If cup counts are averaged without labels, leadership renews the wrong story or cuts a pantry that was actually working on the floor that mattered.
How you label days, buildings, and peak types matters as much as the total pours on the spreadsheet. Break Coffee Co. bills on measured cups from whole-bean espresso equipment with real milk—not seat assumptions that hide real peaks.
Week two data without context is a trap
Campus and tower footprints from Raleigh through Durham and Research Triangle Park often host pilot weeks that overlap with mandatory in-office anchors or grant-driven crunch periods. Whole-bean equipment grinds per cup; cup-based billing shows adoption in pours instead of per-seat pantry lines that cannot explain a heavy Thursday to the CFO.
Preventative maintenance is bundled so facilities are not opening tickets when leadership asks for adoption proof the same week the pilot ends.
Pairing pilot weeks with post-pilot discipline
The May Research Triangle pilot weeks and cup count surprises article explains how to run an honest pilot before week two. This piece explains how to read cup counts after the pilot without averaging away the signal. Read both before renewal decks go upstairs.
Local field notes frame employee comparisons to street-level coffee near RTP and downtown. The break room readiness quiz scores service and spend clarity. The two week trial FAQ covers week one versus week two expectations.
Lab-adjacent rhythms versus corporate towers
A lab-adjacent wing with odd-hour handoffs and a corporate tower with nine-to-five hybrid anchors can share a parent company and opposite cup curves. Do not export math from one pilot wing to another without building type labels. Share mandatory in-office days and client weeks when you route through the Raleigh / Durham, NC overview.
The May research campus pilot weeks and cup counts piece approaches pilots from a spring angle. Pair both when you append day type labels to post-pilot reports.
What to separate in the appendix
Split mandatory in-office days from optional remote days. Split client-heavy days from internal crunch days. Split buildings if one facilities lead ran multiple pilots. Milk discard notes belong beside pour trends so ordering conversations stay honest.
Floor ambassadors catch grinder sounds, drip tray drift, and milk waste patterns that cup totals alone miss. Capture ambassador notes in the pilot closeout email to marc@breakcoffeeco.com so week three service does not reset to generic assumptions.
Pilot the wing leadership will fund
Recommend free two-week trials on the wing with the hardest adoption story, not the executive suite that stayed light. If post-pilot counts come only from the quiet floor, renewal math will underfund the wing that actually needed the upgrade.
Grant crunch weeks can spike pours without changing seat counts. Label those weeks in post-pilot reports so finance does not treat them as the new baseline or cut the program for a quiet optional Friday.
Week three service defaults to generic assumptions when pilot labels disappear. Attach mandatory in-office days, client weeks, and building type to the Raleigh / Durham, NC overview routing email so maintenance does not reset to a nine-to-five curve that RTP never ran.
Moving off single-use pods reduces visible plastic and improves taste. When you present cup counts after pilot week ends, show labeled weeks beside totals so finance does not punish a pantry for a light optional Friday or reward a quiet floor that never represented RTP traffic.
Use the Request a trial form on the Raleigh / Durham, NC overview for new wings. Call (919) 928-2785 or email marc@breakcoffeeco.com for routing questions.
