
What it is
A studio's house, with a journal in it
A small studio usually keeps its public life in four places at once. The site lives with one company, the blog with another, the contact form sends its messages to a third, and the enquiries end up scattered through a mailbox that is also full of invoices. Growthwrite puts those four things under one roof. It is a studio's own website, its journal, the form a stranger uses to write in, and the inbox where that message is read and answered, kept together and kept by the studio.
It has seven pages, and they divide cleanly. Three front rooms set out what the studio offers, in words written directly into the page. A journal holds the studio's posts, written and published by whoever administers the site. Beneath every post an AI chooses what a reader might open next, and above it, for the administrator alone, an AI gives advice on search. A contact form sits at the foot of the front rooms, an inbox gathers every enquiry, and a quiet page builds a sitemap of the journal as a file to download.
It is a house for a studio's words and for the people who answer them, built so that the writing and the enquiries it brings in are kept in the same place.
The AI in it works at a modest and specific strength. It draws a cover for a post when the writer gives none. It reads the other published posts and scores which belong beside the one open. When asked, it suggests keywords, a meta description, a refined title and internal links, and applies none of them. The writing itself, the decision to publish, the answer to a person who wrote in: those stay with the people who run the studio.
What it is not is said as plainly. It does not publish to any network on its own. It sends no newsletter. It keeps no schedule, and it measures nothing about how a post is read or where it ranks. It is a house for a studio's words and for the people who answer them, built so that the writing and the enquiries it brings in are kept in the same place.

A day with it
Thursday, a studio of two and one essay
The studio is two people above a framing shop, and the partner who keeps its writing starts at half past eight with the site already open. Home loads under its fixed bar, the four doors across the top reading The OS, Journal, Linux and Apps, with Commission at the end. She reads the hero line the studio wrote last spring and decides, again, that it can stay. Then she presses Journal.
The journal opens on its own front page, headed The Garden Journal, with the posts laid out as cards, newest first. A row of tags runs above them, All at the start and then every tag the studio has ever used. She presses one, and the list narrows to the posts that carry it, then presses All again. Two cards are marked Draft. A reader arriving now would not see them; they show only because she is signed in as the administrator, and so does the button that reads New Post.
The day's writing is out, the day's two enquiries are answered, and none of it left the house to be done.
She presses it and the editor opens. She types the title of the essay she finished on the train, leaves the slug empty, leaves the status on Draft and the date on today, which the form has already filled in. She types three tags with commas between them, writes a two-sentence excerpt for the card, and pastes the body into the editor below, where a small toolbar offers headings, emphasis, a quotation, lists and links. She leaves the cover address blank on purpose.
Save Post changes its words to say that it is generating an image and saving, and for a little while nothing else happens. Then the journal returns, and her essay is the first card, carrying a cover she did not make: muted greens, a line of warm gold, a great deal of open space, an abstract form that suggests growth without drawing a plant. An AI drew it from the title, in the palette the studio's site already wears.
She opens the card. The reading page sets the cover at the top, then the tags, the title and the date with its Draft mark. Above the body, a panel only she can see is headed SEO Assistant. She presses Generate SEO Recommendations and waits. When it answers, the panel shows a refined title with its length counted beside it, a meta description of about one hundred and fifty-five characters, a row of keywords and three suggestions for linking this essay to older ones, each with the words to link from and a relevance score. She copies the description, opens Edit Post, pastes it over her excerpt, and changes Draft to Published.
Back on the reading page the Draft mark has gone. Below the body, under Continue Reading, an AI has chosen four older posts to sit beneath this one, each with its cover and its excerpt. Above the body sits a row headed Share This Post. She presses LinkedIn, and LinkedIn's own share window opens for her to write in.
At the foot of the page the comments wait. One approved comment from last week sits there with its reply indented beneath it, and above them is a test line her partner approved by mistake while trying the form. She deletes it from the small control beside it. Then she types the address of the inbox, which is not in the bar and is reached only that way.
Two enquiries carry a gold dot. She opens the first, and the dot goes as it is marked Read. The pane on the right shows the sender's name, an email address, the full date and the message, which asks whether the studio still takes on single essays. She presses Reply via Email, answers from her own mail program, comes back and presses Mark Replied. The second enquiry is her own test from Tuesday, and she deletes it after the page asks whether she is sure.
Last, she opens the sitemap page. It shows nothing at all, and a file called sitemap.xml arrives in her downloads, listing the journal and every published post. She sets it aside for whoever looks after the studio's domain. The day's writing is out, the day's two enquiries are answered, and none of it left the house to be done.

