Which growth tactics can one founder actually finish?

Most growth advice was written by people with a team, for people with a team. The assumption is rarely stated. It sits in the last paragraph, where the tactic turns into a workflow, a process, a thing somebody owns. globalize.now is AI-powered localization infrastructure, and the question on this page is narrower than the advice: of the tactics on your list, which ones can one person carry to a finish?

Two pages answer the neighbouring questions and this one does not repeat them. Whether translated pages help you in search, and what has to be true technically, is does localizing your app help SEO. What the localization playbook earned and what running it used to cost is the growth playbook then and now. This page is about sorting your list before you pick.

What separates a tactic you can finish from one you cannot?

Whether the work ends.

That is the whole test, and it has nothing to do with difficulty. Rewriting your landing page is hard and it ends. Answering every support ticket in four languages is easy and it never ends. A tactic that resolves into a steady state with no person standing in it is finishable by one person. A tactic that resolves into a queue is a hiring decision wearing a growth-tactic costume.

Upside is the wrong first filter, because upside is what the advice already sold you on. Ask who keeps it running.

What does a team-shaped tactic look like in practice?

A recurring loop with a deadline attached to every product change.

The best-documented example of localization as a growth channel is Smallpdf's. As reported by OneSky's published case study for Smallpdf, re-fetched on 1 October 2026, monthly users over search rose 60%, from 6 million in 2016 to over 9.5 million in 2017, over 70% of users were from non-English-speaking countries, and Thai grew fastest, with the user base there up over 500% in one year. That is a vendor's account of one customer over one year, not a general rule, and it is the strongest public evidence this tactic has.

Now read the operational sentence from the same source, which nobody quotes: translation requests for new features and site improvements were processed within one to two days for all 17 languages. Speed is being sold there, which tells you the loop ran every time the product moved.

That is the shape of a team-shaped tactic. The cost is not the invoice. It is that shipping a button also meant shipping a translation request, permanently. A founder with no localization function reads that, agrees with the strategy, and does nothing. Correctly, because what was described was not available to them.

Can one person actually finish this one now?

One developer published his own numbers, and they are worth reading with the caveats attached.

Ken Imoto translated his blog at kenimoto.dev into four languages through what he describes as a cross-language LLM pipeline, hand-edited afterwards for register and locale: Brazilian versus European Portuguese, LatAm-neutral versus Spain Spanish. Over 22 days, from 30 April to 21 May 2026, his GA4 figures as published on dev.to and re-fetched on 1 October 2026 were: Portuguese 748 pageviews and 709 sessions, English 195 pageviews and 176 sessions, Japanese 27 pageviews and 29 sessions, Spanish 7 pageviews and 7 sessions. In his own words: "That is Portuguese pulling roughly 3.8× English, 28× Japanese, and 107× Spanish on the same blog, same publishing cadence, same author."

Read that as a snapshot across four languages at one moment, because that is what it is. There is no before-and-after on the same content and no pre-localization baseline was published. The article counts differ, 26 in English, 25 in Japanese, 17 in Portuguese, 10 in Spanish, and he gives no per-article normalisation, so do not invent one.

And Spanish did not work. Seven pageviews in three weeks, from ten articles. He attributes that to distribution rather than to the language, saying he had no Spanish-language community to post into the way he had for Portuguese. Whatever the reason, the honest reading of this data is that one of the four bets lost.

What makes it relevant here is not the multiple. It is the staffing: one person, no vendor, no standing queue, and a public number at the end of it.

Why does so much growth advice fail this test?

Because the people writing it had colleagues.

Tooling in this category grew up serving localization managers, and the content grew up alongside the tooling. When the reader is assumed to have a function, "and then you'll need a workflow" is a sentence that costs nothing to write. For a one-person team it is the sentence where the tactic dies, and it is almost always the last one.

The interesting change in 2026 is not that the tactic got better. Nothing about the strategy has moved since 2017. What moved is how much of it one person can carry to the end.

Which tactics are still team-shaped in 2026?

The ones whose unit of work is a page rather than a decision.

Localazy runs a version of the localization growth play as a page matrix rather than a translated product. A sitemap fetch on 28 August 2026 counted 757 conversion pages and 1,705 language-pair pages, roughly 14,000 indexed URLs in total, and a SpyFu pull on 23 September 2026 put 4,859,220 in summed US monthly search volume across its top 500 keywords.

That works, and it is not available to you on a Saturday. Thousands of generated pages is a build with a content plan attached, and it needs someone maintaining it after launch. Do not read this section as a suggestion to go and make 14,000 pages. Read it as the honest half of the argument: tooling did not turn every tactic solo-shaped, and anyone telling you it did is selling something.

How do you apply the test to your own list?

Write one sentence per tactic, starting with "and then someone has to".

If you cannot finish that sentence, the tactic ends and it is yours to finish. If it completes easily (and then someone has to update it, chase it, re-run it, answer it), you have just written a job description, and on a one-person team you are the candidate.

Then check your analytics before you check anyone's market-size list. Countries already sending you traffic while your product speaks only English are demand that arrived despite a barrier, which makes the barrier the variable you can move. Two languages, nothing else changed, one quarter of data.

What does the localization one cost now?

The recurring part stops being the project.

globalize.now converts a codebase once, in the in-app connect flow. That conversion is a single operation, not something that runs on a schedule. Push jobs translate new catalog units as they appear afterwards, and the files you get back are standard JSON or PO, the same formats your i18n library already reads. Nothing about your runtime, framework or deployment changes. The developer and vibe coder pages cover the setup.

Pricing is on the pricing page and this page is not going to paraphrase it.

What we cannot tell you yet

We do not have our own numbers for this, and we are not going to imply them.

Two customer case studies are being measured now. Until they are finished and dated, every figure on this page belongs to somebody else and is labelled with whose it is and when it was checked. A growth claim without a dated, checkable source is exactly the kind of number that gets quoted back at you a year later, and this category already has plenty of those.

Where this leaves you

Sort by who has to keep it running, not by what it might return. The tactics that end are the ones a founder alone ever finishes, and localization moved across that line recently enough that most of the advice about it has not caught up. If your analytics already show people arriving from places your product does not speak to, connect the repository and start with two languages.