← All projects

SMMBeast

A social publishing workspace for teams managing more than one brand.

Role Product direction and AI-assisted development
Focus Editorial planning, social platform integrations and developer API
Status Active development · pre-launch
Visit project website ↗
smmbeast.dev
SMMBeast public website

Public website · The SMMBeast landing page, with links to the product, demo and developer documentation.

Where the work gets scattered

Say an agency has a video ready for one client and a link post ready for another. The dates live in a calendar, the captions in a document and the accounts in several browser tabs. On publication day, somebody still has to check which account is open, whether the format fits and whether the post actually went through. If a response goes missing, the next person may have to check the platform itself before deciding whether to try again.

I started SMMBeast as my own product to bring that work into one place. I set the product direction and guide development with AI tools, from the public site and dashboard to the API and provider tests. I looked at products for social teams and APIs for developers. They suggested two ways into the same workflow: an agency needs a place to work across client brands, while a developer may need to add account connection and publishing to an existing product.

A workspace with a place for each brand

The dashboard is invitation-only. An organization can keep separate client and brand records, choose a brand, write a draft and put it on an editorial calendar. The date follows the brand's time zone, so an editor working elsewhere can still see the intended day. Saving a draft puts it in the plan. It doesn't queue the post for automatic publication. A full team and client approval workflow is still ahead.

The public site and workspace are available in English and Russian. The public demo is a separate, read-only walkthrough with fictional projects and posts. It shows how the workspace is organized, from the overview to the calendar. It can't connect accounts or publish anything.

SMMBeast public demonstration workspace with fictional sample data
Public demo · example data · product in development. The brands, posts and activity shown are fictional. The demo cannot connect accounts or publish posts. Explore the public demo ↗

Connecting an account is a separate decision

An agency and an integration developer need the same boundary: the right person should authorize the right account. SMMBeast opens a connection flow where an authorized user signs in with the platform and confirms which account to connect. The connection belongs to the selected brand. Developer API keys have limited permissions, and the application keeps each organization's records separate. What the app can do after connection depends on the permissions the platform actually grants.

When it's time to publish, SMMBeast can inspect supported media and resume an interrupted upload. Once the operator sends the post, the app tracks the provider's response. Repeating the same request with the same publication identifier checks the existing record without sending another post. If the response to the final send is lost, the app can show the result as uncertain. Sending again automatically could put a duplicate on a client's public account.

What the platform tests proved

Controlled tests verified Facebook Page publishing and post insights. A professional Instagram test account signed in directly through Instagram, published a test Reel and returned post and account insights. During testing, Instagram returned permissions in a form the integration hadn't expected. I used that discrepancy to guide a targeted fix, then checked the whole path again through sign-in, publication and analytics. A real zero reported by the provider appears as zero; a metric the app couldn't retrieve appears as unavailable.

TikTok was tested separately. One private post completed in Sandbox, and the posting switch was turned off again after the test. Threads has an adapter in the code, with real-account testing still to do. Each of these results describes a specific test under controlled access. Public use depends on platform review and permissions for the account being connected.

Where the work stands

SMMBeast is in active development ahead of launch. The public site, documentation and demo can be explored now. The working app is restricted to invitations. The next work includes platform reviews, further account testing and a reliable way for pilot users to recover access. The approval and scheduling steps that would connect an editorial plan to automatic publication are also still ahead.

For an agency, this is the part of a project I can take on: turn the team's workflow into a usable interface, build the integration behind it, then test it with the provider. On SMMBeast, that meant taking an ordinary question, "Did the post go out?", and making sure the interface can answer it honestly even when the provider doesn't answer back.