Every agency says it works with adult clients. The ones that have shipped in the category answer certain questions instantly, because they have been burned by them. The ones that have not will answer in generalities. These ten questions are sorted by how quickly they separate the two.
If you are already choosing a contractor rather than reading up: here are the 33 services we build.
1. Which processors have you actually onboarded?
Expect names - CCBill, Verotel, Segpay, Epoch - and expect an opinion about which one fits your model and which declined a client last year. "We will integrate whatever you choose" means they have integrated none of them.
2. What happens if the processor declines us?
A real answer covers the fallback order, what documentation improves a second application, and how the timeline moves. This single question eliminates most candidates.
3. Where will this be hosted, and what is their abuse policy?
Mainstream providers suspend on the first serious complaint. A company that has operated here names hosts, knows which have held up, and treats the abuse policy as an architectural input rather than a purchasing detail.
4. How do you handle 2257 and age assurance?
Where the content requires records, they should describe a structured vault and the custodian statement. On age assurance they should ask which jurisdictions you serve before answering, because the answer differs by country and the wrong one is a legal exposure.
5. What does your moderation queue look like?
If the answer is an upload form, they have not run a platform. Ask about the human review path, the repeat-infringer policy, and what the operator sees at nine in the morning.
6. Show me a site you built that is still running
Not a portfolio screenshot - a live URL. Discretion is normal in this category, so an NDA-bound answer is legitimate; "we cannot show anything at all" combined with vague processor answers is not.
7. Who owns the code and the data?
Get it in writing before the first invoice. Ownership, escrow if the platform is proprietary, and an export path for content and customer records. Operators discover the answer at the worst possible moment - when they want to leave.
8. What is the running cost of what you are proposing?
A build quote without a monthly figure is half a quote. Hosting, CDN, processor percentage, moderation time and compliance maintenance all recur, and they are the numbers that decide whether the business works.
9. How do you handle takedowns and law-enforcement requests?
Rare, high-consequence, and revealing. A company with experience has a documented path and knows who signs. One without will improvise, and improvisation here is expensive.
10. What would you refuse to build?
The best answer names something: content that is illegal where you are registered, verification theatre that collects data without protecting it, a geo strategy that pretends a blocked market is served. A contractor with no limits will happily build the thing that ends the business.
Reading the answers
You are testing for two things: whether they have operated in this category, and whether they will tell you something you do not want to hear. The second matters more. Most expensive failures in adult projects are not technical - they are a processor that never approved, a jurisdiction nobody checked, or a moderation obligation discovered after launch. A contractor who raises those before the contract is worth more than one who quotes lower.
Where to look, and what the sources are worth
Search results for this category rank agencies that invested in ranking, which is a signal about their marketing rather than their delivery. Better sources, in descending order of usefulness: operators in your niche who will name their contractor, processor account managers who see which integrations arrive clean, and industry forums where a complaint survives longer than a review.
Directory listings and awards are worth almost nothing here. The category is excluded from most mainstream awards, so what remains is either paid placement or self-declared.
The trial project
Before committing a platform budget, buy something small - a landing page, an integration, a migration of one section. It costs a fraction of the build and answers what no interview can: whether they hit dates, whether the code is legible, whether they raise problems early or present them as finished surprises.
Watch three things during it. How they behave when something goes wrong, because something will. Whether the questions they ask are about your business or only about the ticket. And whether the handover is complete without being chased.
Contract points specific to this category
- Ownership on termination. Code and content return to you whatever the reason the relationship ended, including non-payment disputes.
- Confidentiality both ways. They keep your operation private; you agree what they may say about the work, which is usually nothing.
- Compliance responsibility. State plainly who is accountable for records, age assurance and takedowns after launch. Ambiguity here surfaces at the worst possible moment.
- Subcontracting. Whether work leaves the company, and whether the same confidentiality applies to whoever receives it.
- Data handling. If they touch production, what happens to identity documents and customer records in their environment, and when they are deleted.
Warning signs that are actually warning signs
Not every oddity matters. These four do: a quote produced without any questions about jurisdiction or payment model; a refusal to name any processor; no mention of moderation on a project with user content; and a promise about rankings, which nobody can make honestly. Each indicates the same thing - a proposal written for a generic website by someone who has not operated in this category.
Common questions
What is the single most revealing question?
What happens if the processor declines us. A company with category experience answers with a fallback order and a timeline; one without treats it as hypothetical, because they have never had an application refused.
Is it a red flag if they cannot show past work?
Not by itself - discretion is normal here and NDAs are common. It becomes a flag when combined with vague answers on processors and hosting. Experience shows up in specifics even when clients cannot be named.
Should we require code ownership?
Yes, in writing, before the first invoice - along with an export path for content and customer data. Operators usually discover the answer at the point they want to leave, which is the worst time to negotiate it.
Related reading