Case files from the pass

20 real builds for kitchens that rent, share and produce. Each one starts where the client started, names what was going wrong, shows what we built and how long it took, and ends with the person who runs it saying what changed.

  • 20case files
  • 4kitchen formats
  • 12US cities
Case fileCS-01Street food prep commissary, Savannah, Georgia“One message about commissary kitchen tours now carries what three used to. The difference shows up every morning.”Leah Abbott, Commissary administratorRead this case file

Every case file

Filter by the kind of kitchen you run. The closest match to your operation is usually the most useful read.

Showing all 20 case studies.

  1. CS-01Commissary kitchensStreet food prep commissary

    First messages worth answering for commissary kitchen tours

    For commissary kitchen tours, staff spent their first reply asking for information that should have arrived with the inquiry. Under pressure, that extra step became an overnight delay. Savannah, Georgia 10 working daysRead the case study
  2. CS-02Commissary kitchensWeekend commercial kitchen hire

    The short path to commissary kitchen tours on mobile

    With commissary kitchen tours, callers kept asking where to find things that were, technically, on the site. The information existed; the path to it did not survive a smaller screen. Santa Rosa, California 15 working daysRead the case study
  3. CS-03Commissary kitchensChilled prep and storage kitchen

    One shared set of answers for commissary kitchen tours

    Day to day with commissary kitchen tours, knowledge existed but circulated poorly: buried in threads, uneven between staff, and invisible to anyone visiting the site. Roanoke, Virginia 20 working daysRead the case study
  4. CS-04Commissary kitchensLicensed commercial kitchen share

    What happens after a commissary kitchen tours inquiry is sent

    When it comes to commissary kitchen tours, some people sent the same request twice, and others rang to check it had arrived. Staff lost time merging duplicates and reassuring callers instead of responding. Reno, Nevada 25 working daysRead the case study
  5. CS-05Commissary kitchensHourly commercial kitchen hire facility

    A preparation guide that steadies commissary kitchen tours

    For commissary kitchen tours, versions multiplied until no two customers had quite the same instructions. First conversations regularly began with corrections rather than the matter at hand. Newark, Delaware 10 working daysRead the case study
  6. CS-06Commissary kitchensChocolate and patisserie kitchen hire

    Honest limits on the commissary kitchen tours page

    With commissary kitchen tours, broad wording invited firm conclusions. The team's first job on too many calls was walking back expectations the site had accidentally created. Billings, Montana 15 working daysRead the case study
  7. CS-07Catering kitchensSmall-batch production kitchen

    Ending the relay race in commissary kitchen tours handling

    Day to day with commissary kitchen tours, replies duplicated while neighbors went unanswered. Absence cover meant reconstructing each thread's history before daring to respond. Tulsa, Oklahoma 20 working daysRead the case study
  8. CS-08Catering kitchensMeal prep production kitchen

    Commissary kitchen tours details, readable at last

    When it comes to commissary kitchen tours, no section could be linked, quoted or checked on a phone. The information was good; its container made it useless. Harrisburg, Pennsylvania 25 working daysRead the case study
  9. CS-09Commissary kitchensOvernight bakery kitchen share

    One approved version of the commissary kitchen tours facts

    For commissary kitchen tours, staff had to ask which page a caller was reading before daring to answer. Correcting one section never guaranteed the other versions had been found. Lexington, Kentucky 10 working daysRead the case study
  10. CS-10Commissary kitchensCommunity commercial kitchen

    Helping commissary kitchen tours visitors state their purpose

    With commissary kitchen tours, nothing in the inbox indicated what a message was for. Staff opened each one blind, sorting new requests from follow-ups by hand. Tacoma, Washington 15 working daysRead the case study
  11. CS-11Catering kitchensCatering prep kitchen rental

    The right office, first time, for commissary kitchen tours

    Day to day with commissary kitchen tours, misrouted calls were a daily tax on everyone's patience. The site's location information existed but was never joined up with the inquiry route. Worcester, Massachusetts 20 working daysRead the case study
  12. CS-12Commissary kitchensVegan production kitchen share

    Commissary kitchen tours: shown, not just described

    When it comes to commissary kitchen tours, callers asked practical questions the site never addressed, while the answers sat in internal documents nobody published. Chandler, Arizona 25 working daysRead the case study
  13. CS-13Commissary kitchensShared commissary kitchen

    Catching commissary kitchen tours interest after closing time

    For commissary kitchen tours, the team could not prioritize what it could not parse. The first working hour went on assembling the queue instead of answering it. Savannah, Georgia 10 working daysRead the case study
  14. CS-14Commissary kitchensHot food production commissary

    Commissary kitchen tours forms that forgive mistakes

    With commissary kitchen tours, visitors could not tell which answer needed fixing. Trying again sometimes wiped information they had already entered correctly. Santa Rosa, California 15 working daysRead the case study
  15. CS-15Ghost kitchensDark kitchen and prep space rental

    No dead ends: migrating commissary kitchen tours properly

    Day to day with commissary kitchen tours, every old address was a potential dead end for someone following a saved link. Nobody had an inventory, so nobody knew the size of the risk. Roanoke, Virginia 20 working daysRead the case study
  16. CS-16Commissary kitchensRecipe development kitchen rental

    Recorded approvals for commissary kitchen tours changes

    When it comes to commissary kitchen tours, requests meant different things to different people. Approval happened in principle, then publication happened in practice, and the two did not always match. Reno, Nevada 25 working daysRead the case study
  17. CS-17Commissary kitchensBakery production kitchen for hire

    Existing commissary kitchen tours conversations stay findable

    For commissary kitchen tours, follow-ups arrived dressed as new business. Staff matched names to old threads before anyone could address the actual question. Newark, Delaware 10 working daysRead the case study
  18. CS-18Commissary kitchensFood truck commissary base

    Learning which pages generate commissary kitchen tours

    With commissary kitchen tours, without origins, every page looked equally valuable, which meant no page could be improved with confidence. Billings, Montana 15 working daysRead the case study
  19. CS-19Commissary kitchensFarm shop production kitchen hire

    Planning for the day the commissary kitchen tours form breaks

    Day to day with commissary kitchen tours, a visitor hitting an error had to rummage through the footer for another way to make contact. Staff, meanwhile, had no agreed check for whether test messages actually reached the intended inbox. Tulsa, Oklahoma 20 working daysRead the case study
  20. CS-20Multi-brand operatorsFood startup incubator kitchen

    Commissary kitchen tours documentation the team can actually use

    When it comes to commissary kitchen tours, nobody internally knew the procedures: who approves, how to request, what to check. Ordinary maintenance waited on one person's diary. Harrisburg, Pennsylvania 25 working daysRead the case study

