
What it is
One desk for the four parts of the work
A book is written in one room and sold in four. There is the writing itself, which is never finished at the first pass. There are the posts that tell people the book exists, each one shaped for a different place and a different kind of attention. There are the people: the bookseller who took ten copies, the podcast host who asked for a second conversation, the reader who wrote after a talk. And there is the page where somebody who has heard enough decides to buy. Most writers keep these four in four programs, and the connective thread between them lives only in their head.
OmniWriter keeps them on one desk. It is a signed-in application with a short sidebar and five doors: the first screen, the Writing Assistant, the Post Generator, the contact book, and the book's own page. The first three are private to the person who works there. The last is the window the public looks through, and it ends in a checkout. Nothing about the arrangement is clever. It is simply that the person who wrote a paragraph this morning, turned it into a post at noon and logged a call with a bookseller at four should not have had to change programs three times to do it.
A book is written in one room and sold in four.
Two of the rooms are worked by an AI, and the page says so plainly because the app does. The Writing Assistant sends a draft to a language model with one instruction out of five, and the model returns a revised version, a numbered score of its own, and a list of suggestions with the reason for each. The Post Generator sends a topic, a platform and a tone to a language model and receives a post, a set of hashtags, two other ways of saying it and a sentence of advice. Neither room publishes anything anywhere. What the model writes comes back to the desk, where the writer reads it, takes what is right and copies it out.
The other two rooms are records. The contact book holds the people who matter to the work, each with a status, a source, an estimated value and notes, and each with a history of every email, call, meeting and note logged against them. The book page holds one book, set out as a long, slow page with a guided reading of its chapters, a statement of what is inside, and a three-step checkout that opens a secure payment through Stripe once the house's payment key is in the app's settings.
OmniWriter is one of the nineteen applications in B-Corps, the operating system the house runs on every day. It sits in the publishing layer, beside the tools that prepare a book, and it does the part that comes after the manuscript: the sentence made cleaner, the announcement made, the relationship kept, the copy sold.

A day with it
A paragraph, a post, a bookseller, a Tuesday
An author of a short book on the design of calm software has a newsletter to send by Friday, a talk on Thursday and a bookseller who has not answered since September. She opens OmniWriter a little before nine. The first screen says Welcome back, and under it, Your creative workspace at a glance. Three cards sit in a row. One counts the people in her contact book, one counts those still marked as leads, and the third counts the posts she has saved. Each card has a quiet line beneath it, View details, and each opens its own room.
She goes first to the Writing Assistant, because the newsletter's opening paragraph has been bothering her for two days. She pastes it into the large field marked Your Text. A small count underneath says one hundred and sixty-two words. She knows it should be shorter, so she chooses Make Concise from the five modes along the top and presses Analyze. A line appears on the right, Analyzing your writing, and a few seconds later the results arrive in three cards. The first is a score, seven out of ten, with two sentences on what was changed. The second is the improved version, ninety-odd words, with a copy button in its corner. The third is a list of suggestions, each marked with its kind and each showing the phrase she wrote, the phrase proposed and a short reason.
She does not take the whole revision. She takes the second suggestion, which cuts a clause she had loved and which, read aloud, she can hear was in the way. She copies the improved version anyway, pastes it into her newsletter beside her own, and keeps the better half of each. Then she presses Clear, and the field and the results are both empty again, as if the morning's paragraph had never been there.
At eleven she opens the Post Generator. The talk on Thursday needs announcing. She types the topic, a talk on why dashboards make people tired, chooses LinkedIn as the platform and storytelling as the tone, and adds a line of context: Thursday evening, a small room, questions afterwards. She presses Generate Post. The answer comes back in a card headed Generated Post: a short story about a nurse and a monitoring screen, a turn toward the talk, and a row of hashtags. Beneath it is a sentence of advice from the model about when to post it. Beneath that are two Alternative Versions, one plainer and one more personal. She likes the plainer one. She presses its copy button, and the text is on her clipboard. She saves the main version too, because she may want it next month, and it appears at once in Saved Posts on the left, marked linkedin, with its own copy and delete.
After lunch she opens the contact book. Four counts sit across the top: everyone in the book, the active leads, the customers, and a figure for the pipeline that is simply every estimated deal value added together. She types the bookshop's name into the search, and the table narrows to one row. She opens it, and a sheet slides in from the side with the bookseller's email, telephone, company and the note she wrote in the summer: interested in an event, wants signed copies. Under Activity she presses Add, leaves the type on Note and then changes it to Call, leaves the date as today, writes a subject, Left a message about the autumn event, and two lines of detail. She presses Save Activity, and the call joins the history above the summer's email.
At four a stranger writes after reading her book. She presses Add Contact, gives a name and an email, sets the status to lead and the source to event, and adds a note about where they met. A former partner who has closed his studio she does not delete; she opens his record and sets him to inactive, so that the history stays and the counts are honest. Before she closes the desk she opens The Code from the sidebar, chooses the third chapter in the guided reading to check that its excerpt reads well, walks through the checkout's three steps and back without paying, and closes the window. The newsletter is shorter, the talk is announced, and the bookseller has a record of the message she left.

