Greek House prints custom apparel for fraternities and sororities — a business where the entire year compresses into recruitment season, and a release that slips a week might as well slip a semester. When the founder came to us, his previous team had slowed releases to once every few months. The product wasn't dying; it was calcifying, which is worse, because everyone can see the roadmap and nobody can ship it.
The role
My part was advisory and program leadership, and it started the way these engagements should: not with a proposal, but with the codebase. We reviewed what was actually there before promising anything. The verdict mattered — the code was workable; the delivery machine around it was broken. No pipeline worth the name, no path from a merged change to a live release that didn't involve ceremony and fear.
So the first thing we built wasn't a feature. We set up CI/CD and started shipping the same week. That week matters more than any architecture decision we made in the four years after it, because it reset the founder's relationship with his own product: changes went live when they were ready, not when the stars aligned.
From there I ran the engagement the way I run all of them — curating the program, coaching the team, keeping the founder's priorities and the engineering reality connected, with PMs on the routine and me on everything that couldn't afford to be routine.
What four years of shipping looks like
The cadence became the product's advantage. During rush season — the weeks when the entire customer base orders at once — we held same-day release capability. In a seasonal business, being able to fix or launch anything today during the weeks that decide the year is not an engineering vanity metric. It's revenue.
The company made the Inc. 5000 multiple years running. It secured official licensing with US colleges — a real moat in collegiate apparel, where the licensed and unlicensed worlds don't compete in the same market. And in 2024, Greek House was acquired.
The real outcome
The acquisition is the headline. It's not the result I care most about.
After the exit, the founder started his next company — and came back to build it with us. That's the entire consulting business model compressed into one sentence. A founder who has been through a full arc with you, from a stalled codebase to an acquisition, has seen everything: how you handle the bad weeks, what you're like when the pipeline breaks during rush, whether the invoices match the value. His next company is the only review that can't be faked.
What I'd tell anyone inheriting a "slow" team
Diagnose the delivery system before the code. Codebases get blamed for what pipelines did. A team shipping quarterly almost never has a code problem first — it has a fear problem, and fear grows in the gap between merging and releasing. Close the gap, ship the same week, and let the codebase improve while it's moving. Rewrites are what you do when you can't ship; shipping is what makes rewrites unnecessary.
Engagement: four years, advisory and technical program leadership · CI/CD from week one, same-day releases through rush season · Inc. 5000 multiple years · official US college licensing · acquired 2024 · founder now building his next company with us.