← Pruta AI

What we’ve built

Before and after.
Real businesses.

See what we built for two real clients: how their operations worked before, the systems we put in place, and what changed for their teams.

Business names and identifying details are withheld for privacy.

A rich content website

From a struggling website to a connected content operation.

This established website had an extensive library of original material and an international audience. Keeping it running meant coordinating writing, translation, development, editing, marketing and outside security support. Its manager describes how that operation changed.

Before

The manager recalls repeated website crashes and security incidents, expensive maintenance and content arriving late. The work was spread across remote staff and suppliers: writing and news research, translation, development, SEO, graphics, video and distribution. Financial pressure made that arrangement harder to sustain.

After: what we built

A new foundation for the archive

Using AI coding tools, we began replacing the WordPress site. Over several months, the work produced a new website and content-management system, with language editions, article categories and a home for video and audio.

Original material becomes readable content

The operation starts with its own source library. The manager describes connected agents that find relevant topics, draw on that library, prepare articles and images, and support video editing. Translation tools create language editions from the source article.

Content reaches the audience

The manager describes another part of the workflow adapting articles for messaging groups and social channels, linking readers back to the site. He says a conversational bot answers questions from the original content library and is identified to readers as a bot.

The weekly print edition returns

The printed newsletter had stopped when staffing and production costs became too much. The manager says AI now assembles it from that week’s website content, with a richer design, games and additional features, at a fraction of the previous cost.

The workflow we built

From source material to an audience

  1. Find the material

    Connect a relevant topic with the website’s own archive and source material.

  2. Prepare the article

    Turn the material into a readable piece with supporting images and an appropriate category.

  3. Translate and adapt

    Create language editions and shorter versions suited to messaging and social channels.

  4. Publish and distribute

    Put the content on the site and bring readers back through the connected distribution channels.

The human responsibility

The manager remains responsible for the operation, its source material and editorial standards. In his account, routine work now runs largely unattended, with periodic oversight. The print newsletter also has a review step before distribution.

The result

The manager reports more frequent publishing, better images and translations, readers commenting on the improvement, and the return of the weekly printed newsletter. He describes a smoother website and substantially lower operating costs.

Operating improvements and cost comparisons reflect the manager’s firsthand account; savings have not been independently measured.

Back to the stories ↑

A subscription research business

The author writes. The publishing workflow carries it through.

For a subscription publication, the report is only part of the job. It also needs a readable layout, a place in the member library and a way to tell subscribers it is ready.

Before

An established institutional research firm had opened a newer retail subscription service. According to the project owner, the team was learning report-design software, website publishing and consumer marketing while subscriber numbers were declining. The retail service needed its own operating workflow around the author’s research.

After: what we built

From document to branded draft

The intake accepts a document or report text. It prepares a branded PDF and a subscriber summary, and shows both to reviewers.

An approval that triggers the next steps

An authorized reviewer replies with the approval instruction. The publishing tools then prepare the member-site entry and trigger subscriber email and push alerts.

A member experience around the report

The website includes a report library, account access and Q&A reading pages. Download tools add a member-specific watermark to PDFs. Localized titles and summaries support the site’s language editions.

The workflow we built

Following one report from draft to members

  1. Send the report

    The author provides the document or writes the report in an email.

  2. Check the draft

    Reviewers see the formatted PDF and the summary intended for subscribers.

  3. Approve publication

    An authorized reviewer gives the explicit approval the workflow expects.

  4. Publish and notify

    The publishing process updates the site and sends the report alert to entitled members.

The human responsibility

The author owns the research and its conclusions. Reviewers approve what will be published. Subscriber research questions go back to the author; the operating tools do not invent answers or make investment decisions.

The result

The workflow has produced branded report files and a connected member library. Publication and distribution steps are built around the same approved report, with separate test behavior for rehearsals.

Language support varies by report, with localized titles and summaries available alongside the original research.

Back to the stories ↑

Start with the work

What keeps passing
from desk to desk?

Bring us the job you want done. We’ll help you work out where an AI employee fits.

Get a free AI assessment →