inbox placement is a feature
Sending reputation, authentication records and bounce handling are set up with you, not left as homework. Reports show delivered, inbox placement, bounces and complaints side by side so a dip is easy to explain.
About Jibby
you want a list that’s glad to hear from you. here’s why we built this.
Jibby is an email workspace for small teams and creators. It exists because the tools on offer were either a blank box with a send button or an enterprise console with a six-week onboarding. Most people publishing a newsletter need something in between.
Annual plans from $149 — Sprout, Bloom or Orchard.
01 · the problem
email is the one channel you own, and the hardest to tend
The gap
Too little: a plain editor that stops at “send.”
Too much: a console built for a department you don’t have.
Jibby: one workspace sized for a team of one to ten.
A newsletter is a promise made on a schedule. Readers hand over an address and, in return, expect something worth opening on a Thursday morning. Keeping that promise is mostly unglamorous work: formatting the issue, remembering who joined last week, noticing who has gone quiet.
Small teams do that work in pieces. The editor lives in one tool, the list in a spreadsheet, the welcome email in a half-finished draft, and the results in a dashboard full of charts that never say what to do next. Every seam between those tools is a place where an issue slips a day or a new reader hears nothing.
A good send should leave you knowing what to try on the next one.
Jibby was built to close those seams. The editor, the sequences, the audience and the reports share one set of subscribers, so a change in one place shows up in all of them. The software stays out of the way so the writing can come first.
02 · how we decide things
five principles, checked against every release
When a feature idea arrives, it has to survive these questions. Most ideas don’t, and that is the point.
-
readers first
ConsentDouble opt-in is a setting we nudge you toward, and anyone who unsubscribed elsewhere stays unsubscribed when you import. A list of people who meant to be there outperforms a bigger list that didn’t.
-
say it in sentences
ReportsEvery report opens with a short written summary: what was opened, what was clicked, what to try next. Charts are there to back the sentence up, not to replace it.
-
set it once
TemplatesBrand colors, fonts, the footer and the unsubscribe line are decided one time and applied to every issue after. The tenth newsletter should take less effort than the first.
-
draw it, don’t code it
SequencesA welcome series is a picture: a trigger, a wait, an email, a branch. If you can sketch it on a napkin, you can build it here without writing a rule or a line of code.
-
price by list size
PlansThree annual plans, one payment a year, and the plan tracks the size of your list. No per-feature add-ons and no surprise tiers hiding behind a “contact us” button.
03 · how it’s made and looked after
sent on time, explained when it isn’t
Software for email carries a particular duty: when it fails, it fails in front of your readers. Here is how we look after that.
a reply from someone who knows the product
Write to support@jibbystudio.com and a person who uses Jibby every day answers, with the answer instead of a link to an article. Orchard adds priority support and a dedicated sending IP.
leaving should be easy
Contacts, tags and campaign history export as CSV whenever you ask. A tool you can walk out of cleanly is a tool you can trust to walk into.
small releases, written down
Updates ship in small pieces with a plain note on what changed and why. Nothing about how you send moves without a line in the changelog.
04 · where it’s heading
the next few issues of jibby itself
A direction, not a promise of dates. We write down what we’re working toward so you can decide whether it’s the same place you’re headed.
better send-time advice
Reports already show opens by hour. Next, Jibby will suggest a send window for each segment, with the reasoning written out beside it.
deeper journeys
More triggers for sequences: purchases, link clicks and tag changes, so a post-purchase drip can respond to what a customer actually did.
whatever you ask for twice
The roadmap leaves room on purpose. If two people write in about the same gap, it moves up the list, and you’ll hear back when it ships.