When we launched Weshare last week, we shipped with sixty-something FAQ entries before our first rental ever happened. From the outside this might look backwards — usually FAQs grow organically from real customer questions. We wrote ours into the empty room. Here’s why, and what the writing process actually taught us.
The Bangkok rental problem we’re trying to solve
Most things in your home get used a few times a year. Camping gear, a DSLR, a power drill, a karaoke machine, a stand-up paddleboard. People in Bangkok have these — and people in Bangkok need them, sometimes for one weekend in Hua Hin or one shoot at Wat Arun. But the matching is broken. You either buy something you’ll use three times (terrible economics, terrible for storage in a 30-square-meter condo), or you scroll through Facebook groups and LINE chats and hope a stranger replies with a clean rate.
Weshare exists to fix that match. List what you’re not using. Rent what you don’t want to own.
The hidden bottleneck: trust, not inventory
People ask us if we’re worried about supply. We’re not. Bangkok homes are full of underused stuff. The bottleneck is the moment a stranger asks to take that DSLR away for two days, and the owner has to decide if it’s coming back.
That moment isn’t solved by features. It’s solved by a thousand little signals — phone verification, ratings, deposits, dispute resolution, transparent fees, trust badges, ID checks, insurance. Every one of those signals raises a question in the user’s head. How do you verify? What if it doesn’t come back? Who pays the deposit? What’s your cut?
FAQs are the cheapest place to put those answers. Cheaper than a sales rep. Cheaper than a chatbot. Cheaper than waiting for the user to email and giving up halfway.
So we wrote sixty of them
We organized them into seven categories the way we think about the platform:
- About Weshare — the existential ones. What is it? Why not just buy? Is it available outside Bangkok?
- What Can You Rent? — the surprisingly long-tail edge cases.
- For Renters — how to find, book, pay, return.
- For Owners — how to list, price, protect yourself.
- Trust & Safety — the section that took the longest to write.
- Payments & Receipts — the boring-but-non-negotiable stuff.
- Ratings & Reviews — what makes the system self-policing.
None of these were invented in a vacuum. They came from imagining someone — a Thai expat moving back home, a freelance photographer in Sukhumvit, a parent with a stroller their kid outgrew — and asking what would actually stop them from clicking List.
What writing the FAQs taught us
1. The strangest questions are the most useful
“Can I rent out my pets?” was the question that broke us. It started as a joke during one of the writing sessions. Then someone said: actually, in Thailand people rent out small dogs for film shoots. Should they be able to?
We ended up with a real answer (no, we don’t allow living things on the platform — too many dimensions of risk we can’t insure) and a real product decision (we’d rather have a clear “no” up front than discover edge cases through abuse reports later). The “Can I rent food and drink?” question went the same way.
The lesson: weird questions surface real product principles. If we’d waited for users to ask, we would have answered case-by-case, inconsistently, and probably regretted it.
2. “Is Weshare available outside Bangkok?” forced us to be honest
The instinct was to write “Not yet — we’ll expand soon!” The honest answer was “Bangkok is the only city where the marketplace can actually work right now, because P2P rental needs density. We’ll know it’s time to expand when Bangkok has so many listings that demand spills outward.”
That’s a less marketable sentence. But writing the honest version locked us into a strategic discipline: we don’t ship to a second city until Bangkok works. No half-measures, no premature scaling. Sometimes a FAQ is also a commitment device.
3. The Trust & Safety section was the hardest, by far
Every other category answers questions like “how does X work.” Trust & Safety answers “what happens when X goes wrong.” That’s a fundamentally different writing problem. The reader is already nervous when they get there. They don’t want vague reassurance — they want specifics about deposits, claims processes, what’s insured and what isn’t.
We rewrote those answers four times. We’re still not happy with them. They’re better than nothing, and they’re going to get rewritten again as soon as we have real cases to learn from.
4. What we cut
We started with closer to ninety entries. Thirty got cut for the same reason: they answered questions a careful reader would never ask, or duplicated something already on the listings page. A FAQ that no one needs is worse than no FAQ — it dilutes the section and signals that you don’t know what your users actually care about.
The cut list is its own product document. It tells us what we thought mattered but didn’t.
Why “before launch” instead of “as questions come in”
Two reasons. First: a marketplace’s first hundred users are skeptical by definition. They’re showing up to a platform with zero reviews, zero transactions, zero proof. The FAQ is part of their evidence. Sending them away to email support — or, worse, leaving them with unanswered questions — kills the signup.
Second: writing FAQs in advance forces you to define your platform. If you can’t answer “what counts as damage” before launch, you don’t have a damage policy yet. Better to find that out at the writing desk than after a dispute.
The honest cost
It took roughly forty hours of writing across two weeks. Counting research (looking at how Fat Llama, Airbnb, and ShareGrid handled the same questions), debate, and rewrites, probably closer to sixty. That’s a meaningful chunk of pre-launch effort for content that won’t directly drive revenue.
We’d do it again. The FAQ pays for itself the first time a hesitant user lands on the trust-and-safety section, finds an answer that sounds like it was written by a real human who has thought about their concern, and clicks continue instead of closing the tab.
What’s next
The FAQ is going to be wrong in places. We know this. The plan is to track every support email, every confused chat message, and rewrite the relevant FAQ entry in real time. After three months of operation, we’ll publish what changed and why — a kind of post-mortem of our own assumptions.
If you want to see what we actually shipped, the full FAQ is at weshare.rent/faq. If you spot something we missed, write to us. That’s how this gets better.