# How to Launch a New Service with Enough Evidence to Explain It By AI Visibility editorial team AI-assisted article. Before promoting a new service, ask someone unfamiliar with it to work out whether it fits their situation, what it includes and how to take the next step. Then ask the team delivering it to confirm that the public explanation matches what they can actually do. A launch needs an approved offer and a customer path the business has verified. A name, a hero image and an announcement can introduce the service, but the buyer still needs the conditions that affect their decision. Create a small release pack with the evidence behind each important claim. Include what is included, who qualifies, how pricing or quoting works, and what happens after an enquiry. Give each item a named owner and decide what can go live while a detail remains open. That lets the team launch with a bounded offer even if some planned options are still in development. Disclosure. AI Visibility is published by Lunasol, which offers GEO and AEO services. The worked service launch is fictional. The public Bedia Pottery example illustrates published offer information. No private client material, live assistant test or booking was used. About AI Visibility (https://aivisibility.ae/about/) Start with the service the team can deliver on launch day Ask the service owner to describe the first transaction from the customer's point of view. Specify the audience, location or coverage, what the business delivers, prerequisites and the action that starts the process. Decide which exceptions the team can handle and how someone should ask about them. Write the offer at the scope the team can support now. A service that will eventually cover several cities can launch with one verified coverage area and a clear way to check eligibility. Capture the commercial conditions as part of the same review. If the business sells a fixed package, identify the approved price basis and what changes the total. If it quotes case by case, explain which inputs the team needs and when it can confirm the amount. Record which options are included and which cost extra. If the service requires an appointment, distinguish a booking request from an accepted slot. Have the relevant owner confirm any material condition before the copy presents it as available. Identify the owner of the service after launch. An editor can publish the explanation, but operations needs to know what capacity and conditions were promised. Customer service needs the same wording and a route for questions it cannot answer. GOV.UK's Service Manual describes skills for testing with users and supporting a service once it is live. A commercial team can adapt that principle by confirming who can handle enquiries, verify exceptions and communicate changes before promotion starts. GOV.UK Service Manual on setting up a service team (https://www.gov.uk/service-manual/the-team/set-up-a-service-team) Gather proof that matches the promise A public service page can demonstrate how specific an offer needs to be. Bedia Pottery's private workshop page describes an instructor-led session and different clay options. The options have different descriptions of what the customer takes home or what happens afterward. Those distinctions are useful to a person choosing a workshop. A launch editor can use the structure as an example of explaining the experience and the practical conditions together. The page describes the merchant's offer. It supplies no confirmation of a particular date or seat. Bedia Pottery private workshop page (https://bediapottery.ae/product/private-pottery-workshop/) The studio also publishes a cancellation and rescheduling policy. When your own service has a product page and a general policy, check which policy applies to the particular booking and where the buyer sees it. If two internal drafts differ, have the commercial owner resolve the conflict before publication. A customer should be able to tell which terms govern the action they are about to take. The published Bedia policy is cited here as an example of a separate source and this guide does not interpret how it applies to a particular reservation. Bedia Pottery cancellation and rescheduling policy (https://bediapottery.ae/cancellation) Bedia Pottery's official cup-experience reel provides a separate example of a promotional handoff. The caption invites an enquiry by direct message. In the earlier inspection, the canonical timestamps showed 2 November 2026 and the profile grid displayed a different date. The reel can illustrate the offer it describes and the stated way to ask. It does not establish the terms of the private workshop page or a confirmed slot. In a launch pack, attach each social asset to the specific claim and destination it supports. Official Bedia Pottery Instagram reel (https://www.instagram.com/bediapottery/reel/DfOlYzwtALc/) Collect stronger evidence for stronger claims. A demonstration can show how a step works when the conditions are known. A permitted customer example can illustrate one experience. A claim that a service typically produces a quantified result needs evidence covering the cases and measure that the statement describes. If the service is new and those records do not exist, explain the process and what the team can verify today. Keep outcome claims on hold until the evidence supports them. View the selected official Instagram post (https://www.instagram.com/bediapottery/reel/DfOlYzwtALc/) Bedia Pottery’s cup-experience reel invites an enquiry by direct message. The inspected canonical timestamps showed 2 November 2026. Build the service explanation and the customer path together Give the writer the key decision in one sentence. For example, “A facilities manager should be able to tell whether the assessment covers one site and what to send to request it.” The page should answer that question before asking for a commitment. Place the material conditions near the relevant action. A form can explain which requests it accepts and what response follows. The page can link to detailed terms where needed while retaining enough information for the customer to understand the choice. Check what happens after someone clicks. A customer may be sent to a form, a calendar or a messaging channel. Confirm the destination and what it asks for. If the service takes a deposit, make sure the customer can tell when a reservation is confirmed. If the launch begins with a waitlist or invitation, use wording that describes that stage. Do not let a promotional caption imply immediate booking while the destination only collects interest. Use the same approved facts in the main language versions. A translation can shorten a sentence without removing the area, price basis or eligibility that changes the offer. Ask a reviewer to check the language that customers will actually see, including the form labels and confirmation. Where the business has different support routes by language, state that explicitly and verify both. The point is for each reader to reach a person or process that can handle the request described. Write down which launch claims can appear in a short announcement. If a social caption promises a result that the detailed page qualifies, revise the caption and check the destination together. A useful short version can say who the service is for and what the next action starts. Keep the details that materially change eligibility or cost next to that action. Where the announcement uses a demonstration, label whether it shows the ordinary offer or an example prepared for the launch. Check whether the evidence can be maintained after the launch team moves on. Keep the approved offer and its supporting documents in a place the service owner and editor can reach. Add a date for verifying time-sensitive details and an event that brings the check forward, such as a change in coverage or staffing. A launch pack should tell a later editor whom to ask and which public copies depend on the answer. Run a rehearsal with a customer who qualifies and one who does not Imagine a fictional Dubai workshop launching a pickup assessment for upholstered furniture. The launch covers specified districts and begins with an assessment request. The team can confirm collection after reviewing the item and address. Its operations lead is still deciding whether oversized pieces can be handled. The editor can explain the approved assessment route and avoid promising collection for cases the team has yet to confirm. This is a fictional release exercise. Item What to prepare Owner and release check Offer scope Covered districts, eligible items and how exceptions are reviewed Operations confirms the first release boundaries Quote process Required photos and address details, plus what the first response means Service owner verifies the price explanation and enquiry language Public route Service page, form and approved confirmation message Web owner checks the same path as a visitor Promotional asset Approved example, claim, date and destination Campaign owner verifies the exact asset and scope Support handoff Staff response for eligible, uncertain and out-of-scope requests Support lead checks the route and names a delegate Try a request inside the confirmed coverage and another outside it. Can a person tell what to send and whether they are requesting an assessment or booking a collection? Check the public form without submitting unless the business has authorised a test. In an authorised rehearsal, label the request, confirm that it reaches the right team and inspect the response. The release owner should see the result before approving promotion. A valid page and a functioning form do not establish that the request was correctly routed. Use a short record to preserve the release decision. Service launch evidence Service, launch date and reader decision Approved inclusions, exclusions and source Price or quote basis and applicable terms Customer action, destination and confirmation meaning Public proof, permissions and owner Release decision, outstanding conditions and next check Decide what can go live and what needs more evidence Approve the part of the offer the team can explain and deliver. If one option is unresolved, remove it from active promotion or label it accurately as pending. If the uncertainty affects the whole service, hold the launch or publish an interest route whose purpose is clear. Record who can clear each condition and when they will check. A campaign deadline does not determine whether an operational condition is ready. Set an early checkpoint with the people who can act. For the fictional workshop, the support lead can identify requests outside the approved districts and the web owner can verify whether the form explains eligibility. If the team learns that customers repeatedly skip the photo requirement, it can improve the instructions and test the same path again. Keep the observation and the resulting change with the launch record. After release, review actual enquiries and questions where available. GOV.UK's live-service research guidance includes looking at how users experience changes and involving the people who support them. For a small business, the same principle can mean asking the enquiry team which information people still need before they can proceed. Compare those questions with the live page and fix any missing explanation. Keep observed demand and service performance separate from any later search or assistant observations. GOV.UK guidance on user research in live services (https://www.gov.uk/service-manual/user-research/user-research-in-live) The wider AI Visibility guides cover initial testing and information improvements. This launch exercise starts earlier in the customer path, with a verified offer and a reliable place to act. Save the approved terms, page and evidence checks together. When the team expands the service, it can reopen the affected conditions and verify the new promise before it becomes part of the public offer. AI Visibility guides and 90-day plan (/category/guides/)