The front rooms
Where a studio says what it does
A visitor arrives at Home, and Home is a long page with a settled shape. A centred hero line leads, then a row of four figures, then a process told in three phases, a seed, a growth and a harvest. After those come the studio's tiers of work, six cards on what a client receives, a paragraph on who does the work, and at the bottom the contact form. Every word on it is the studio's own, and every word is written into the page's code rather than read from a record.
That fact matters for how the rooms are used. Changing the offer, a tier or a figure is an edit to the page itself, done by whoever keeps the site's code, and it is not a field to fill in on a busy morning. The front rooms are set the way a printed brochure is set: considered once, read many times, changed when the studio's offer changes. The journal is the part of the site that moves from week to week, and the front rooms are meant to hold still around it.
Nothing on these pages takes a payment or books a time; each door opens a conversation, and that is the whole of what the front rooms ask a visitor to do.
Two further rooms follow the same pattern for two lines of work. Apps sets out a practice of growing one application across iPhone, iPad, Mac and Vision OS, and it keeps the order Home has already taught the eye. Linux sets out a branded Ubuntu build, the studio's own version of the operating system with its mark on the boot screen and its programs installed from the start. A third room, called The OS in the bar, takes that build apart in four layers and describes each one in turn.
That last room is the most particular of the three. The root is the moment the machine starts, with Plymouth boot animations and GRUB menus set in the studio's type and colours. The canopy is the desktop itself, with GNOME or KDE shell extensions written for the studio's tools and the login screens redrawn. The flora is the visual system, GTK3 and GTK4 themes and a set of drawn icons that replace the defaults. The harvest is how it travels: a bootable ISO image and a private APT repository from which installed machines take their updates. The page describes the work. It does not build it, and nothing in Growthwrite compiles a theme or an image.
On Home there is also a drawer. A single button opens it to four package cards for larger and regulated work, and choosing one opens its description, its list of what is included and an inquiry button that writes an email. Choosing it again folds it away. Like the rest of the front rooms, the packages and everything claimed in them are the studio's own copy, set down in the page.
Every page sits under the same bar, with the current door underlined in gold and a Commission button at the end that opens a message to the studio's address. On a phone the bar folds away and the page carries on alone. The tier buttons across the front rooms are email links of the same kind. Nothing on these pages takes a payment or books a time; each door opens a conversation, and that is the whole of what the front rooms ask a visitor to do.

A draft is read by one person before anyone else. The journal shows it to the administrator, and to nobody else, until it is published.

