Case study categories by industry

• B2B professional services: Categories

  This category collects case studies about B2B professional services, such as consulting firms, where visitors are executives, department heads and procurement at the same time. The case studies are typical scenarios built from common project patterns, not named clients, and their outcomes are written as expected outcomes, never as measured results. They show two situations. In one, a consulting firm's website works when each visitor role finds a short explanation of what the firm does and then deeper detail on request, by cutting content, adding role-based paths and writing to explain rather than promote. In the other, an unclear website that grew over the years is rebuilt as a structural job: audit what exists, cut what is redundant, merge overlaps and rebuild navigation around how visitors judge a service. Each case ends with answers to common questions.

• Healthcare & clinics: Categories

  This category collects case studies from healthcare. Patients are often uncertain, and they judge medical credibility and clarity of communication at the same time, so a health website has to keep medical accuracy while using calm, plain wording and making the way to contact obvious. Three cases show it. One is a typical scenario, not a named clinic, about replacing promotional wording with a step-by-step structure that explains services, specialties and the care process. One is a real project, kept anonymous: a Greek-language information website for a paediatrician, built with Next.js, with articles for parents, structured data for the practice and its FAQ, and a contact form processed on the server with a limit per IP address. The third is the AWS infrastructure we built from scratch for a US healthcare SaaS platform.

• Internal tools & platforms: Categories

  This category collects case studies about our own tools and platforms, each named and described as an own product. The CMS behind every website we build keeps languages in step, converts images automatically on upload, manages redirects and a log of 404 errors, offers fields for short answers and structured data, and protects the admin with roles and two-factor login. Praion AI is our SaaS platform, with a separate database for every customer. Our quality and security agents check every build on a fixed route, and every confirmed finding is fixed with a test that fails before the fix and passes after. The Planner turns a detailed specification into a working application without supervision: the test comes first, results are checked in a browser against the design, and a quality gate decides what moves on.

• Multi-stakeholder organisations: Categories

  This category is for case studies about organisations that serve several groups at once, for example leadership, operational teams and outside partners. The case we have published is a typical scenario built from common project patterns, not a named client, and its outcome is described as expected, never as measured. The main idea is that the website works when each group gets its own clear path and the messages stop overlapping. The focus is on separate audiences, role-based paths and fewer overlapping messages, and the scenario chooses clarity over trying to say everything on one page. It shows how that is done, step by step, starting with who the groups are and what each one needs to decide, and it ends with answers to the questions readers ask most often.

• SaaS & technology: Categories

  This category collects case studies about SaaS and technology companies. A SaaS website helps people understand the product when content is organised by audience and depth, with use cases before feature lists, because visitors include decision-makers, technical teams and day-to-day users, often within a short evaluation window. One case is a typical scenario that shows how separating roles and revealing detail gradually makes a product easier to evaluate. Praion AI is our own SaaS platform: each customer lives in a separate database, and three apps, Lead Concentrator, Content Studio and Product Manager, share accounts, brands and one wallet of AI credits, with two-factor login and scanning of every attachment. The third case is an AWS infrastructure built from scratch for a US healthcare SaaS platform, with a traffic filter of 23 rules and an automatic script that blocks scanners.

• Supervised businesses: Categories

  This category is for case studies about businesses that a supervisory authority oversees and other places where a wrong or unclear statement carries real responsibility. The case we have published is a typical scenario built from common project patterns, not a named client, and its outcome is described as expected, never as measured. In a bank or insurance company the website works best when every page has a named owner, one set of terms and a predictable path. The focus is clear ownership, one vocabulary and predictable navigation. The scenario is explicit that the website does not certify anything: it shows responsibilities clearly, so that a reviewer, a partner or a customer can see who stands behind each statement. The case shows how that structure is built, the steps involved and what to expect from it, and it ends with answers to common questions.

← All case studies