BestDinner × Aibolit — partnership campaign

Two brands with overlapping audiences — one selling pet food, one running a pet-care community — wanted to run a joint subscription offer. The blocker was the pitch itself: a static PDF deck reads once and gets buried in an inbox, and a generic Notion page doesn't feel like a real partnership artefact.

They also needed somewhere for joint subscribers to land — a single surface that carried both brand identities without one visually swallowing the other.

The pitch deck as a static site: one component per slide, deep- linkable, sharable as a URL instead of an attachment. Each slide is its own React component, which means the deck reads on a phone, supports inline embeds (the live mini-app sits inside the deck) and can be updated without re-exporting anything.

The co-branded mini-app re-uses the assistant from the Aibolit build but skins it with both logos in the header and a partner attribution row at the bottom of every reply. Identity stays balanced — neither brand reads like a sponsor.

Next.js 15 built to a static export — no server, drops onto any host, including the partner's own infrastructure if they want to white-label the deck. Each slide is a route segment so the URL identifies the slide; shared layout handles brand-marks, slide counter and arrow-key navigation.

The mini-app embedded in the campaign slide is the same React build from the Aibolit case, parameterised with the partner id. One codebase serves the standalone assistant and the partnered version.

The co-branded Telegram mini-app spans onboarding, an AI vet chat, a food card with prescription protocol, a renewable diet cycle, an escalation path to a real clinic, and partner attribution baked into the receipt. The same React build runs as the standalone assistant on aitelegram.mkantaria.com and as the co-branded version embedded inside the campaign slide — only the partner-id prop differs.

Each screen is hover-replayable on the live page. The screenshot below is a single static frame; the link above it opens the live interactive version.

Sign-up and reach numbers belong to the partner brands and stay with them. What I can confirm is shape: deck shipped, mini-app shipped, both live in English and Russian, one campaign cycle run end-to-end.

Brand partnerships die in PDFs. A deck-as-site survives because it sits at a URL, the partner can open it on a phone, and the actual product being pitched embeds inline. If a studio is running a co-marketing engagement and the deliverable is currently a Keynote export — this is the alternative.

The mini-app layer is optional. The deck-as-site pattern works on its own; the embedded product sample is what flips it from "a sales doc" into "a working artefact".