The blank box had excellent PR
Writing software has spent years treating an empty rectangle as freedom. It is not freedom when the brief is in one document, the useful detail is in someone’s head, and the source is in the tab you closed. It is administrative hide-and-seek with a cursor.
Payments makes that problem louder. A case study needs evidence, a research paper needs sources, an RFP needs row-by-row coverage, and a press release needs the news before the victory lap. Yet each job usually arrives at the same blank box and receives the same heroic advice: start typing.
I stopped designing a better blank box
I built Juno around the job before the sentence. Choose what you are making and the surface changes with it. Ten writing workflows ask different questions, keep different evidence close, and review the draft against the assignment it is meant to finish.
That distinction sounds obvious, and so does labelling the fire exit. Both become interesting when somebody forgets.
The interface had to make the argument
The homepage does not explain this with a diagram wearing business casual. Its ultramarine field is made from writing fragments and currency marks. Move through it and the characters give way, then press and hold to turn the field into paper while the rings gather. Release, and the system snaps back with a ripple.
Below it, the same idea becomes product structure. Brief, research, and draft are visibly different states. Ten Greek gods, redrawn as aggressive ASCII portraits, guard ten purpose-built writing surfaces. It is a little theatrical because payments writing has survived enough grey rectangles.
The boring rules became the product
Juno runs without an account for now, drafts can stay local, and sources remain attached to claims. Eight surfaces can prepare a complete, reviewable packet for ChatGPT or Claude without putting the draft into a URL, while RFP and Carousel stay inside Juno by design.
The Profound-compatible connector is equally specific. It works only when an operator supplies an authenticated gateway and the user has access. That sentence is less exciting than “one-click integration,” which is precisely why it is true.
What exists, and what I am not pretending exists
The public product is live. Ten workflows, local-first saves, Ideas, voice controls, citation-aware research, Journal, review, versions, export, and the external handoff flow are implemented. The homepage and its interaction system have passed desktop, mobile, keyboard, reduced-motion, build, isolation, and regression checks.
There is no public adoption number here, no customer logo, and no miraculous percentage. Juno is evidence that a writing product can begin with the shape of the work and still leave room for the writer. Business impact needs real users and a measurement window. Until then, the honest result is the thing itself.