Tuesday's edition
Eight stories that matter today
Three sentences each, with a line on why each one matters. Five minutes.
- A port strike enters day three
- The census results land at 10
- A small town votes on a four-day school week
BlastsFlow, the Blasts Hub for publishers
The edition is what your readers subscribed to.
Each publication you run is a list readers choose. Each edition reaches the readers who chose it: by email from the first day, and directly on their phone or computer once they connect on Blasts.
- Name the publication
- Readers choose it
- Publish the edition
- It reaches them
Standard Blast Credits, no BlastsFlow subscription. Content Series included from the start.
The publication
Morning Brief
The edition
The reader
- By email From the day the reader subscribed. Nothing to install.
- On Blasts Once the reader connects with the same email address.
Why publishing is different
Everywhere else, the message is about something. Here, the message is the thing.
Most organizations send messages about a relationship that lives somewhere else. A publisher's readers came for the messages themselves.
Who sendsWhat the message is about
A schoolwrites about the school day.the school day
A property managerwrites about the building.the building
An employerwrites about the shift.the shift
A restaurantwrites about the table.the table
A publishersends the edition itself. It is what the reader asked for.the edition itself
So a publication needs its own readers, its own schedule and its own editor, and every edition should arrive as the thing it is.
What a publication is in BlastsFlow
A publication is a list readers choose, and the editions you send it.
BlastsFlow organizes your Hub around your publications instead of one mailing list. Four pieces, all of them real in the Hub today.
The Sunday LetterWhat it covers, and when it arrives: Sundays, 7:00 a.m.
- Edition 41
- Edition 42
- Edition 43
The editor in chief
Readers who chose The Sunday Letter
Publication
An audience readers choose
Named the way readers know it, with a line on what it covers and how often it arrives. Readers pick it on their preferences page, or in Blasts as an interest.
Edition
A message to that audience
Written in Compose and sent now or at a time you schedule, or written ahead as a Content Series and released on the publication's schedule.
Editor
A teammate granted the publication
Publishes to the publications they edit and reads their readers' replies. Editor approval is on by default, so an owner sees each edition first.
Subscriber
A reader and their choices
One person, one email address, and the publications they picked. They receive nothing they didn't choose, apart from what you send to everyone.
One publisher, three publications
- Morning BriefingWeekdays, 6:30 a.m.The news editor
- The Sunday LetterSundays, 7:00 a.m.The editor in chief
- Recipe of the MonthFirst Saturday, 8:00 a.m.The food editor
Three audiences, three schedules, three editors. A reader who chose only the recipe never receives a briefing.
- One send reaches one publication. There is no combining two publications or excluding one.
- All Subscribers reaches everyone in your Hub, whatever they chose, so it is for the rare message every reader should get.
- Announcements is a list readers choose for news from you between editions, like a new publication.
- Contributors, beta readers and any group you fill yourself stay hidden from readers.
Why readers subscribe
Readers choose the publication. They receive exactly that.
A reader who picks one publication gets its editions and nothing else from you, apart from what you send to everyone.
- They pick the publications
- On their preferences page, or as interests in Blasts. Adding one never adds another.
- They drop one without leaving
- Dropping a publication stops that publication only. Everything else they chose continues.
- Replies reach an editor
- A reply to an edition becomes a private conversation with the editors of that publication. Readers never see each other.
- Email or Blasts
- By email with nothing installed, or on Blasts once they connect. A reader receiving by email can take each edition as it goes out or one weekly digest.
One reader's choices
- Morning Brief (chosen)Weekdays, 6:30 a.m.
- The Explainer (not chosen)Weekdays, 9:00 a.m.
- Weekend Guide (chosen)Saturdays, 8:00 a.m.
- Announcements (not chosen)News between editions
Replying STOP stops everything and removes every publication choice. Replying START turns messages back on, and the reader chooses their publications again.
Email first
Readers subscribe with an email address. Their editions follow them to Blasts.
Nobody installs anything to subscribe to a publication. Blasts is the direct path a reader can add whenever they like, and the richer one once they do.
- 1
Bring your readers
Import the readers who agreed to receive your publications, with the publications each one chose, or point your sign-up form at the Hub. Each becomes an email subscriber.
- 2Receives by emailRoundmark PublishingMorning Brief, Tuesday: eight stories
Publish
Each edition goes to the publication's readers by email, from your own sending address once it is verified.
- 3Connects on BlastsRoundmark PublishingMorning Brief, Tuesday: eight storiesSame address: [email protected]
Readers connect when they choose
A reader who adds the free Blasts app and connects with the same email address moves to Blasts automatically, and their editions arrive directly on their phone or computer.
- The move needs the same email address. It happens on its own; nobody moves anyone by hand.
- A connection with a different address is a separate person in your Hub. The publications the first address chose do not follow it.
- Files you attach reach readers on Blasts only. The email edition carries the edition itself, so link to anything an email reader needs.
- The Hub reports delivery by channel. It does not know who read an edition or what they did next.
Content Series
A publication's schedule, written ahead and released on time.
Write the next month of editions at once. The Hub releases each one on the publication's schedule, to that publication's readers and nobody else.
- A reader who subscribes midway receives the next edition, not the backlog.
- Pause, resume or add editions any time; the Hub warns you when a series runs low.
- A paused series skips the dates it missed rather than sending them late.
- Series editions are text. An edition with images or files goes out through Compose, now or scheduled.
- Content Series is included from the start. No Hub Pro needed.
- Sunday 7:00Edition 39Sent before they subscribed
- Sunday 7:00Edition 40Sent before they subscribed
- A reader subscribes here, midweek
- Sunday 7:00Edition 41The one they receive next
- Sunday 7:00Edition 42Written ahead, waiting for its date
- Sunday 7:00Edition 43Written ahead, waiting for its date
When an edition is published
An edition goes to its publication's readers, and to nobody else.
Every edition follows the same path, whoever wrote it.
- 1Editor
The editor writes it
In Compose, from a template such as New edition, Correction or Schedule change, or ahead of time in a Content Series.
- 2Owner or administrator
An owner approves it
Editor approval is on by default: the edition waits until an owner or administrator approves it. Settings can turn this off.
- 3The Hub
It goes out
Now, at a time you scheduled, or on the Series schedule. An immediate send is held for about a minute so you can cancel it.
- 4Each reader
Each reader receives it
On Blasts if they connected, otherwise by email. Readers of other publications receive nothing.
- 5Editors
Replies come back
A reader's reply becomes a private conversation with the editors of that publication.
BlastsFlow sends when you publish. It does not promise the minute an edition reaches a device, and it does not know who read it or acted on it.
What you manage in the Hub
Your publications, your readers and your editors, in one place.
Everything a publisher runs in BlastsFlow, and nothing it doesn't.
- Home
- Conversations
- Compose
- Templates
- Campaigns
- Sent & Scheduled
- Review queueAppears once BlastsHub staff register a producer for you
- Audiences
- Subscribers
- Team
- Settings
- Integrations
- Help
Audiences
- All Subscriberseveryone
- Announcementsreaders choose
- The Sunday Letterreaders choose
- Recipe of the Monthreaders choose
- Contributorsorganization assigns
- Publications
- One audience per publication, with its description and its readers.
- Subscribers
- Imports, your sign-up form and an enrollment code. Only the email address, the name and each reader's publications are kept.
- Editors and approval
- Grant each editor their publications. Approval is on by default.
- Editions
- Compose with formatting, links and images, templates for a new edition, a correction or a schedule change, and a test to yourself first.
- Content Series
- A publication's schedule, written ahead and released on time.
- Conversations
- Readers' replies, private to the editors of each publication.
Hub Pro adds a New Reader Welcome for each publication (a short sequence for readers who subscribe from then on) and Event Campaigns for a launch or a live session. It unlocks at $500 in cumulative Blast Credit purchases.
Editions from your own systems
Some editions are written by a system. A person still publishes each one.
Some editions come from something you run: a generated digest, a daily puzzle, a report your team builds. BlastsFlow can accept them through a signed connection and hold each one for review.
- Your systemSigned ingest
- In your review queueTomorrow's puzzle
- A person decidesPublish now to Daily Puzzle readersApprove onlyReject
- ReadersBy email, and on Blasts once they connect
- Registered, not open
- Each producing system is registered for your organization by BlastsHub staff and signs every item. There is no open inbox.
- Held until a person decides
- Each item waits in your review queue exactly as readers would receive it, with the audience it goes to.
- Publish sends it now
- Publishing sends the item immediately to that audience. The queue does not schedule items: publish when you want it to go out.
- The source stays attached
- Every item keeps its producing system and its status: waiting, approved, rejected, published or failed.
BlastsFlow never writes an edition and never publishes one by itself.
What BlastsFlow does not do
A way to deliver your publications. Not a place to host them.
Knowing the edges saves you a surprise later.
- It does not host a website, a public archive or a paywall for your publications.
- It does not bill your readers: there are no plans, paid tiers or trials in the Hub, and it knows nothing about what a reader pays.
- It does not know who read an edition or what anyone did after reading it.
- It does not write, generate or supply content. Every edition is yours.
- It does not publish on its own. Every edition is sent by a person, at a time a person set, or from the review queue by a person.
- It does not promise the minute an edition reaches a device. It sends when you publish; arrival depends on each reader's email provider or device.
- It has no connector to newsletter or payment platforms. Readers arrive by import, sign-up form, Zapier or an enrollment code.
Cost
Standard Blast Credits. No BlastsFlow subscription.
- Credits per reader
- One edition on Blasts to one reader uses one Blasts credit. One email uses one email credit.
- Prepaid, never expire
- Credits are bought on BlastCredits.com as one-time purchases, never expire and carry no monthly fee.
- Included from the start
- Publications, subscribers, editors, Content Series and conversations, plus 50 email credits with every new Hub.
- Hub Pro at $500
- Journeys and Event Campaigns unlock at $500 in cumulative Blast Credit purchases, for any organization.
Example publisher
See it at Roundmark Publishing.
Roundmark is a demonstration publisher with five publications, each with its own schedule and its own editor. It is fictional, and it shows how publications, editions and readers fit together.
- Morning Brief
- The Explainer
- Daily Lift
- One Good Joke
- Weekend Guide
Questions publishers ask
What is BlastsFlow?
BlastsFlow is the Blasts Hub for publishers. Each publication you run is an audience readers choose, and each edition you publish reaches the readers who chose it: by email from the first day, and on Blasts once they connect.
What counts as a publication?
Anything readers subscribe to by name and expect again: a weekly letter, a morning briefing, a daily tip, a recipe edition. In the Hub each one is its own audience, with its own editions and, if you like, its own editor.
Do my readers need an app?
No. Readers receive editions by email with nothing installed. Readers who use Blasts can connect with you, and when they connect with the same email address their editions move to Blasts automatically.
Can readers choose some publications and not others?
Yes. Each publication is an open audience readers choose on their preferences page, or as an interest in Blasts. Every edition goes to one publication, so a reader receives only what they chose, plus anything you send to everyone.
What is a Content Series?
A publication's editions written ahead and released on its schedule, to that publication's readers. A reader who subscribes midway gets the next edition, not the backlog. It is included from the start.
Can a system send editions into BlastsFlow?
Yes, through a signed connection that BlastsHub staff register for your organization. Each item waits in your review queue, and a person publishes it. Publishing sends it now; the queue does not schedule and never sends on its own.
Can I charge readers or run a paid tier?
Not in BlastsFlow. The Hub holds no billing, plans or trials and knows nothing about what a reader pays. You pay for delivery in Blast Credits.
What does it cost?
Standard Blast Credits: one edition on Blasts to one reader is one Blasts credit, and one email is one email credit. Credits never expire. There is no BlastsFlow subscription.
What happens when a reader replies STOP?
Everything stops for that reader, and they are removed from every publication. If they reply START later, messages turn back on and they choose their publications again on their preferences page.
Set up your first publication.
Sign in, create an audience for each publication, bring your opted-in readers, and publish the next edition to the people who chose it.