Turning your travel knowledge into a city guide people pay for

You have a saved map with a hundred and forty pins on it. Some of them are places you loved, some are places you walked past twice and never went in, and eleven of them are the ones you actually send people. Every few weeks someone messages to say they are going, and you spend twenty minutes rebuilding the same list from memory, slightly worse each time.

Why the shared document stops working

The first version of every travel guide is a document you resend. It is free, it is generous, and it has three problems. You cannot tell who used it, you cannot correct it once it has been copied, and you have quietly taken on the job of a concierge for anyone who ever followed you. The generosity is real. The system is not.

There is a harder problem underneath, and it is the reason travel products are more work than they look: cities change faster than files do. A restaurant closes in March, a museum moves its late opening, a neighbourhood that was quiet is suddenly the one everybody posts about. A guide is not a book you finish, it is a thing you maintain, and the maintenance is the actual product.

There is also a limit to what you can honestly promise. You are not a booking agency, you do not know what someone's four-year-old will tolerate, and you cannot guarantee that the place you loved in October will be good in February. Saying so on the product page does not weaken the offer. It is the difference between a guide by a person who has been there and a listicle assembled from other listicles.

Same knowledge, two containers

Nothing about the content changes when you charge for it. What changes is that it becomes maintainable, and that the people using it are people you know about.

Building the first guide

Do one city, the one you know best, and resist the urge to cover a whole country. Depth is the only thing you have that a search engine does not. Set it up as a digital download so it delivers instantly and can be replaced later.

1. 1Choose the trip, not the city: three days in Lisbon without a car, or a long weekend in Rome with a toddler. Specific beats comprehensive.
2. 2Write the itinerary as days and half-days with times, walking distances and what to book ahead. Sequence is the thing people cannot get elsewhere.
3. 3Cut ruthlessly. Two dinner options per night, not seven. You were hired for the decision, not the shortlist.
4. 4Add the things only a regular knows: which entrance has no queue, which market day ruins the parking, the tram that is a tourist trap and the one that is genuinely useful.
5. 5Include a map link and an offline-friendly version, because phone signal abroad is not something you can assume.
6. 6Put a "last checked" date on the first page and the version number in the file name.
7. 7Write the product description as the trip it plans, not as the city it covers, and say plainly what it does not include: no bookings, no hotel deals, no affiliate placements unless you disclose them.
8. 8Buy it yourself on your phone and read it the way someone reads on a plane with a dying battery.

How the numbers tend to shape up

Picture a three-day guide at £12, published six weeks before the season people actually visit. If nine copies sell in the first month from your own audience, that is around a hundred pounds and it is not the interesting part. The interesting part is that nine strangers told you which city they are going to and paid to find out what you think about it, which is a much better research signal than any poll you could run.

In autumn you spend an afternoon checking the list, drop the two places that closed, add three that opened, and replace the file. Everyone who bought in spring now has the autumn edition. Next year you write the second city, and the nine people from the first one are already in your customer list to tell. Whether nine becomes ninety depends entirely on your audience and your work, and nobody can promise you that.

The mistake most travel creators make

They write the guide the internet already has. Ten things to do, one paragraph each, a photo of the famous square, no opening hours and no point of view. That document is free everywhere, and it should be. Your version has to contain the sentences a search result will never write: this one is worth the queue and that one is not, go on a Tuesday, eat before you arrive, skip the tour and walk the same route yourself in forty minutes. Opinions are the product. The second mistake is covering everywhere at once, which produces a guide that is thin about eight cities instead of definitive about one.

The free itinerary that feeds the paid one

List a single perfect day as a $0 product. It delivers exactly like a paid one, to its own order page, and it adds the person to your customer list with everything they downloaded attached. People who use a free day in your city and enjoy it are the most likely buyers of the three-day version, and you can see the pattern rather than guess at it once you have per-product analytics from Starter upwards. Keep the free one genuinely good; a deliberately weak sample teaches people your paid work is weak too.

The guide is already written. It exists in the messages you have sent, the pins you have saved and the answer you give every time somebody asks where to eat on the second night. Putting it in one file with a date on it is mostly an act of tidying, and the tidying is what makes it worth paying for.