Sidekick — included on Pro and Business, in early access

Your site, updated live on the call.

Sidekick is a meeting partner. Invite it to a call and it listens like any other attendee — hearing what's said, reading what's on the shared screen, and drafting the change you're all talking about before you hang up. Send it a Loom or a recording and it does the same thing after the fact.

book a demo

What it actually is

Sidekick is a second, quieter attendee on your call. It doesn't run the meeting, and it never interrupts. It listens the way a good chief of staff listens — tracking what's being decided, and noticing when a decision is really a change to your website.

When it hears one, it writes it down as an action item and shows it to the room. When somebody tells it to go, it makes the change: a real edit to your site, on a Draft. Everyone is looking at a real change instead of imagining one. Then it goes back to listening.

It doesn't only hear the meeting. While someone is sharing their screen, Sidekick is reading that screen too — which is how “make this one bigger” survives the trip from the call to the change. And it does the same job from a Loom or a recording afterwards, if you'd rather not put anything in the room at all.

  • What it is A silent AI attendee that joins your meeting like any other participant.
  • What it does Keeps a live summary of the call, reads what's on the shared screen, and drafts real site changes while you talk.
  • How you steer it Say it out loud, message it in the meeting chat, or click in its panel.
  • What it can't do Publish. Every change lands as a Draft you approve, like everything else here.

It isn't a notetaker

Plenty of tools already sit in meetings and write down what happened. That part of the problem is solved, and Sidekick would be a poor reason to replace the one you have.

Here's the part that isn't solved. Notes are a list of things somebody now has to go do. “Update the homepage headline” gets copied into a doc, then into a ticket, then into a sprint, and reaches the actual website three weeks later — if it survives the trip at all. The decision was made in eleven seconds. The delivery takes a month.

Sidekick closes that gap while everyone is still in the room. What you leave the meeting holding isn't a note about a change. It's the change, drafted, waiting for a yes.

A notetaker Sidekick
When the call ends A summary of what everyone said. A Draft of the page you were talking about, with the change already in it.
The action item “Update the hero headline” — assigned to someone. The new hero headline, already written, waiting on you.
What happens next Somebody opens a ticket. Somebody clicks approve.

It hears you, and it sees what you're seeing

Half of what gets decided on a screenshare is unsayable. Someone shares their dashboard, points at it, and says “this one — right here.” The transcript records the word this, which by the next morning means nothing to anybody.

Sidekick takes the frame from that moment and reads it. Not the meeting window with everyone's faces in it — the shared screen itself, full-bleed, so nothing is sitting on top of the thing being discussed. Then it writes down what's on it: the labels, the layout, the numbers, and the names actually rendered on the page rather than the ones it thought it heard. The pronoun gets a picture attached to it.

It isn't only listening for “this” and “that,” either. People narrate a screen three ways — pointing at it (“this button”), reading off it (“162 a month”), and announcing where they're going (“let me pull up the dashboard”) — and after the pattern-matching, a second pass reads the conversation again for the moments no pattern would have caught.

And the frame doesn't just sit in the recap. When Sidekick hands the work off, the screenshot goes with it — so whatever writes the copy or drafts the change is looking at the same screen you were pointing at.

  • What the transcript says “It takes four of these metrics, from here, so the customers helped…” — which names nothing you could act on.
  • What the frame says The dashboard that was open at that second, with its columns legible: Conversations, Customers Helped, Replies, Avg First Response. The garbled “customers helped” in the audio is a column header on the screen.
What it isn't

It isn't watching video. It reads still frames, at the moments the conversation flags — a curated set, not a recording of everything that crossed the screen. It doesn't track your cursor or your hands; every capture is triggered by something said. And it reads a screen the way a person does — labels, layout, headline numbers — not like a scanner. Don't treat what it writes down as a system of record for the figures on your dashboard.

You don't have to be in the meeting

The live call is the version worth seeing on a demo. But the usual reason people never start with something like this is that they'd have to change how they work — and you probably don't need to.

You almost certainly already have the raw material. A call that was recorded. A Loom you'd have made anyway to explain the change to somebody. A transcript sitting in a notes tool. Hand Sidekick one of those and it does the same thing after the fact: finds the moments where you were pointing at something, pulls the frame from each one, reads it, and drafts the change against your site.

Recording a two-minute Loom of your own site while you talk through what's wrong with it is, for a lot of people, the lowest-effort way to ask for a change that exists. You're not writing a spec. You're doing the thing you'd do anyway if you were explaining it to a person.

Calls it joins live

  • Zoom
  • Google Meet

Recordings it reads afterwards

  • Loom
  • Fathom
  • a recording or transcript you already have

How a change happens on a call

Start to finish, with nothing skipped. Every step that changes what the public sees is still a step a person takes.

  1. 1

    You invite it in

    Sidekick joins the call the way any other attendee does — it shows up in the participant list, and everyone can see it's there. Then it goes quiet. It has no microphone and never speaks.

  2. 2

    It follows the conversation

    In a panel beside the call it keeps a running summary: the topics you've covered, what you decided, and the action items coming out of them. You can watch it fill in as you talk.

  3. 3

    It spots the site change

    When the conversation turns into “the pricing page should say X,” that becomes an action item of its own — written down, shown to the room, and marked ready to run.

  4. 4

    You tell it to go

    Out loud (“Sidekick, go ahead”), in the meeting chat, or with a click in the panel. All three work the same way, and nothing starts without one of them.

  5. 5

    It drafts while you keep talking

    Sidekick makes the real change to your site — an actual edit to the Astro project behind it, on its own Draft. You carry on with the agenda while it works.

  6. 6

    The Draft is open before you hang up

    The change is on your site as a Draft — a real edit, not a note about one. Send it back for another pass in a sentence, out loud, and it goes again. Approving it is still a separate, deliberate step, on the call or after it.

