A week that runs itself.
Five things will go out on their own this week. The one that spends money won’t — it waits, up there, for your yes.
Everything waits in one line.
Blog posts, short videos, ad launches, budget changes, promo pages, even the little messages your app sends — before any of it happens, it stands on one calendar with a date and a time next to it. Not five tools with five queues: one line, in order, that you can read in a minute. Repeating work — a weekly video, a monthly reader email — is a routine you set once, right on the calendar, in plain words; what it makes lands on the same calendar for review. And a post written once goes wherever you’ve connected it — LinkedIn, Facebook, X, Bluesky, Pinterest, Threads, Medium, your own blog — each version reshaped for its network, all from the same calendar slot. For Fernly, the invoicing app in our examples, next week is five items long.
When a post’s turn comes, SiteOps doesn’t publish it to some page of ours — it hands the post to your site, on your domain, in your design. Then it waits until the page is actually live, checks it, and tells the search engines it exists. Each step lands in the feed as it happens, so “published” always means published.
Messages go out through your own tools.
When the week calls for an email — a nudge, a welcome, the news that something shipped — SiteOps drafts it and hands it to the email tool you already use: Resend, Postmark, Mailgun, Brevo, SendGrid or Reteno. Your domain, your sender name; SiteOps does the writing and the timing. And you choose who it reaches: everyone, a segment straight from your email tool, or a cohort built from what visitors actually did on your site — “signed up but never checked out” is one click, because the one-line snippet has been quietly keeping score.
Messages inside your app work differently, on purpose. SiteOps never reaches into your product — when an in-app note or a push is due, it delivers the finished words to a web address you set up once, and your app shows them its own way: a banner, a push, a line in the inbox. The quiet rule holds here too — payment tools stay read-only. SiteOps can write “your trial ends Friday” because it can read your billing tool. It can’t touch it.
A dial, not a switch.
How much happens on its own is a dial with four stops. At the first, everything waits for you. At the second, drafts arrive finished and still wait. At the third, routine things — posts, videos, pages — go out on their own after a veto window: a full day where the item sits in plain sight and one tap stops it. At the fourth, you only hear about exceptions.
Money never rides the dial. Ads don’t launch and budgets don’t rise without your yes — at any stop — unless you walk into Settings and deliberately hand that trust over yourself. Even then your spending caps hold, and one switch stops everything at once, mid-week, no questions asked.
Your whole job is one short list.
Everything that needs a human lands in a single list: the ad waiting for a yes, the post inside its veto window, the draft that came out odd. On a good week it’s two items and a coffee. Approving is one tap; vetoing is one more.
Once a week a wrap-up arrives in plain words: what went out, what it brought back, and the one or two decisions actually worth your attention. At the top of the dial the daily list is usually empty — the wrap-up is how you keep your hand on the wheel.
It knows Black Friday is coming.
The calendar also carries the moments that matter to your product — Black Friday if you sell anything, World Tarot Day if you read cards. An event doesn’t do anything by itself: it marks the date, well in advance. You open it and tell the assistant what’s launching — it plans the posts, videos and emails around your dates, and the drafts arrive for your yes with time to spare.
Nothing about the moment is automatic money, either. If it calls for a discount, you create the code in your own billing tool; SiteOps writes the words around your dates, never the code itself — and payment tools stay read-only windows here.
Fair questions.
Can SiteOps spend money without me?
No. Ad launches and budget raises wait for your yes at every stop of the dial. The only way that changes is if you go into Settings and explicitly raise the trust for ads yourself — and even then your daily spending caps stay hard ceilings, and the switch that stops everything stays one tap away.
What if it schedules something I don't like?
That's what the veto window is for. Before anything routine goes out on its own, it sits visibly on the calendar — a full day by default — and one tap pulls it. If a draft is simply wrong, reject it or ask for another take, the same way you already review videos. And if you ever want silence, one switch holds the whole queue.
Does SiteOps create discounts in my billing tool?
No, and it never will — payment tools are read-only windows here. Your billing stays entirely in your billing tool: if a promotion needs a discount code, you create and manage it there. SiteOps only drafts the words around your dates — announcements, posts, an email — and every draft waits for your review.
Where do the blog posts actually live?
On your site — your domain, your design. SiteOps sends each post to your site through a small connection you set up once in Settings, waits for the page to come back live, and only then tells the search engines about it. If your site doesn't answer, nothing pretends: the item stays in the queue, marked as not yet out.