The writing
The first screen, and a second reader for every draft
The desk opens on its first screen, and the first screen is deliberately small. It welcomes the person back, says in one line that this is their workspace at a glance, and shows three counts that are each a door. The number of people in the contact book opens the contact book. The number still marked as leads opens the same room, because a lead is the person most likely to need something next. The number of saved posts opens the Post Generator. Below the counts, under Quick Actions, two larger cards open the Writing Assistant and the Post Generator directly, each with a sentence on what it does, so the next thing to do on most mornings is one press away from the moment the app opens.
When the contact book holds anyone, a panel headed Recent Contacts appears beneath, showing five names with their email and status and a link to view all of them. It is a glance rather than a report: enough to remind a person who is in play, without asking them to open the full table before they have had coffee. A desk that holds no one yet simply leaves the panel out rather than drawing an empty box, and the counts read zero until the first name is added.
The model is a second reader, and the desk is built so that the writer stays the first.
The Writing Assistant is the room most people will open most often. It is one wide field for text, a word count that changes as the text changes, and five modes set out along the top like the stops on an instrument. Full Improve asks the model to work on grammar, style and clarity at once. Grammar asks it to look at grammar and nothing else, which is the mode for a paragraph whose voice is already right. Style asks for suggestions on how the thing is said. Clarity asks for the text made clearer and easier to read. Make Concise asks for the same meaning in fewer words, and it is the mode for the paragraph a writer already knows is too long.
When the writer presses Analyze, the text goes to a language model with the instruction for that mode, and the app asks the model to answer in a fixed shape. That shape is what makes the room useful rather than merely impressive. The first thing back is a score from one to ten, which is the model's own judgment and should be read as one opinion among several, with a short summary of what was changed. The second is the improved version, whole, with a button that copies it. The third is the list of suggestions, and each suggestion carries four things: its kind, marked as grammar, style, clarity or conciseness; the phrase as it was written; the phrase the model proposes; and an explanation of why.
The explanations are the heart of it. A revision without reasons asks a writer to trust it or ignore it. A revision with reasons can be argued with, sentence by sentence, and a writer who argues with a good editor for a year becomes a better writer. The model is a second reader, and the desk is built so that the writer stays the first. Nothing changes in the original text unless the writer copies something across. Clear empties the field and the results together, and the room keeps no record of what was pasted into it, which makes it a place for unfinished work as much as for finished paragraphs.

A draft improves at the second reading. The desk supplies the second reader and leaves the decision where it belongs.

