A funnel per book: link or QR code in the book → landing page → email → bonus download → optional follow-up emails.
Legal links are not set for the bonus pages — they are an instance setting.
Loading…
New bonus funnel
Sending health
Every email the system owes an answer about. Unclear outcomes wait here for your decision — they are never retried blindly.
Loading…
Reactivate a blocked address
For readers who unsubscribed or bounced and asked to receive emails again. Removed (deleted) addresses stay blocked.
Remove a reader completely
Deletes the person's data (data-removal request). Their address stays blocked so no future email can reach them. This cannot be undone.
Sender
The service that delivers your reader emails. Enter the connection values from your onboarding sheet — until the connection is verified, funnels stay unpublished and nothing sends.
Placeholders (button and unsubscribe are required): {first_name}, {bonus_name}, {button}, {button_note}, {closing}, {ps}, {sender_name}, {sender_email}, {publisher}, {year}, {unsubscribe}
Your whole catalog — click a pen name, then a book. Nothing about marketing here.
Loading…
Stacks
A stack is a set of Sponsored Products campaigns launched together. Built-ins are read-only — duplicate one to make your own. Launching a stack arrives with the launch update.
Creates the book in the catalog. Only the name is required — price, keyword, ASIN/ISBN can come now or later, the two ad links come from the generator afterwards. The book then appears automatically everywhere (offers, campaign, "still to offer").
Amazon keyword-link generator
Keyword + ASIN and/or ISBN-13 → the Amazon filter link (p_66 ISBN, plus p_78 when an ASIN is there) — it shows only your book while the buyer only sees the keyword. Saving it activates the book's branded short link — the link you give out in flows, ads and emails.
Funnel launch
Create a Meta ad from one complete, reviewable setup. Recommendations are prefilled; choose new media and a start time.
No Meta changes
Funnel launch — Meta ads for a new test-reader funnel
Launch a new book's test-reader funnel: pick the book, set the keyword, then prepare the Meta campaign — you approve every text in the preview, ads are created PAUSED, and one Activate click starts delivery. Nothing spends before that click.
Today — what needs you
Loading…
…
loading…
Funnel by book — where every lead stands
Loading…
Member sales by book — offered → bought → paid
Every sale to a club member, whatever the channel — club offers with their live status, plus books members bought via the test-reader funnel (counted as paid).
Loading…
Refunds to send
Everyone waiting for money — test readers and club, one list. Send the money in PayPal first, then click the row's "Mark as Paid" — it books the payout & arms the credit note in the same click, whatever the channel. Missing PayPal or address? Edit it right on the card.
Record a payout manually — edge cases
Normal case: the one-click "Mark as Paid" on the refunds list above does everything. This form is only for special cases (custom amount, past date, hand-picked purchases). You already SENT the money in PayPal; "Go" marks the chosen purchases as Paid and writes ONE row into the Payouts ledger. Afterwards "Create credit note" arms the PDF (~2 min).
Bookkeeping catch-up
This card only appears when a payout could not be booked automatically (e.g. address was missing at Mark-as-Paid). "Prepare" only READS and shows exactly what would be written — nothing happens until you approve.
Credit notes — the ledger
Every payout, newest first, with its credit-note state. "Create credit note" arms the row — the PDF builds within ~2 minutes.
Loading…
Data check — is everything consistent?
Read-only consistency report across CRM · Payouts · Club · Purchases. Writes nothing.
Accounts — you & the VA
Create or reset a login. The VA (virtual assistant) role sees the modules you tick below (Notifications, People, Emails) — the tabs marked with the green dot in your sidebar — never money (enforced by the server, not just hidden). Give Jana her password directly; it is stored only as a hash in ~/.bmo-users.json.
All data lives in this app’s own database.
Reviews waiting for your verification…
Allowed actions: verify ✓, enter address, "no address → PayPal". Payouts are done by Kris only.
Notifications
Two lists, grouped by book. Paid = these people are already paid and their review is not confirmed on Amazon yet. Waiting for the review = they bought the book but no review has been recorded (payment comes after). When you find a review on Amazon, click ✓ Review is on Amazon — the app records the right thing by itself (unpaid people move to Reviewed and enter Kris's pay workflow; paid people just get confirmed). Paying itself stays on the Home tab (Kris only).
Enter an address or PayPal email — the credit note needs at least one.
All leads by stage (the ManyChat pipeline)
Loading…
Member replies — the club inbox, sorted for you
Every new mail in the club mailbox from a known member or lead queues here — with a guess what it is and the matching one-click action. Nothing is written automatically; every button shows its proof line. Screenshots open right from the row.
Loading…
1 · Pick person, email type & books
Everything is live — members, email texts and books come straight from the database — refreshed every time you open this tab.
Books to offer (one or many):
2 · Check it — this exact text goes out
Edit anything directly in the fields. Nothing is sent until you click Send.
Club campaign — offer books to many members at once
Pick the offer template + book(s), build the eligible list (members who bought, were already offered, or have an open purchase for a chosen book are excluded automatically). Then review each email and send one by one. Every send does the full bookkeeping: email + the offered-books record + a Club Purchases row (Offered, price from the Links DB).
Everything an email is built from. Saving writes straight back to the database — the composer and campaign pick it up on their next refresh.
Placeholders you can use: {first_name}, {book_title}, {blurb}, {links}, {book_blocks} (list of several books), {amount}. Tick "records offer" if sending this email should mark the books as offered.
The fixed text with placeholders ({vorname}, {book_blocks}, {buchtitel}, {blurb}, {links}). Your German ships VERBATIM as written here — placeholders are filled per send.
Live preview
Assembled from the template + blurb fields as they are RIGHT NOW — unsaved edits included. «First name» marks where the real first name lands.
Sends via your SMTP account · Sent copy saved by IMAP · every send is logged · texts and books live in the app database.