How Example Bakery raised $84,000 from 132 neighbors to open a second oven

This is a placeholder case study committed during Phase 2 of the v4.0 build. It exists to confirm that the content schema validates, the page layout renders, and the build pipeline produces a working static page. A real, agent-generated case study replaces it during Phase 6.

Example Bakery is a fictional sourdough bakery in Pittsburgh’s Lawrenceville neighborhood. The owners opened in 2022 with a single deck oven and a ten-foot prep table. By spring 2025 they were turning away wholesale orders three days a week and renting time on a friend’s commercial oven across town to keep up with weekend demand. The capital raised on Honeycomb went toward a second deck oven, the lease on a small overflow kitchen one block away, and a part-time baker to run the early shift.

What changed when the goal hit

The campaign closed in nineteen days at one hundred and forty percent of goal. A hundred and thirty-two neighbors invested. Most of them already knew the loaves they were funding. The bakery’s existing wholesale accounts, the regulars who line up Saturday mornings, the parents at the school across the street, the staff at the coffee shop two doors down: they were the early checks. The middle of the campaign brought investors who had read about the raise on a neighborhood newsletter. The last week saw a small wave of out-of-state friends and former neighbors who heard about it through word of mouth.

Three weeks after the campaign closed, the second oven was installed and the overflow space was operational. Wholesale capacity went from forty-eight loaves a day to one hundred and twenty. Weekend retail sellouts at the original storefront stopped happening on Sundays.

The numbers in plain terms

• Raised: $84,000 from 132 investors at 140% of a $60,000 goal.
• Funding window: 19 days from launch to close.
• Use of proceeds: a second deck oven, six months of overflow-kitchen rent, and the first quarter of a part-time baker’s wages.
• Repayment: monthly debt service over thirty-six months at a fixed rate the owners chose at the time of listing.

Why a community raise instead of a bank loan

The owners had been pre-qualified for a traditional bank loan at a slightly lower headline rate. They went with a community raise for two reasons: the bank loan required a personal guarantee against their home, and they wanted the people who already shopped at the bakery to have a small ownership stake in what came next. The Honeycomb investors get monthly interest payments. The owners keep their home off the table. Both sides know what they signed up for.

What the campaign asked of them

The owners spent about thirty hours preparing the campaign and another ten hours during the active window answering questions, recording short updates, and replying to comments on the campaign page. They wrote one email to their existing customer list at launch, posted twice on the bakery’s social accounts, and printed a single eight-by-eleven flyer for the storefront window. Honeycomb’s team handled the legal documents, the investor accreditation checks, and the disbursement.

What they tell other owners considering a raise

The owners say two things to small-business friends who ask about Honeycomb: the work is mostly upfront, and the money is real money that comes with real obligations. The campaign window itself was straightforward because their existing customers carried the early momentum. The repayment is a line item they account for every month, the same way they account for rent. They do not romanticize either part. They built a bakery that already had a loyal following and a campaign that asked those followers to chip in. That is the pattern that worked for them.

What is on this page versus the live site

This placeholder ships with the v4.0 build verification. The real site replaces this fixture with a series of agent-generated case studies, each one tied to a specific Honeycomb campaign that hit its goal. The agent fetches the campaign page from invest.honeycombcredit.com, calls the Claude API with the same prompt that produced the rest of the catalog, runs the humanization validator, fetches the hero image, and commits the result. Every story on the live site is a story that actually happened, written from the public campaign data and the public summary the owners themselves submitted.

If you are reading this fixture during Phase 2 review, the layout, type system, color palette, metric strip, and CTA section above are all populated from the schema. The story body is plain HTML inside MDX. Phase 7 deletes this file.