The journal
Writing, keeping and retiring posts
The journal is the part of Growthwrite that lives, and it is built around one list. Its front page lays out every post as a card, newest first, with the cover, the date, the title, three lines of excerpt and the post's tags. A card without a cover carries a quiet leaf mark in its place, and a post not yet dated says Unpublished. While the list is loading, three pale cards hold its shape so nothing jumps when the posts arrive.
Above the cards, a row of tags is built from every tag on every post, with All at the start. Pressing one narrows the list to the posts that carry it, so a journal with years of writing in it can be read by subject as easily as by date. A reader sees published posts only. The administrator sees the drafts as well, each marked Draft, and a New Post button at the top. An empty journal says so in a sentence, and to the administrator it adds an invitation to plant the first seed.
It is a way to seed an empty journal, and it is not a journal that writes itself.
Opening a card opens the reading page. A line at the top returns to the journal, then come the cover, the tags, the title and the date, and the body is set below in a light, open hand for long reading. The page also writes the post's title into the browser's tab and places a description and a social card, built from the excerpt and the cover, into the page as it loads. A post opens inside the journal rather than at an address of its own, which is worth knowing before anything else in this section: a link to the journal arrives at its front page, where any post is a card away.
The editor is one form, and it holds everything a post is. A title is required; the slug may be left empty. Status is Draft or Published, the publish date defaults to today, tags are typed with commas between them, and there are fields for a cover address and an excerpt. The body is written in a rich editor with a toolbar for headings, bold, italic and underline, quotations, numbered and bulleted lists, links and images. Save Post keeps it and returns to the journal. Cancel leaves without saving, and nothing changes.
When a post is saved with a title and no cover, the editor asks an AI image model to draw one. The instruction is precise about the house's taste: muted forest greens, warm gold used as an accent, generous negative space, abstract organic forms, a calm that whispers rather than announces. The button says that it is generating an image while the picture is made, and the address of the finished image is saved with the post. If the drawing fails, the post is saved without it, and the writing is never held back for want of a picture.
Retiring a post is done in one of two ways, and both are deliberate. Setting a published post back to Draft takes it out of every reader's list while keeping it whole for the administrator. Deleting it, from the reading page, asks first whether the post should really go, and then removes it. Edit Post opens the same form with everything filled in, so revising last year's essay is the same act as writing a new one.
The code also holds one more piece of writing machinery, and it is described here at exactly its strength. A server function, which refuses anyone but an administrator, has an AI write five essays of eight hundred to twelve hundred words on five set topics about software that grows, draws a cover for each, gives all five the same four tags and publishes them together, dated the day it runs. No screen in Growthwrite calls it, and it keeps no schedule. It is a way to seed an empty journal, and it is not a journal that writes itself.

Being found
Search advice, what to read next, sharing
Above the body of every post, for the administrator alone, sits a panel called the SEO Assistant. It does nothing until it is asked. Pressing Generate SEO Recommendations sends the post's first two thousand characters to an AI with an instruction to keep the language considered, and the AI returns eight to twelve longer keywords, a meta description of about one hundred and fifty-five to one hundred and sixty characters, and a refined title of fifty to sixty that keeps the original's manner.
A second call follows at once. The AI is shown the titles of up to ten other posts and asked which three to five this post should link to, and with what words. The panel sets all of it out: the refined title and the description, each with its length counted beside it and a button that copies it, the keywords in a row, and the suggested links, each with its anchor text and a relevance score out of a hundred. The server refuses the request from anyone but an administrator, whatever the screen shows.
Advice that has to be chosen before it is used is the only kind a careful writer would want, and this is the only kind it gives.
The assistant changes nothing in the post. A writer who likes the description copies it into the excerpt by editing the post, and a writer who prefers her own title keeps it. Each run is saved as a new record in the site's data, so the history of the advice is kept, but the panel itself starts fresh every time it is opened. Advice that has to be chosen before it is used is the only kind a careful writer would want, and this is the only kind it gives.
Beneath every post, under Continue Reading, a second AI works without being asked. Each time a post is opened, a server function sends its title, tags, excerpt and opening to an AI along with up to fifteen other published posts from the fifty newest, and the AI scores each one for how closely it belongs beside this one. The four that score highest are shown with their covers, titles and excerpts and a line that reads Read Article. When nothing comes back, the section is simply not drawn. Those links, like every link into the journal, open its front page, where the chosen post is waiting among the cards.
Sharing sits in a row above the body, headed Share This Post. X, which the button still calls Twitter, opens a new post carrying the title and the address. LinkedIn opens its own share window with the address. Email opens a new message in the reader's own mail program, with the title as its subject and the excerpt and the address in its body. The address carried is the one in the browser at that moment, which is the journal's. Nothing is posted by Growthwrite; every share is finished, or abandoned, by the person who began it.
The last tool for being found is the plainest. Opening the sitemap page builds an XML file listing the journal and every published post, with each post's last change as its date, the journal marked to be read weekly and the posts monthly. It arrives in the browser as a download called sitemap.xml, and the page itself shows nothing. The addresses in the file are written against one domain fixed in the code. It is a file for a person to place where search engines will find it, not a page that search engines read on their own.