The posts
One topic, the platform's measure, and two other ways to say it
Telling people a book exists is a craft of its own, and it is a different craft on every platform. A post for X has two hundred and eighty characters to work in and is read in a scroll. A post for LinkedIn can run to three thousand and is read by people deciding whether a writer is worth their working hour. Instagram allows two thousand two hundred and is read under a picture. Facebook's ceiling is so high that the limit is a formality. The Post Generator begins from that fact. A person chooses the platform first, and the app tells the model the platform's limit in the same instruction that carries the topic.
Then the tone. There are seven in the menu, and each changes the post more than the topic does. Professional, casual and humorous are the registers most people reach for first. Inspirational, educational, promotional and storytelling are the ones that suit a book, and storytelling in particular tends to give the model something to do: a small scene, a turn, and the announcement at the end. A field for additional context takes anything the model should know and could not guess, such as a date, a place, a link or the one point the writer insists on. The button stays unavailable until there is a topic, because a post about nothing is not worth the model's time or the writer's.
The writer chooses, and the choosing is the part of the work no model can do for them.
What comes back is more than a post. The main version sits in its own card, with a row of hashtags beneath it, five to eight that the model judges relevant to the topic. Below that, when the model offers one, is a short engagement tip: a sentence of practical advice about the post, such as when to publish it or what to ask the reader. Below that again is a card headed Alternative Versions, holding two other ways of saying the same thing, written by the same model in the same request. Each alternative has its own copy button, so the writer who prefers the second wording takes it in one press, and the one who prefers the first takes that.
This is the most honest thing about the room. A single generated post invites a writer to accept it or start again. Three versions side by side invite a comparison, and a comparison is where taste comes back into the process. The writer chooses, and the choosing is the part of the work no model can do for them. The copy button on the main post carries the hashtags with it, each written with its mark, so the clipboard holds a post ready to paste. The alternatives copy as text alone, which suits the writer who would rather choose the hashtags afresh.
A post worth keeping is saved with one press, and the app keeps it with everything that made it: the platform, the text, the hashtags, the tone and the original topic. Saved Posts sits beneath the settings and lists the twenty most recent, each marked with its platform and each with two quiet buttons, one to copy it again and one to let it go. A post deleted is gone at once, so the bin is for the post that has truly served its purpose. The room posts nothing itself. It writes, it keeps what the writer chooses to keep, and it hands the words to the clipboard, so the writer stays the one who decides when and where a sentence goes out under their name.

The people
A contact book that remembers what was said
Every writer who sells their own work keeps a list of people, and most keep it badly: in a spreadsheet that is never current, in an inbox that cannot be searched by intention, in a notebook that stays at home. The contact book in OmniWriter is a small, well-made version of the thing they meant to keep. It opens on four counts. One is everyone in the book. One is the active leads, the people who have shown interest and not yet gone further. One is the customers. The last is the pipeline, which is nothing more mysterious than every contact's estimated deal value added together, so a writer can see at a glance what the conversations in progress might be worth.
Beneath the counts are a search and a filter. The search matches a name, an email address or a company, so the bookseller can be found by the shop's name when her own has slipped the mind. The filter narrows the table to one status at a time. The table itself shows each person's initial, name and email, their company, their status, how they came to the book and their estimated value. A person without a company shows a quiet dash rather than an empty cell. A search that finds no one says No contacts found and waits.
A desk that deletes what it should only have rested is a desk that forgets.
Adding a person takes one form. Only two fields are required, a name and an email, because a contact book that asks for everything at the door is a contact book nobody fills in. The rest is offered and optional: a telephone number, a company, a status chosen from lead, prospect, customer or inactive, and a source chosen from six. The sources are the honest places a writer's people come from: the website, a referral, social media, cold outreach, an event, and other. There is a field for an estimated deal value and a larger one for notes. The same form, opened from the pencil on any row, edits the person, and it opens already filled with what the book knows.
Retiring someone is the gentler act, and the status is how it is done. A partner who has closed a studio, a buyer who has moved on, a lead who said no and meant it, each can be set to inactive. They leave the active counts and the lead filter, and their record and history stay exactly as they were, which is right, because a relationship that has paused is not a relationship that never happened. The bin on each row deletes a contact outright and at once, without a second question, so it is for the duplicate and the mistake. A desk that deletes what it should only have rested is a desk that forgets.
The history is where the contact book earns its place. Choosing any row opens a sheet from the side of the screen with the person's details and notes, and beneath them a section headed Activity. Add opens a small form: the kind of contact, chosen from email, call, meeting or note; a date, which starts on today; a subject, which is required; and room for details. Save Activity writes it into the person's history, and the history lists every entry newest first, each with an icon for its kind, the subject, the day and month, and whatever detail was written. A person with no history yet says No activity recorded yet. The sheet does not send the email or place the call. It remembers that it happened, and what was said, so that the next conversation can begin where the last one stopped.

