Graview Cloud for a content calendar

Six slots booked. Two still empty.

Posts, newsletters and videos, each at a different stage, on different channels, made by different people. Plan the slots by date and move each piece from idea to draft to ready. A slot with nothing in it is flagged, and so is a piece that nobody is making.

For small marketing groups and solo creators who post across three channels and keep the plan in a spreadsheet.

1 template
2 rules that watch
Private alpha · invite-only

Request an invite See the templates

Graviewstudio.graview.app/a/q4-content

Live

You, in ChatGPT

Plan our content for the quarter: what goes out on which channel, and what's still in draft.

graview · create_app4 kinds · 11 records · 2 rules

Slots4

Tue 7 OctTuesday post
Fri 10 OctFriday roundup
Tue 14 OctTuesday post
Fri 17 OctemptyAutumn launch recap

Pieces3

Tuesday postready · Mia
Friday roundupdraft · Raf
Autumn launch recapidea · Mia

Channels2

Blog2 pieces
Newsletter1 piece

People2

Mia2 pieces
Raf1 piece

RuleNothing is scheduled for Fri 17 Oct, in 13 days

Rules2 of 2 hold

Youput Autumn launch recap in Fri 17 Octnow
Rafmoved Friday roundup to draft2 min
ChatGPT, for youmade the app at studio.graview.app/a/q4-content4 min

Sound familiar?

If you run a content calendar, you've said one of these.

“What's going out Thursday? I thought you had that one.”
“Two weeks with nothing, then four posts in a day.”
“The draft is in a doc, the image is in a folder, and the caption is in a chat.”

For a content calendar

What the app holds.

Slots by date and by channel
Each piece from idea, to draft, to ready
Empty slots and unowned pieces, flagged

A week with it

What changes, day by day.

Monday planning
you set the quarter's slots per channel and who's making what; the calendar fills, and the empty weeks show.
Wednesday
a draft moves to ready from a chat; the slot it fills turns from flagged to booked.
Friday review
what shipped, what slipped, and the slot nobody has claimed yet.

Templates

Start from this one.

It's a complete app for a content calendar. Answer the questions it asks and it's yours to change. Or skip it and describe the job in your own words.

Template · 4 kinds · 2 rules

Content calendar

What's going out where and when, who's making it, and the gaps.

Holds: Slots A date something should go out on a channel, like Tuesday's post or the monthly newsletter.Pieces Something we're making to publish: a post, an email, a video.Channels A place we publish, like the blog, the newsletter or a social account.People Someone who writes, films or edits.
Rules it keeps: Every coming slot has something scheduledEvery unpublished piece has somebody making it
It asks you: Where do you publish? The blog, a newsletter, an account…Who makes the content?When should the first piece go out, if you know?

How it works

From a sentence to a shared app.

There is no setup. The app's shape comes from what you describe, and it changes when the job does.

Step 1
Describe it
Add Graview to ChatGPT or Claude once. Then say what you're organizing, in your own words. Or start from one of our templates on graview.cloud.
You: “Track our kitchen renovation and what's on order.”How to connect
Step 2
Get the app
About a minute later it's live at its own address on graview.app, with the records and rules the job needs. It shows up in your chat and opens on any phone.
okafor.graview.app/a/kitchen-renovation
Step 3
Invite people
Give each person a role: owner, editor, viewer, or one your app defines. Everyone sees each change as it lands, with the name of whoever made it, your AI included.
Here now: Nick, Sam and Ana
Step 4
Change it by asking
Ask for a deposit field or a budget warning and the app changes shape. Every record comes through. If one wouldn't, you're asked first, and earlier versions can be restored.
You: “Add a deposit field.” → version 2

Privacy

Your plans stay yours.

People put real money and real addresses into these apps. This is who can see them, and what happens when you leave.

Private until you share it

Only you can open a new app. Each person you invite gets a role: owner, editor or viewer.

Your AI has your permissions

A connected chat can do what you could do in that app, and nothing more. Its changes are labeled as its own, and it can never change who has access.

Sights decide who sees what

An app can keep some records to some people. A record you can't see is absent everywhere: on the page, in search, and in your chat.

One app can't reach another

Each app runs on its own, with its own storage, at its own address.

Not read, not used for training

We don't read your apps or train AI models on them. Staff can look only if you grant support access: read-only, for 24 hours, ended whenever you like.

Leave with everything

Export a whole app with its history at any time. Delete it and it's gone within 7 days, and from backups within 30.

Questions

What people doing a content calendar ask.

Does it publish for me?

No. It's the plan and the state of each piece; publishing stays in the tools that do it well.

Can a freelancer see only their pieces?

Yes. Invite them with a role that sees their own work, or give them a link to their list alone.

Other jobs

People keep track of all sorts.

Private alpha

Bring the calendar. Fill the empty weeks.

Graview Cloud is invite-only while we build it with its first people. Tell us what you'd make and we'll send an invite when there's room.

For you

Coming soon

Your own apps, kept as long as you like and exportable at any time. Free while the alpha runs.

For the people you invite