cookboy

Nick is a chef, bartender and writer. He ran sauté, grill and pasta at a Michelin Bib Gourmand and James Beard–winning Boston kitchen, cooks privately for Harvard, Google and the Boston Pops, and writes with bylines in Yahoo Finance and FRANK151. Over a few years I built him the things a career shaped like that needs and nobody sells: a resume that reads like a person instead of a form, a site, a career system that drafts in his register rather than a template’s, and a recipe archive with no preamble in it.

Then the work turned into a business. COOKBOY is a kitchen-audit practice: Nick spends two weeks inside a restaurant mapping how prep, service and guest feedback actually run, and hands back one page per step. I build the system underneath it — the identity, the site, the automation, the document engine that produces the audit.

Designer, writer and engineer on every piece. The resume and its type system, the identity, the Cloudflare Pages site at nickdgardner.com, the audit site at cookboy.museshift.com, the recipe archive, the automation on n8n, and a career-materials system with his profile, voice rules and a cover-letter framework behind it.

Nick runs the taste and the kitchen expertise. I run the system underneath.

COOKBOY sells one thing: two weeks inside a restaurant, then a written map of how it actually runs. Every step of prep, service and guest feedback gets its own page answering the same four questions — where it breaks, what software could do about it, who stays in charge, and how you would know it worked. Then a ranked build order, an audit of the software they already pay for, and a 90-day plan that names no vendor Nick gets paid by.

The offer is guaranteed against a number: ten recoverable hours a week, or five times the fee in margin, written into the deliverable where the client can check it. The argument up front is the industry’s own — 42% of U.S. operators finished 2025 in the red, 9,500 independents closed, and roughly $130K a year separates a profitable full-service room from an unprofitable one.

I named it, designed it, wrote the code, stood up the infrastructure, and wrote most of the words. The identity had to work for a person applying to kitchens and for a business selling to the owners of those kitchens, which is why it stayed dark, typographic and unbranded-looking rather than turning into a logo exercise.

The through-line is the same one I use on my own systems: build the engine, not the artifact. The resume is a system that cuts resumes. The audit is a document engine that produces one page per step. Nick brings ten years on a line and knows which fixes a crew will actually use, which is the part no system supplies.