The page that sells the book
A guided reading, three steps and a thank-you
The fifth door on the sidebar leads out of the private desk and onto the page the public sees. It is a long page for one book, and today that book is The Code, Volume I, subtitled The Living Ecosystem, a design language for software built around the human nervous system. The book's words are written into the page itself, its title, its chapters, its excerpts and its promises, so the page is a finished piece of work rather than a form to be filled in. A writer who means to sell a different book with it changes the page, and the page is arranged so clearly that the change is one of words rather than of structure.
It opens slowly. Two soft fields of colour breathe behind the title on a twenty-second cycle, rising and settling, and the book's description sits beneath in a serif. A single link carries the reader down to the purchase, and a quiet word at the foot of the first screen invites them to descend instead. Four cards then set out what the book is about, each with a small mark and two sentences, under a heading that calls them the soul of the text. They are Radical Calmness, Sacred Containers, Biological Entrainment and Developmental Hosting, and each names an idea from the book rather than a claim about the reader.
The excerpt is the argument, and the page lets the book make it.
The section that does the most work is called A Guided Reading. On one side is a short list of the book's five chapters, numbered, and on the other is a pane drawn to look like paper, with a fine grain and a turned corner. Choosing a chapter brings its number, its page range, its title, its subtitle and a passage from it into the pane, and the passage fades in rather than snapping. A reader moves through the book's argument in the order the author set, reading the book's own sentences rather than a summary of them. The excerpt is the argument, and the page lets the book make it.
Beneath the reading is a section for the words of readers, set as a row of quotations with a name and a role beneath each. The three standing there now are sample text written into the page, holding the place for reflections from people who have read the book, and they belong on a public page only once real readers have written them. The section is the frame. What fills it should be true.
The checkout is three steps rather than one form, and each step says one thing. The first, Gather, says what the reader is about to receive and lists what the book contains. The second, Commit, states the price plainly and says that it is a single payment with nothing recurring. The third, Receive, says that the reader will go on to a secure page to pay. A row of small marks above the steps shows where the reader is, and any step already passed can be returned to. The final button asks the house's backend to open a Stripe checkout for the book, which it does only for a reader who is signed in, with that reader's email already filled in. Cancelling there brings the reader back to the book page. If the house's payment key is not yet in the app's settings, the page says that checkout is not configured yet, in a line, and nothing is taken.
After a payment the reader lands on a short page headed Welcome to the Sanctuary. It says their copy is ready, thanks them for choosing to design with empathy, and offers a way back to the book. It is a calm place to arrive, and it does not ask the reader for anything more. The page closes, as the whole book page closes, on a single line from the book about designing for the exhale.

Every reader of a book was once a name in somebody's notebook. Here the notebook remembers what was said.

Across B-Corps
The desk among nineteen
B-Corps is nineteen applications that the house runs its own work on every day, installed side by side on the house's Mac. One desk starts them, opens them and rests them, and every two minutes it restarts any that has stopped, so a writer who opens OmniWriter in the morning finds it running. A stock-take of every application's records and functions is kept in one register, and OmniWriter's entry lists its records of contacts, conversations and saved posts, and the one function that opens the checkout. The house's reading room reads every application and every book, so it knows this desk as well as it knows the others. Each application keeps its own sign-in today, OmniWriter included.
OmniWriter sits in the publishing layer, and its neighbours are the tools that make the book it sells. Luminous BookFlow is a publishing house in software, where a manuscript becomes an edition. Audiobook AI prepares a book for listening. Chapter to Blog takes a book chapter by chapter and turns each into posts, and ContentSpark sets one source out across every channel and into a course. A person who keeps Chapter to Blog open beside OmniWriter can take a post made there, tighten its opening in the Writing Assistant, and write its announcement for one platform and one tone in the Post Generator. Nothing passes between them by itself. The suite is arranged so that a writer moves between the rooms in the order the work asks for.
OmniWriter is the small desk where one writer meets the world one sentence at a time.
Further out are the marketing tools, which work at a larger scale. SquareDash runs a whole website's pages, articles, search and social, and GrowthWrite gives a studio a blog that runs itself. OmniWriter is the small desk where one writer meets the world one sentence at a time. A writer whose house uses SquareDash for its site and GrowthWrite for its blog still needs a place for the post written this afternoon and the bookseller called at four, and this is that place.
Two more connections are matters of arrangement rather than code. The Luminous Book writes down a business's voice, and a writer who has that voice written down has a measure to hold the Writing Assistant's suggestions against: the model proposes, and the house's own voice decides. Resonance CRM keeps the senior seats a firm intends to reach inside one organisation. OmniWriter's contact book is its gentler cousin, built for the readers, partners and buyers of a writer's work, where the relationship is long and the deal is often a signed copy and an evening in a bookshop.