How every case file reads

The same five stations, in the same order, so two builds can be compared side by side.

  1. 01

    Starting point

    How the kitchen handled this before we touched it, in plain terms.

  2. 02

    The problem

    What that cost the team, day to day, on the line and in the inbox.

  3. 03

    What we built

    The pages, forms and routing we shipped, with the features they use.

  4. 04

    Timeline

    Working days from content approval to handover, staff review included.

  5. 05

    What changed

    The result, and the person who runs it saying so in their own words.

Questions about these case studies

Are these real clients?

Yes. Every case study on this page describes a real build, and every quote is from the named contact at that business, published with their permission. Nothing here is a composite or a written example.

Why is the business not named?

Each client is described by kitchen type and region instead of by name, so a case study can be specific about what was broken without advertising somebody else’s facility. The person quoted is named, with their role.

Why are so many of these about tour inquiries?

Because for a shared-use or rental kitchen, the tour request is the sale. A prospective tenant who cannot book a walk-through, or who has to send three emails to get one, signs somewhere else. Most of these builds fixed one part of that path: the form, the mobile page, the reply, the handover or the page that explains the facility.

How long does a build like these take?

The builds on this page ran between 10 and 25 working days after the client approved the content, including staff review and handover. A full new site on The Line goes live in 7 days, counted from onboarding.

Can we get the same work on our own site?

Yes. Every feature used in these builds is part of a plan, and each case study links to the feature and the plans that carry it. Plans start at $117 a month, with the $647 build fee invoiced only after launch.

Your kitchen could be the next case file

A live walk-through of the site you would get, in about 30 minutes. Plans from $117 a month, the $647 build fee invoiced only after launch.