Karol Leszczyński Build & Develop PL

Smart-Copy — from topic to published article with not a single manual step along the way.

My own product: you give it a topic and the system finds sources, reads them, drafts an outline, writes section by section, adds an image and publishes the finished post. The same backend serves the panel, the mobile app, a public API and no-code integrations.

178
texts delivered out of 190 ordered
1.6M
characters of ordered content
7
steps between topic and publication
6
ways to order a text

The problem

Generated text is not yet a published article.

Between the two lie research, an outline, an image, formatting and pasting it all into your site. Generators deliver the middle of that road and leave the rest to the user — and the rest is what takes the most time.

  1. 01

    The generator hands over text and stops there

    You get paragraphs in a browser window. Publication still needs an image, formatting, pasting it into the site and checking whether it is actually about anything.

  2. 02

    The model writes from memory, not from sources

    Without reaching for material you get text about everything and nothing: plausible-sounding, but without a single number, name or detail that would have required looking anything up.

  3. 03

    A long text doesn't fit in one pass

    In longer forms quality drops halfway through, threads start to repeat, and the ending summarizes what has already been said. You have to write in pieces and keep watch over the whole.

  4. 04

    A subscription for something you use in bursts

    These tools sell monthly bundles, while real work looks different: ten texts in one week, then a month of nothing. There you pay for access even when nothing gets written.

The solution

One order, seven steps.

Each step does one thing and passes the result on. It is far more work than a single model call, but it is the only way to get text that stands on its own without edits.

Research before writing

The system drafts queries, searches for sources, fetches their content and keeps the ones that actually add something to the topic. Only from that material does the outline get built.

Writing section by section

The text grows piece by piece along an approved outline. That is why the last paragraph holds the level of the first instead of summarizing what was just said.

Image and publication in the same run

At the end a featured image is generated, and the finished post can go straight to WordPress. Between the topic and the published article there is no manual step.

Pay per character, not per month

Each order is charged against your balance. When a generation fails, the funds come back automatically — no support ticket needed.

From the product

What it looks like in practice.

Two views: the process as the user sees it, and the same order placed from someone else's application.

Smart-Copy — Seven steps, watched live
Seven steps, watched live Query creation, source search, content fetching, source selection, outline, section writing, featured image. Alongside: a progress percentage and estimated time, with a publication confirmation at the end.
Smart-Copy — The same thing in one call from your application
The same thing in one call from your application Topic, length, language and text type. The response comes back over a webhook, so there is nothing to poll in a loop. Test keys are free — you can build the integration before spending a single złoty.

The hard part

Where I got stuck the longest.

  • Keeping the text coherent when it's written in installments Writing in sections solves the quality drop but creates a new problem: each section is written on its own and does not know what the others said. Without passing along the outline and a summary of what has been covered, the text starts repeating itself or contradicting itself by part three.
  • Telling a source from junk The search engine returns a list of URLs, half of which are pages with no substance, aggregators of other people's texts or ad copy. A separate stage evaluates the fetched pages and rejects the ones with nothing to take away — otherwise research makes the text worse instead of better.
  • Refunds when something breaks midway The process has seven steps and every one of them can fail: a source stops responding, the model returns a malformed answer, WordPress refuses the connection. Since the balance is charged up front, a failure has to return the funds on its own — otherwise the user pays for nothing and writes me an angry email.
  • Six entry points, one engine The panel, the mobile app, the public API, Zapier, n8n and the WordPress plugin. Each authenticates differently and expects different responses, but all of them have to order the same text through the same queue — without duplicating the logic in six places.

What's in it for you

A product other systems plug into.

An application with a public API is a different level of commitment than a panel for your own users: endpoints have to stay stable, responses predictable, and errors described so that whoever is on the other side knows what to do. Smart-Copy went down that road together with no-code integrations and a plugin for someone else's system.

If you are thinking about a product that machines should be able to use too — or about wiring an existing tool into whatever your team already works in — write me how it should work.

Related services

What I do beyond my own products.

Smart-Copy is a web application with a public API and no-code integrations. Below, the rest of what I do for companies, with starting prices.

Let's talk

Need a product other systems can connect to?

Describe what it should do and what needs to connect to it. I'll reply with how I'd split it into stages, what a public API requires and roughly what maintenance would cost.