Nothing goes live on its own

Sidekick drafts. You publish.

Every change it makes arrives as a Draft — the same approval step as every other change on BlinkPages. It has no publish step, on a call or off one.

see it on a real call

What you're left with when the call ends

Three things instead of one. The meeting stops being the place decisions go to wait.

  • The summary Topics, decisions, and who owns what — written as the meeting happened rather than reconstructed from a transcript afterwards.
  • The drafts A real Draft of your site for every change you asked for, each one sitting a single approval away from Live.
  • The record The action items that weren't about the website filed where your team already tracks work, so those don't quietly evaporate either.

Who this is for — and who should skip it

Most people don't need Sidekick, and we'd rather say so here than have you find out later. The ordinary way to run a BlinkPages site is to describe what you want to Claude, look at the preview, and publish — from your desk, in your own time. That's the product, and for most sites it's plenty.

Sidekick is for the people whose website decisions get made out loud, with other people in the room:

  • Agencies on client calls

    The client asks for the change and sees it before the call ends. The “we'll get that over to you next week” round trip — and the follow-up email, and the revision of the follow-up email — stops existing.

  • Founders and marketers running site reviews

    The weekly “the homepage should really say…” conversation ends with the homepage saying it, instead of with a note that the homepage should say it.

  • Teams with a long queue

    Any team where the distance between deciding and shipping is measured in weeks, and most of that distance turns out to be handoffs rather than work.

The honest version

If your site changes come out of conversations, Sidekick collapses the gap between the conversation and the site. If they don't — if you're a person who edits their own site when the thought arrives — skip it. Nothing else about BlinkPages changes either way.

Where it's up to

Sidekick is in early access

We run it on our own calls every week, and we're bringing customers on a few at a time. Something that sits in your meetings has to earn that seat, and the only way to find out whether it has is to use it on real ones and keep the group small enough to fix what we find.

It has drafted real changes to our own marketing sites during real meetings, and at least one of them is live today. We haven't put it on a customer's site yet — that's what early access is for.

It comes with the Pro and Business plans, so if you're on one of those you're already in line for it — early access is about the order we bring people on, not about paying extra. Say so on a demo and we'll be straight with you about whether your meetings are the right shape for it — some are, plenty aren't.

book a demo

The questions people actually ask

Mostly about the microphone, and rightly so.

  • Does Sidekick talk during my meeting?

    No. It has no voice and no way to interrupt. It appears in the participant list, listens, and writes into its own panel beside the call. If you want to interact with it, you start that — by saying its name, messaging it in the meeting chat, or clicking in the panel.

  • Is it recording my meetings?

    It joins as a visible attendee and keeps its own transcript of the call. While someone is sharing their screen, it also keeps still frames of that shared screen, because that's the only way it can know what “this one” means. Those frames are of the shared screen, not of people's cameras, and they're held for about a month. And because Sidekick shows up in the participant list, nobody is in the room without knowing it — if your organization has rules about who may join a call, treat Sidekick as an attendee and apply them.

  • Can it publish something to my live site?

    No. Sidekick has no publish step — it can open a change, not ship one. Everything it makes lands as a Draft against your site and stays there until a person approves it, which is the same separation every other change on BlinkPages has. A meeting full of people talking over each other is precisely the situation you want that separation for.

  • What if it drafts the wrong thing?

    You send it back, in a sentence, out loud. A wrong Draft costs you the time it took to look at it — nothing is live, nothing is broken, and there's no ticket to close. Being able to react to a real page instead of imagining one is most of the value.

  • Which platforms does it work with?

    Two different questions, so here are both answers.

    Calls it joins live: Zoom and Google Meet. If you run your calls somewhere else, tell us on a demo and we'll say yes or no rather than leave you guessing.

    Recordings it reads afterwards: Loom and Fathom, plus a transcript you paste in from anywhere. A Loom is the cleanest input, because a screen recording is nothing but screen — a call recording puts the participant thumbnails in the corner of every frame.

    We'd rather name the four we actually run than publish a supported-integrations table we'd then have to keep true. When that list changes, this page changes with it.

  • Can I send it a recording instead of inviting it to a call?

    Yes, and for a lot of people that's the easier way in. Point it at a Loom or a recording and it pulls the transcript, finds the moments you were pointing at something, and reads those frames before it drafts anything — the same thing it does live, just after the fact. A transcript on its own works too, though it's working blind: no screen, no pointing, just the words.

  • Do I need Sidekick to use BlinkPages?

    Not at all. The ordinary way to run a BlinkPages site is to describe what you want to Claude, look at the preview, and publish — on your own time, at your desk. Sidekick is there for teams whose site changes get decided in meetings, and it sits on top of that ordinary way rather than replacing it. Everything else about your site works the same whether you ever invite it to a call or not.

  • What does it cost?

    Nothing on top of your plan. Sidekick comes with Pro and Business, so if you're on one of those it's part of what you already pay for. It isn't on Starter. See pricing for what the plans cost.

    Being on the plan is what puts you in line for it, not what switches it on the same afternoon: Sidekick is still in early access and we bring people on a few at a time. Ask on a demo and we'll tell you where that queue is.

Bring a meeting

Watch your site change during the call.

Book a demo and we'll put Sidekick in the room. Describe a change out loud — or bring a Loom you already made — and we'll have it drafted before we're finished talking.

book a demo