IndustriesEvent and content agencies
Every event, its campaigns and its posts, on one calendar.
Illustrative, not a customer story
An illustrative week before a launch event
Three weeks out
The event is confirmed. The plan goes into a spreadsheet, the flyer into a drive folder, the caption into a chat thread and the client sign-off into an email. Nothing links them.
The approval chase
The client asks which posts are approved. The answer is spread across four places, and the person who knows is out today.
The day before
One post still needs its image. No tool knew the event was close, so nothing said so.
An event agency sells a date that cannot move. Maiden keeps the event, the campaigns around it, the content for each campaign and the files behind that content as connected records, so the calendar can show what is planned, what is approved and what is still missing.
Private beta. We start with a setup call and bring your existing work across.
Same week. Same team. Fewer seams.
- Without
The event is one sheet and the content plan is another.
With MaidenEvent, Campaign and Content item are linked records. Open an event and its campaigns and posts are there.
- Without
The same flyer is copied into a folder per campaign.
With MaidenThe Library holds a file once and links it to the event, campaign or content item that uses it.
- Without
Approval is a thread. Nobody can say what is signed off.
With MaidenEach content item has a reviewer and a status: Draft, In review, Approved or Published. An Approvals board groups them by that status.
- Without
Nobody notices a post has no asset until the day.
With MaidenContent items carry a "needs an asset" flag, and a Due dates calendar shows what is coming and what is not ready.
How an event agency fits
The event-agency template gives you these records. You approve the structure, and you can change it.
Event
Title, dates, venue, status from Planning to Wrapped, an owner and a budget. Event items hold run of show, deliverables, logistics and budget lines.
Campaign and content
Campaigns belong to an event. Content items belong to a campaign, with a brief, a caption, a due date, a reviewer and an approval status.
Posts and the schedule
A post has a platform, a status and a scheduled date. A Schedule calendar shows them by day. A Performance table holds reach, likes and comments per post.
Vendors and assets
Venue, AV, catering and print vendors, with a confirmed flag. Assets and folders for images, video and documents.
What works today, and what does not.
Works today
- Event, Event item, Campaign, Content item, Post, Vendor, Asset and Folder records, linked
- Events table, due-date calendar, schedule calendar, Approvals board and Performance table
- Instagram publishing for a post a second person approved, at the scheduled time, once
- A client portal for files, requests and approvals, free for clients
- Ask answers from your own records and says where it got the answer
Not built yet
- Publishing to LinkedIn, Facebook, TikTok, YouTube or X. Those platforms can be recorded on a post, not published to.
- An agent that writes, schedules or posts without a person approving it. Agents draft and recommend.
- Time tracking, rate cards and per-event profit.
Do we have to use the event template?
No. It is a starting structure. You see it before it is applied, you can change record types and views, and Maiden does not rewrite a live structure on its own.
Will Maiden post for us?
For Instagram, it publishes a post that a second person approved, at the time you set, and it checks the post still matches what was approved before it sends. If anything is unclear it stops and asks a person. Other platforms are not connected.
Can clients approve content?
Clients get a portal for files, requests and approvals. It costs nothing per client.
What about our design files?
Keep Figma or whatever you use. The Library stores the exports and links them to the event or campaign they belong to.