Jyro.ai / Historical SaaS product
2023Public walkthrough · November 15
Creator · team-built product
From free credits
to paying users.
Built in 2–3 days.
A recurring editing problem inside a writing agency became a product for other writers. Noah and his team built Jyro to rewrite articles with their surrounding context in mind, while handling embedded links separately.
Explore the editing workflow01 / The business problem
A recurring editing
bottleneck.
The agency’s writers researched and drafted articles before editors refined the language. Noah wanted to reduce the routine work between those stages while retaining the article’s meaning and useful links.
Rewriting an isolated paragraph could change its meaning enough to clash with the surrounding article. Jyro supplied the article title, relevant headings and preceding paragraph as context for each edit. Links needed their own treatment so a rewrite did not disconnect useful references from the words they supported.
02 / How it works
One article.
Context for every edit.
Follow the main path, then explore the branch for text containing links. The technical map includes the repeated editing pass.
A shared document is copied, edited using article context and returned for review, with a separate path for hyperlinks.
03 / Implementation
The context.
The document structure.
The visible progress.
Work from a copy of the article
A user shared a Google Doc with viewing access and submitted its URL through a web form. The described workflow made a copy, retrieved its content and inspected the paragraph and text structure before editing.
Give each paragraph the surrounding story
The editing prompt received the title, parent heading, subheading when present and previous paragraph. It asked for clearer, tighter wording while keeping tense consistent. The text allowance varied with the passage’s length.
Handle hyperlinks through a dedicated branch
The Make workflow separated normal text from hyperlink text. Noah’s demonstration shows a branch retaining the hyperlink’s name and URL; he describes applying the destination to relevant rewritten text. This was an important document-handling problem, beyond asking a model to rewrite prose.
Show what is changing
The selected text span was highlighted in purple. Document API calls replaced that span with the new version, cleared the highlight and continued through the article. The visual cue made the current editing step visible to the user.
04 / Product launch
A fast build.
Real willingness to pay.
In the public walkthrough, Noah says his team built the product in roughly two to three days, advertised it to freelancers across multiple platforms and received signups on the day of launch. He also reports that users consumed their free credits and purchased additional credits.
The build time and customer response are reported in Noah’s walkthrough. No revenue total or conversion figure is published.
Noah explains the product direction and contextual editing approach as part of a team effort to build and launch the tool.
05 / Quality and historical context
An editing assistant.
Review still matters.
Development involved more than fluent rephrasing. Earlier walkthroughs show work on paragraph boundaries, document positions and editor feedback, alongside link-replacement and formatting defects.
Those challenges explain why the edited copy still needs a person to check its meaning, references and layout. The product assists the editorial process; it does not replace the final quality decision.
This is the historical Jyro.ai. It is separate from the later Jyro application, and Noah says it was already no longer live when this walkthrough was recorded.
06 / Historical walkthrough
Inside the product.
Source walkthrough published November 15, 2023
Noah’s original walkthrough covered the agency editing problem, the context supplied to each edit, the reported launch response and the Make workflow.
- The editing problem: preserve meaning and use relevant context during revision.
- The launch account: distinguish Noah’s reported response from independently verified product results.
- The workflow: document intake, structure and an iterative editing loop with human review.