Skip to content
serpico.

Food manufacturing and retail

A Marketing Plan Platform for a Food Brand

We built a platform where the brand's marketing plan lives at a /year/month address: activities by content category, an editor for each format, an Instagram feed preview, comments and change history. Guests can read the plan without logging in.

Client
Ukrainian food brand
Region
Ukraine
Timeframe
September - October 2026
Tech stack
Next.js 16 · React 19 · Tailwind CSS v4 · Supabase · Vercel · Supabase Realtime · Email
screens
8
database tables
14
migrations
23
commits
33
A Marketing Plan Platform for a Food Brand

Challenge

A food brand's marketing plan consists of dozens of activities per month: posts, stories, carousels, Reels, videos and live streams. Each format has its own structure. A carousel needs a description of every slide, Reels or a live stream need a storyboard, and a simple post has just text and a visual.

When a plan like this is kept in a spreadsheet or document, typical problems arise:

  • it is hard to tell how the Instagram feed will look after the posts go live;
  • comments and edits are scattered across chats;
  • it is unclear who changed what in the plan and when;
  • deadline reminders are sent manually;
  • partners or managers have to be given access to working files just to view the plan.

The brand needed a tool where each month's plan has its own permanent address, can be read without logging in, and where editing and discussion happen in one place. Visually, the platform had to follow the brand book rather than look like someone else's service.

What we did

We built the platform on Next.js 16, React 19, Tailwind CSS v4 and Supabase, deployed on Vercel. Over September and October 2026, the project accumulated 33 commits, 8 screens, 14 tables and 23 database migrations.

Plan structure

  • one plan per month at an address like /year/month;
  • guests read the plan without logging in, and only authorized users can edit;
  • activities are organized by content category and format.

A format-specific editor

The editor changes depending on what exactly you are planning. Stories and carousels have separate parts, so each frame or slide is described individually. Reels, videos and live streams have a storyboard.

Feed preview

The plan can be viewed as an Instagram feed on the brand's real profile. This lets the team judge how posts will look side by side before they are published.

Teamwork

  • comments directly on activities;
  • reminders daily at 6:00 AM and by email;
  • change history with a field-by-field comparison: you can see what it was and what it became;
  • real-time updates without reloading the page;
  • light and dark themes.

We carried the brand colors and fonts over from the brand book into design tokens, so the platform looks like part of the brand.

Results

The brand's marketing plan moved from spreadsheets to a dedicated platform. Each month has a permanent address that can simply be shared, and the recipient will see the current plan without signing up.

What the team got:

  • an editor that adapts itself to the content format;
  • an Instagram feed preview before publishing;
  • discussions in comments on specific activities instead of in chats;
  • daily reminders at 6:00 AM and by email;
  • a full change history with field comparisons;
  • real-time collaboration.

We do not cite reach or sales figures: this is a planning tool, and its effect depends on how the team runs its content. Development scope: 8 screens, 14 tables, 23 migrations.

What makes this project special

Generic content planning services offer one form for every format. Here, the editor understands the difference between a carousel and Reels and asks for exactly the information each one needs. The preview on the brand's real profile ends the "how will this look" debates, because the result is visible right away.

Another important detail is public read access. The plan can be shown to a partner or manager with a single link, without giving them editing rights. And the change history with field-by-field comparison provides full transparency: you can see who changed what and when.

Published: · Updated:

Questions about this project

How long does it take to build a content plan platform?

We built this platform in September and October 2026: 33 commits, 8 screens and 14 tables. The timeline for your project depends on the number of formats, roles and integrations.

What drives the cost of a platform like this?

The price depends on the number of modules, content formats with their own editor logic and integrations, for example with email or messaging apps. Work with the brand book and design tokens also affects it. We give a precise estimate after discussing the task.

Can you show the plan to people without access to the system?

Yes, guests read the plan at the /year/month address without logging in. Only authorized users can edit and comment.

How does the Instagram feed preview work?

The platform shows scheduled posts as a feed on the brand's real profile. This way you can judge how the content will look next to what is already published, before it goes live.

Can you see who changed the plan?

Yes, there is a change history with a comparison of every field: you can see the previous and the new value. Changes also appear in real time for everyone working with the plan.

Who supports the platform after launch and who owns the code?

We set the terms for code ownership and access in the contract before work begins. New formats or content categories are added to the same platform, because the database structure is managed through migrations.

More case studies

Lviv Meat Processing Producer: SEO, Google Ads and a Rozetka Marketplace Launch
SEO ServicesLocal SEOGoogle Ads

Lviv Meat Processing Producer: SEO, Google Ads and a Rozetka Marketplace Launch

Our longest-standing client: a Lviv meat producer with a chain of branded stores. Since February 2024 we have handled SEO, Google profiles for the stores, Google Ads and Shopping, plus the move to marketplaces: a 426-product feed for Rozetka and a fix for a critical stock error.

average Google position, June 2025 vs June 2026
12.6 → 5.5
clicks in June 2026 vs June 2025
+28%
Read case study →
A CRM for a Meat Producer's Marketplaces, Orders and Pricing
Web Development

A CRM for a Meat Producer's Marketplaces, Orders and Pricing

For a Lviv meat processing producer, we built a single dashboard that brings together feeds, orders, stock, shipping labels and prices from the client's own WooCommerce store and the MauDau and Rozetka marketplaces. The system now has 18 screens, 74 API routes, 6 roles and 5 scheduled automated jobs.

screens in the dashboard
18
API routes
74
Read case study →
Hurtom: A B2B CRM and Wholesale Customer Portal
Web Development

Hurtom: A B2B CRM and Wholesale Customer Portal

Hurtom brings wholesale orders, order picking with actual weights, documents and account balances together in one CRM with a separate customer portal. Thanks to a ready foundation from a previous project, the first working version with all modules was ready in about 3 hours.

screens in the CRM
19
screens in the customer portal
9
Read case study →

Want results like these?

Tell us about your goals and we'll estimate your project's growth potential.

Free consultation

Tell us about your project and we'll prepare a growth plan