The answering room
Comments, the form and the inbox
A journal that nobody can answer is a noticeboard. Growthwrite gives readers two ways to answer: in public, beneath a post, and in private, through the contact form. Both are built to be read before anything is done with them, which is the habit of a studio that would rather answer one real person well than collect a hundred anonymous lines.
At the foot of every post a reader leaves a name, an email address and a comment, and presses Post Comment. The comment is saved as pending, and the reader is told plainly that it has been submitted for moderation. Nothing a stranger writes appears on the page until it has been approved. Approved comments are shown newest first, each with its author's name and date, and each has a Reply line beneath it. A reply is set in under its parent and indented by its depth, so a conversation reads as a conversation, and the administrator sees a small control beside every shown comment to remove it.
The enquiry is kept before anything is sent about it, so a notice that goes astray costs nothing but a moment's delay; the message is still in the inbox.
Approval itself is not a screen in Growthwrite, and the page would mislead if it suggested otherwise. A comment moves from pending to approved in the site's own records, outside these pages, and until someone moves it the comment simply waits. The record has room for more, a rejected mark, a spam mark and a flag for pinning a comment to the top, and the code holds those places without yet using them.
The contact form sits at the foot of Home, Apps and Linux, and asks for three things, a name, an email and a message, each required. It also carries a field nobody sees. A person filling the form never meets it; a program that fills every field it finds fills that one too, and when it is filled the form quietly sends nothing. When an honest message arrives, it is saved first as a new enquiry. Only then does a server function send an email notice, with the sender's name, address and message and a line to reply to them, to one address written into that function.
The order of those two steps is the important part. The enquiry is kept before anything is sent about it, so a notice that goes astray costs nothing but a moment's delay; the message is still in the inbox. The address the notice goes to lives in the code, and a studio sets its own there before it relies on it. When both steps finish, the form clears and thanks the visitor in one line. When either does not, it keeps its fields and offers no false thanks.
The inbox is a page for the administrator, reached by its address and kept out of the bar. It lists every enquiry newest first, each with a gold dot while it is unread, the sender's name, the opening of the message, the date and a status of New, Read or Replied. Opening an enquiry marks it Read. The reading pane beside the list gives the name, the email, the full date and the whole message as it was written, line breaks kept. Beneath it are four plain verbs: Reply via Email, which opens a message to the sender in the studio's own mail program; Mark Replied; Mark Unread, for the message that needs a second look tomorrow; and Delete, which asks first.
Anyone else who finds the address is told in one line that the room is kept for administrators. An inbox with nothing in it says that there are no submissions yet. That is the whole room, and it is enough: a studio can see at a glance who has written, who has been answered, and who is still waiting.

An enquiry is kept before anything is sent about it, so the inbox holds the message even on a day the email never arrives.

In the suite
How it sits among the rooms of B-Corps
Growthwrite is one of nineteen applications that make up B-Corps, and it runs the way the others run. Each is installed on the house's own Mac by its own documented method, each against its own cloud backend, side by side on one desk that starts, opens and rests each application, and every two minutes restarts any that has stopped. A stock-take of every application's records and functions is kept beside them, and Growthwrite's entry in it lists its six records and the calls it makes. It keeps its own sign-in, as every application in the suite does today.
Its place in the suite is at the outer edge of the publishing layer, where the house's writing meets a stranger. Chapter to Blog turns a book into a set of posts, one chapter at a time; a person who keeps both open can carry a finished post from there into this journal's editor and publish it under the studio's name. ContentSpark sets one source out across every channel, and a journal post here is exactly the kind of source it was made for. OmniWriter is a writer's desk for one author's work and the people around it; Growthwrite is the studio's house that a writer's work can be published from.
None of these connections passes data on its own today.
The voice of the house is kept elsewhere, and this application is arranged to be written against it. The Luminous Book reads a business and writes its voice down, and a studio that has done that work there holds both its front rooms and its journal posts against that written voice before they go out. SquareDash plans a site's pages, articles, search and social presence in one marketing workspace, and a studio that plans there and keeps its own site here carries the plan across by hand, post by post.
The people who write in belong somewhere as well. An enquiry answered in this inbox is, very often, the first conversation with a future client, and the outreach sheet in Resonance CRM is where a firm keeps the people it intends to stay in touch with; a person who works both enters the sender there by hand. B-Corp, the foundation of the suite, holds the record of the organisation itself, its people and its teams, and that record is the studio on whose behalf this site speaks.
None of these connections passes data on its own today. Each is a way the suite is arranged to be used by a person who keeps more than one room open, and the page says so in the same words the code would.

