Today I launched this site: an independent field guide to Customer Success for aviation maintenance software, using Veryon as the case study. Here’s what went into day one and why it’s shaped the way it is.
Why Customer Success, and why Veryon
Maintenance software only earns its keep when technicians actually use it and operators can tie it to uptime. That gap between “installed” and “valuable” is exactly where Customer Success lives. Veryon is a strong case study: six product lines (most of them acquired and renamed), a new AI layer called AIRE, and a customer base Veryon puts at 5,500+ organizations in about 150 countries.
Step 1: Build the source library first
Before writing a word, I had Claude collect and rank public sources: product pages, press releases, webinars, product demos, the YouTube channel, analyst profiles and user reviews. Then I added five trade outlets (Aviation Week, AIN, FlightGlobal, Aviation Maintenance and Simple Flying) and flagged every article on AI in maintenance that mentions Veryon. The library is now 70 sources, each with a priority and notes on how to use it.
Step 2: Structure the site around the customer journey
- Platform at a glance: every product with its legacy name, because customers still call Veryon Tracking “Flightdocs.”
- The CS journey: Onboard, Adopt, Prove value, Renew & expand, mapped to what’s specific about maintenance software (logbook activity as an early churn signal, for example).
- What’s new: a timeline of the moves customers will ask their CSM about, from the AIRE launch to the Polaris Aero acquisition.
- AI in MRO: curated trade press coverage, with articles that cite Veryon highlighted.
Step 3: Ship, then audit
Claude built a lightweight WordPress block theme, installed it through my HostGator account, and then a separate audit agent checked the live site for SEO and accessibility. It caught link colors that failed contrast standards and confirmed the SEO plugin was already handling titles and structured data, so we didn’t duplicate it. A second agent trimmed unused plugins and turned on caching.
Step 4: Ask the Lab goes live
The assistant I promised in the first version of this post is now live. Click Ask the lab in the corner of any page, or the Ask the lab card under Resources, and ask about Veryon’s products, news or Customer Success. The starter questions are a good place to begin.
How it works
- A small custom WordPress plugin sends each question to Claude (the Haiku model) from the server, so the API key never reaches the browser.
- Answers come only from a curated knowledge base summarized from the source library. If the answer isn’t there, the assistant says so instead of guessing.
- Every on-topic answer ends with links to the sources it used.
- The knowledge base is cached between questions, which keeps the cost of each answer to a fraction of a cent.
Guardrails I set before writing any code
- Spending cap: it pauses once it has spent $1 in a day and resumes at midnight UTC.
- Rate limit: 20 questions per visitor per hour.
- Scope: Veryon, its products and news, and Customer Success for aviation maintenance software. Anything else gets a polite one-line decline.
- Aviation safety: it never gives maintenance, repair or inspection instructions. Those must come from approved maintenance data and certificated professionals.
- Independence and privacy: every chat opens with a note that this is an independent project, not affiliated with Veryon, and asks visitors not to share personal information.
Lesson learned: a chatbot’s rules matter as much as its knowledge. Deciding the scope, the safety line and the budget first made the build itself the easy part.
What’s next
The site has grown into the Aerospace Lab, with a second track on the space industry and AI. Next up: teaching Ask the Lab to answer space questions from that briefing.
This is an independent learning project and isn’t affiliated with or endorsed by Veryon.