Who it is for
The writer who also has to sell
OmniWriter is for the independent author, the small press with one or two people in it, and the practitioner who has written a book as part of a larger practice. Each of them writes, each of them has to tell people the book exists, each of them keeps relationships that matter more than a mailing list, and each of them sells at least one book from a page of their own. They do not need a newsroom's editorial system or an agency's social suite. They need the four parts of the work in one place, done carefully, and they need to stay the author of every word that goes out.
What it replaces is a familiar set of tabs. A grammar checker that marks errors without saying why. A chat window used for posts, where every request begins from nothing and nothing is kept. A spreadsheet of contacts with a column called notes that grew until nobody read it. A storefront with a checkout bolted on, built in yet another program. Each of these does one part of the work, and none of them knows the others exist. The cost of that is not money. It is the small, constant effort of remembering where each piece is and carrying context between programs by hand.
It keeps the writer as the first reader of every sentence and the last word on every post.
What makes this desk different is the shape of what the AI returns and what the desk keeps. The Writing Assistant gives reasons with every suggestion, so the writer learns rather than merely accepts. The Post Generator gives three versions rather than one, so taste re-enters the process at the moment it matters. The contact book keeps a dated history of every conversation, so the relationship has a memory longer than the writer's. The book page lets the book's own sentences do the selling, and asks for a single payment with nothing recurring. None of this is elaborate. It is a small set of decisions, each made in favour of the person at the desk.
It is not a publishing platform and does not claim to be. It posts nothing to any social network, sends no email from the contact book, and holds no manuscripts. It keeps the writer as the first reader of every sentence and the last word on every post. For a person who writes for a living and sells what they write, that is the right amount of machine: enough to take the second reading and the first draft of an announcement off the desk, and no more than that.
How it is offered
Installed for an organisation, and kept
OmniWriter is offered to an organisation in three ways: on its own, as part of the publishing floor, or inside the whole of B-Corps, where every application on these pages is installed together, set up in the organisation's own voice and with its own records, and kept running for as long as the organisation keeps it. The house carries each application into its suite for good, so what is set up now is still there, and still mended, in the years after.
The fee reflects the work of installing and shaping it, and the size of the organisation it serves. It is set with each organisation, after a conversation about what the application will carry for it.
Arranged in conversationOmniWriter · B-Corps

The care it takes
Small decisions, made toward calm
The care in OmniWriter is in its refusals. The desk sits behind sign-in, and a visitor who has not signed in is sent to do so before any room is drawn; one who is not registered is told plainly that access is restricted and how to ask for it. The checkout will open a payment only for a reader who is signed in, and it fills the payment form with that reader's own address rather than asking them to type it again. The payment is a single one, and the step before it says so in words, so nobody discovers a subscription after the fact. A reader who changes their mind at the payment page is returned to the book, where they began.
The rooms are patient with empty states. A Writing Assistant with nothing in it says to enter text and press Analyze. A Post Generator with nothing chosen says to set a topic and generate. A contact with no history says no activity has been recorded yet, and a search with no match says so and waits. The buttons that would do nothing stay quiet until they can do something: Analyze until there is text, Generate Post until there is a topic, Save Activity until there is a subject. A contact asks for only a name and an email, and the Writing Assistant keeps no record of what was pasted into it, so a rough paragraph can be tried there without becoming part of anything.
The work stays the writer's, and the desk stays out of the way of it.
The book page moves slowly where it moves at all. The fields of colour behind its title breathe on a twenty-second cycle, the chapters fade into the paper pane rather than cutting, and the checkout's steps rise into place and settle. Its type is a serif for the voice and a plain sans for the furniture, the pairing the house uses for everything it writes. The colophon at the foot of every room names Luminous Prosperity, and the line beneath it, Wealth in Service of Light, is the house's own.
A writer who closes OmniWriter at the end of the day leaves behind a shorter paragraph, a post on the clipboard or in the saved list, a conversation written into somebody's history, and a page that will sell the book overnight to whoever reads far enough. The work stays the writer's, and the desk stays out of the way of it. That is the whole of what it promises, and it keeps it.
B-Corps