Who it is for
A studio that would rather keep its own house
Growthwrite is for a small studio, a consultancy or a practice run by one or two people, whose site has to say what they do and whose writing is part of how they are found. It suits a place where the person who writes the essays is also the person who answers the enquiries, and would rather do both from the same chair than across four services with four logins and four ideas of who the studio is.
It replaces a familiar arrangement. A site built in one service, a blog kept in another, a form service that forwards messages, and a mailbox where those messages compete with everything else: four accounts, four sets of settings, and nowhere that shows, in one list, who wrote in and whether anyone answered. Here the site, the journal, the comments and the enquiries are records of one application that the studio keeps, and the inbox carries a status on every message.
The front rooms are written by the people who run the place, and the journal's posts are written by them too; the AI is set to draw covers, advise on search and choose related reading, and it is not set to speak for anyone.
It is different in three particular ways. The first is that the studio's words stay the studio's. The front rooms are written by the people who run the place, and the journal's posts are written by them too; the AI is set to draw covers, advise on search and choose related reading, and it is not set to speak for anyone. The single function that writes essays exists to seed an empty journal and is reached by no screen.
The second is restraint about the reader. Comments are held until approved, the contact form screens out the simplest programs without asking a person to prove anything, and nothing a visitor writes is put on show by default. The third is that the AI's work is always visible as what it is. The search advice is shown field by field with its lengths counted, and applied only when a person copies it. The related posts are scored and shown, and the cover is drawn only when a writer leaves the cover blank. A studio can see exactly where the machine has been and decide what to keep.
What it asks in return is modest and specific. Someone keeps the front rooms' words up to date in the page's code, someone approves comments in the site's records, and someone checks that the notice address in the code is the studio's own. Those are the tasks of a studio that looks after its own house, and the house is built to make them small.
How it is offered
Installed for an organisation, and kept
Growthwrite 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 conversationGrowthwrite · B-Corps

The care it takes
What it holds back, and what it keeps
Most of the care in Growthwrite is in what it declines to show. A draft is visible to the administrator and to no one else until it is published. A comment waits as pending until it is approved, and an unapproved comment is never drawn on the page. The tools for writing, for search advice and for removing things appear only to an administrator, and the two server functions that write, the search advice and the five essays, refuse anyone else on the server whatever the screen shows.
The rest of the care is in what it keeps. An enquiry is saved before any notice is sent about it, so the record survives a failed email. A post is saved even when its cover cannot be drawn. Deleting a post or an enquiry asks first, in a sentence, and a message opened by mistake can be marked unread again. The search assistant writes its advice down as a record each time it runs and changes nothing in the post it reads. Every share is begun in the reader's own window or mail program and finished there; the application posts nothing anywhere.
The writing goes out under the studio's own name, and the answers come home to the same place.
Some things are said here so that nobody discovers them later. A post opens inside the journal and has no address of its own, so a link from a share, from Continue Reading or from the sitemap opens the journal's front page. The sitemap is a file to download, built against one domain written into the code, and the description and card tags are written into the page by the browser after it loads. The rich editor's toolbar stores formatting that the reading page, which reads Markdown, is not shown to render. The pages move as they appear, rising and breathing gently, and they do not yet quiet that motion for a person who has asked their device for less.
The figures, timings and claims on the front rooms are the studio's own copy, typed into those pages, and this page repeats none of them. They belong to whichever studio keeps the site, and they are its to write and its to keep true.
What remains is a plain and useful thing. A studio has a house with its offer in the front rooms, its writing in the journal, and the people who answered it gathered in one quiet list, each with a mark that says whether they have heard back. The writing goes out under the studio's own name, and the answers come home to the same place.
B-Corps
